You may see each character you type in a Telnet session appear twice or none of your characters appear at all if Termius incorrectly detected whether local echo should be on or off.
When local echo is on, Termius echoes (shows) each character you type on the screen. Local echo is on when Termius doesn’t expect the server to echo the characters. When local echo is off, Termius doesn’t echo any characters, but rather simply send it to the server because it expects the server to echo characters.
Termius expects the server to echo when it receives the following commands from the server:
Character duplicates will appear when both Termius and the server echo characters. Characters won’t appear at all when both Termius or server don't echo them.
Configuring the server in a way that is sends
WILL ECHO or
DON'T ECHO should solve the issue. Either command will disable Local Echo on the client’s (Termius) side.
Was this article helpful?
Articles in this section
- My App Store subscription is not active
- I can't run the iOS app in the background
- I don't see the local terminal option in the desktop app
- I see double / none of my characters in a Telnet session
- I get the ‘no route to host’ error message
- I can’t enter characters (pipe, backslash, etc.) using the Option key
- I can’t connect to a server having .local in its name
- I get the ‘Unable to write public key file’ error
- I can’t map Caps Lock
- Termius keeps asking me to provide a passphrase for my PuTTY key