Drop SSH connection
Discord username (optional)
No response
Describe the bug
When I try to connect to my router I get an error and the connection drops.
To Reproduce
- ssh [email protected] -p 22
Expected behaviour
I expect to see no errors.
Screenshots

Operating System
MacOS
OS Version
12.5.1
Shell Version
zsh 5.8.1 (x86_64-apple-darwin21.0)
Warp Version
v0.2022.08.31.18.11.stable_00
Additional context
No response
Does this block you from using Warp daily?
Yes
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
No response
Hello @pavel-hushca, I'm Danny, Support Engineer at Warp.
So sorry to hear you're having this issue with SSH.
To enable Blocks over SSH, Warp uses an SSH Wrapper function; navigate to Settings > Features if you need to disable it.
Note: You'll need to start a new session before a change is reflected) or try invoking the SSH binary directly: /usr/bin/ssh
__ Danny Neira (he/him/his) Support Engineer www.warp.dev
@pavel-hushcha, Hi I'm Danny, Support Engineer with Warp. Have you had any luck with the above troubleshooting steps?
I'm unable to repro this issue on my end, Any updates on the above steps.
Hello @pavel-hushca, I'm Danny, Support Engineer at Warp. So sorry to hear you're having this issue with SSH. To enable Blocks over SSH, Warp uses an SSH Wrapper function; navigate to
Settings > Featuresif you need to disable it. Note: You'll need to start a new session before a change is reflected) or try invoking the SSH binary directly: /usr/bin/ssh … __ Danny Neira (he/him/his) Support Engineer www.warp.dev
Since we cant reproduce this issue i'll close out this one, but feel free to reopen if you can confirm this is happening with the latest version of Warp.
Hello @pavel-hushca, I'm Danny, Support Engineer at Warp. So sorry to hear you're having this issue with SSH. To enable Blocks over SSH, Warp uses an SSH Wrapper function; navigate to
Settings > Featuresif you need to disable it. Note: You'll need to start a new session before a change is reflected) or try invoking the SSH binary directly: /usr/bin/ssh …
Disabling SSH wrapper helps.
But with enabled SSH wrapper have the same issue:

@dannyneira, could you please reopen it?
@pavel-hushcha No problem, we can open but will need abit of help with the repro as i'm unable to repro on my end. Are you using bash or zsh on the remote machine? are you using any custom prompt or rc files on the remote machine?
My guess is that you normally have a custom prompt or rc file and that Warp is unable to parse it.
You can check whether it’s something in your dotfiles by setting up clean configs:
Set
ZDOTDIR=/
in your
~/.zshenv
file. This forces Zsh to run with zero configs.
You can disable parts of your dotfiles just for Warp by using this conditional statement:
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW
# Whatever you want to disable
##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi
We have a list of incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools And more info on custom prompts here: https://docs.warp.dev/features/prompt
@pavel-hushcha No problem, we can open but will need abit of help with the repro as i'm unable to repro on my end. Are you using bash or zsh on the remote machine? are you using any custom prompt or rc files on the remote machine?
My guess is that you normally have a custom prompt or rc file and that Warp is unable to parse it.
You can check whether it’s something in your dotfiles by setting up clean configs: Set
ZDOTDIR=/in your~/.zshenvfile. This forces Zsh to run with zero configs.You can disable parts of your dotfiles just for Warp by using this conditional statement:
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then ##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW # Whatever you want to disable ##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE fiWe have a list of incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools And more info on custom prompts here: https://docs.warp.dev/features/prompt
I have that issue trying connect to router's CLI. http://docs.help.keenetic.com/cli/3.1/en/cli_manual_kn-1011.pdf
Hey there, Is it possible to not use the "SSH Wrapper feature" for some connections, make a list of exclusions, etc.? In this case, it will solve such a problem with connecting to the Keenetic, which Pavel also has.
ssh keenetic-fru
[email protected]'s password:
Command::Base error[7405600]: no such command: export.
Connection to 192.168.10.1 closed.