This article describes known issues and limitations of the terminal session sharing functionality.
Rendering issues and artifacts
One of the known limitations of the shared terminal sessions is caused by the use of the WebRTC data connection based on the UDP peer-to-peer connection. When the network is unstable or the terminal generates a lot of output (e.g. due to
-R /), or when the terminal is being frequently updated (e.g. by htop), a viewer may see that the output is incomplete or that a character appears at an incorrect position.
The solution is to reconnect to the shared terminal by closing the tab and following the shared terminal link again.
Terminal Size issues
Another current limitation is the absence of synchronization between the size of viewers' terminal and the size of the streamer's terminal. Because of that the viewers' screen may look different from the streamer's screen.
The solution is to adjust the size of the terminal, making it the same as the size of the streamer's terminal.
Was this article helpful?
Articles in this section
- Some symbols in the terminal are rendered as question marks, how can I fix it?
- I get a "Couldn't load reCAPTCHA" error
- I can't use the iOS app in the background
- I can't log in or synchronize data
- I can't connect to a local device on iPhone
- I can't use Termius for Android in the background
- I can't find the local terminal option in the desktop app
- I see double / none of my characters in a Telnet session
- My App Store subscription is not active
- I can't map Caps Lock