SSH Connectivity Issues: Broken pipe

crypticseeds commented 8 months ago

Discord username (optional)

crypticseeds

Operating System

MacOS

Operating System and Version

14.3.1

Local Shell Version

5.0.17(1)-release

Remote Shell Version

5.0.17(1)-release

Warp Version

v0.2024.02.20.08.01.stable_02

I have tried commenting out my system & user rcfiles and warp still will not bootstrap

[X] Yes

Screenshots

Include shell xtrace output

WARP_DEBUG_MODE=1 ssh k8s-control The authenticity of host 'k8s-control (172.31.43.252)' can't be established. ECDSA key fingerprint is SHA256:nNNes3zE1+jlBMsgADSrcwx2D3fFIZdCxC7W+t+setM. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'k8s-control,172.31.43.252' (ECDSA) to the list of known hosts. Password: Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.15.0-1053-aws x86_64)

Documentation: https://help.ubuntu.com
Management: https://landscape.canonical.com
Support: https://ubuntu.com/advantage

System information as of Wed Feb 28 10:53:12 UTC 2024

System load: 0.56 Usage of /: 51.6% of 19.31GB Memory usage: 36% Swap usage: 0% Processes: 251 Users logged in: 1 IPv4 address for docker0: 172.17.0.1 IPv4 address for ens5: 172.31.43.252 IPv6 address for ens5: 2600:1f16:fb6:4402:c70c:1cee:7fe4:7430 IPv4 address for tunl0: 192.168.175.0
Ubuntu Pro delivers the most comprehensive open source security and compliance features.

https://ubuntu.com/aws/pro

Expanded Security Maintenance for Applications is not enabled.

27 updates can be applied immediately. To see these additional updates run: apt list --upgradable

8 additional security updates can be applied with ESM Apps. Learn more about enabling ESM Apps service at https://ubuntu.com/esm

New release '22.04.3 LTS' available. Run 'do-release-upgrade' to upgrade to it.

Last login: Wed Feb 28 10:46:01 2024 from 216.24.219.230

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa

None

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

LFd3v commented 8 months ago

Hi, there. It seem that you are using bash as the local and remote shell, is this correct? Have you also check the ssh troubleshooting steps from the documentation? Thank you.

kevinyang372 commented 8 months ago

Hi there! Does this "broken pipe" message happens right away when you connect to the SSH session? Do you mind sharing your .ssh_config file to help us debug this further?

davidbaranek commented 7 months ago

Hi, I have a similar problem. It happens when a remote computer logs me out due to inactivity. The terminal is then unusable, I have to close it and open a new terminal tab.

dustinmoris commented 2 months ago

Same issue here, I can SSH using Warp to a variety of hosts, but for some reason I get immediately the Broken Pipe error when SSH'ing into my Hetzner box.

Works without issues from my native macOS terminal.

Has anyone found a solution to this?

dustinmoris commented 2 months ago

Hi there! Does this "broken pipe" message happens right away when you connect to the SSH session? Do you mind sharing your .ssh_config file to help us debug this further?

@kevinyang372 I don't know about the OG, but for me this happens right away and my ~/.ssh/config is empty.

EDIT:

The remote shell is /bin/bash and my local shell is /bin/zsh so both are supported according to the docs:

Running command ssh works as well, so the issue is with the ssh wrapper for sure.

warpdotdev / Warp