-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teleport does not set terminal size correctly on connection #1692
Comments
Screenshot of the terminal performing the above tests https://i.imgur.com/mgdcd2Y.png |
And performing the same test in the same terminal via SSH to the same host.
|
@russjones is this the same issue you fixed by #1567 or a different one? |
@russjones thoughts? |
@aashley is that gnome-terminal you're using? |
@aashley I was able to reproduce this using Ubuntu 16.04 and GNOME Terminal 3.18.3. I'll investigate. |
I did some more investigation into this, this only seems to be a problem when using the recording proxy and connecting to a Teleport node. Otherwise terminals are re-sized as expected.
@aashley With what configuration are you running into this problem? |
We're using Teleport Node with recording proxy. Our setup is lots of remote deployed machines on other networks behind NAT firewalls so we use a cloud master with each site being a trusted cluster. Using the recording proxy to maintain logs of the sessions in the cloud master instance as apposed to each individual deployed server. |
What happened: Terminal size is not set correctly and text wrapping does not work correctly. Fix for #1087 does not work.
What you expected to happen: Text to wrap correctly as per every other terminal app.
How to reproduce it (as minimally and precisely as possible):
This was run in gnome-terminal and mate-terminal as per my original comments on #1087 with the same failure results
Environment:
teleport version
): Teleport v2.4.1 git:v2.4.1-0-gf90cc7ctsh version
): Teleport v2.4.1 git:v2.4.1-0-gf90cc7cBrowser environment
Relevant Debug Logs If Applicable
The text was updated successfully, but these errors were encountered: