SSH causes intermittent issues

[taman0753]

Discord username (optional)

No response

Describe the bug

When i do SSH into some sever this happens frequently .

channel 21: open failed: connect failed: open failed channel 21: open failed: connect failed: open failed channel 23: open failed: connect failed: open failed channel 21: open failed: connect failed: open failed channel 23: open failed: connect failed: open failed channel 25: open failed: connect failed: open failed channel 21: open failed: connect failed: open failed channel 23: open failed: connect failed: open failed channel 25: open failed: connect failed: open failed channel 21: open failed: connect failed: open failed channel 23: open failed: connect failed: open failed channel 25: open failed: connect failed: open failed channel 21: open failed: connect failed: open failed channel 21: open failed: connect failed: open failed channel 23: open failed: connect failed: open failed

To Reproduce

After doing ssh to machine.

Expected behaviour

No response

Screenshots

No response

Operating System

MacOS

OS Version

12.6

Shell Version

version 3.2.57

Warp Version

v0.2022.10.11.08.13.stable_01

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

[orionarcher]

I came to report the same issue.

[taman0753]

@szgupta Can you check this

[szgupta]

Hey @taman0753, is this happening only in the latest release?

[taman0753]

@szgupta This was a intermittent issue is previous versions as well , but after update its very frequent which causes me to not use Warp terminal !!

[taman0753]

I have used the troubleshooting step given here https://docs.warp.dev/features/ssh#troubleshooting

[taman0753]

@szgupta @alokedesai Any updates

[alokedesai]

@taman0753 Just to confirm, you aren't seeing this in other terminals? Does this still repro in Warp if you disable the "Warp SSH Wrapper" setting?

[taman0753]

@alokedesai Other terminals are working as expected , after disabling "Warp SSH Wrapper" i am not able to utilise warp feature like suggestions , history etc.

[alokedesai]

@taman0753 Yeah, just wanted to make sure it was something specific to our SSH wrapper implementation :) Are you able to reproduce this for all the boxes you SSH into or is it only for specific ones?

[taman0753]

@alokedesai Its almost for all the boxes. after disabling "Warp SSH Wrapper" the issue is not seen as of now.

[taman0753]

@alokedesai But after disabling SSH wrapper functionalities are not working

[taman0753]

@alokedesai @szgupta Any updates here , please check its very frequent.

[alokedesai]

@taman0753 We're actively looking into this. Could you send us a video of the issue occurring so we can better understand when and how the error manifests?

[alokedesai]

@taman0753 Could you also run sudo sshd -T | grep -Ei 'TCPKeepAlive|AllowTCPForwarding|PermitOpen' on the remote boxes where this reproduces and send the output?

[taman0753]

@alokedesai Please find the output of the above command.

[taman0753]

@alokedesai I have shared the video over email ([email protected]) to you. Please acknowledge.

@taman0753 We're actively looking into this. Could you send us a video of the issue occurring so we can better understand when and how the error manifests?

[taman0753]

@alokedesai Let me know if any other thing needed to dig deeper to the issue.

[alokedesai]

@taman0753 Are you able to reproduce this if you turn off syntax highlighting and error underlining?

[orionarcher]

I disabled syntax highlighting and error underlining and am still having a similar issue on nearly every command:

channel 3: open failed: administratively prohibited: open failed
channel 5: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed

[alokedesai]

@orionarcher Is this a recent regression? Are you able to reproduce with this build?

[orionarcher]

I was able to reproduce with that build. I didn't see any option for syntax highlighting or error underlining present though.

[alokedesai]

@orionarcher Ok good to know, how long has this issue existed in Warp for you?

[orionarcher]

I only started using Warp a couple weeks ago and it happened the first time I sshed into a cluster.

[taman0753]

@taman0753 Are you able to reproduce this if you turn off syntax highlighting and error underlining?

Yes @alokedesai Issue is still there

[taman0753]

@alokedesai Can we get the update to correct this issue.

[horacimacias]

I'm having the same issue as well. In case this helps, in my case I'm using ssh controlmaster and I've seen this problem in a "child" ssh connection. I checked MaxSessions as suggested but I have that commented out. If there is any troubleshooting/logs that can help here just let me know; I'm eager to using warp more. keep up the good work!

[rohitrp]

Facing same issue. This started happening after I had updated Warp 2-3 weeks ago. Any update on this?

[alokedesai]

@taman0753 @horacimacias @rohitrp We're still trying to better understand why this is happening as we've been unable to reproduce on our end, thank you for your patience here.

In the meantime, it would be very useful for us if you could help us debug when this issue went wrong by testing on prior builds of Warp. Does this issue repro on this version of Warp?

[rohitrp]

@alokedesai I have been using this build (v0.2022.09.07.14.56.stable_00) for the last 1 hour and didn't face the SSH issue. With the latest build, I start getting the SSH errors (channel open failed) within mins. So, it looks like this build doesn't have this SSH related bug.

[dannyneira]

Hi @taman0753 @orionarcher @horacimacias, I'm working to reproduce this issue, and I just wanted to rule out if there are some unsupported plugins on the remote machines. Please try the following on the remote machines and see if the issues persist.

1. Re-enable the ssh wrapper in Warp.
2. Disable your dotfiles just for Warp on the remote machine by using this conditional statement:

if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW

# The entire contents of your bashrc/zshrc on the remote machine.

##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi

This way we can make sure the plugins on the remote machine are disabled for Warp and not the cause of the issues.