Mac/Linux to Windows Connection | Shell opener command was unsuccessful: client_loop: send disconnect: Broken pipe

[yottoya]

Mac/Linux to Windows Connection | Shell opener command was unsuccessful: client_loop: send disconnect: Broken pipe

[crschnick]

After spending some time trying to set up key-based authentication on windows, I gave up. It's honestly not worth it.

Note that you can still launch the connection from xpipe (I just can't do other stuff like the file browser) in the XPipe 9 PTB, if you enable the don't interact with systems setting for the connection. You should find that

[crschnick]

I assume that you are running the latest xpipe version? As a quick test, you can run the latest PTB build as there were many ssh changes: https://github.com/xpipe-io/xpipe-ptb

If that does not work, you can try running ssh -i ~/.ssh/windows11 [email protected] -T and see whether that reproduces it. Note that if you run an ssh command in warp, it does run through the warp wrapper. I.e. you're not directly executing your local ssh client: https://docs.warp.dev/features/ssh. So you should try that in another terminal.

You can also try running the latest Windows SSH server from https://github.com/PowerShell/openssh-portable. One issue is that the SSH distribution included in windows is quite old, that has caused a few issues before.

[yottoya]

Appreciate the quick response!

So, just now, I did the following:

1. I downloaded the latest xpipe-ptb build, and resynced my linux connections, which got added perfectly no problem.

2. I tried to add the Windows 11 PC as a connection in xpipe-ptb, and it threw back the same error.

3. I totally understand what you mean by warp's wrapper because it doesn't work well when connecting to Windows.

   • So, in the regular terminal app, I ran ssh -i ~/.ssh/windows11 [email protected] -T, and it threw back this error:

     • client_loop: send disconnect: Broken pipe

   • I also ran ssh -i ~/.ssh/windows11 [email protected] -T in warp, and it also threw back this same error.

4. I definitely have that exact OpenSSH installed, exactly for the reason you stated! 😬

[crschnick]

So it seems to have something to do with the -T switch, i.e. the disabled pseudo terminal. You can try solutions listed in here:

• PowerShell/Win32-OpenSSH#1873
• https://unix.stackexchange.com/questions/602518/ssh-connection-client-loop-send-disconnect-broken-pipe-or-connection-reset but I don't think anything of that will work.

I can successfully connect to my Windows systems, so can't reproduce that.

If you have WSL on the windows host, you can try running an SSH server in WSL instead.

[yottoya]

Mannnnnnn I feel like nothing works for me the first time correctly, ever… 😢

As you fore-stated, none of these proposed solutions worked (for me)...

Solution Worked?	Link
Didn't Work (for me)	PowerShell/Win32-OpenSSH#1873
Didn't Work (for me)	https://unix.stackexchange.com/questions/602518/ssh-connection-client-loop-send-disconnect-broken-pipe-or-connection-reset

This might be useful to you to mention, but when I try to add the Windows 11 PC as a Remote SSH connection, and it fails and throws back the Shell opener command was unsuccessful: client_loop: send disconnect: Broken pipe, I click the "insights" on the bottom left, and I take the command that xpipe would've executed, I executed it in my terminal, and I was able to successfully SSH in:

ssh "windows11" -oStrictHostKeyChecking=accept-new -oRemoteCommand=none -oNoHostAuthenticationForLocalhost=yes -t

I think the only solution is transitioning completely over to Linux, forever.

This issue can be closed out because if Windows connections work for you, and no one else has brought this up, it might just be something odd on my Windows 11 system not allowing me to connect.

Thanks for your super quick assistance @crschnick ! I appreciate that more than anything else 🙏

[crschnick]

Let me try my Windows 11 laptop, I only used it on Windows 10.

The insights work because that is what is executed to launch a terminal with -t. The first connection by xpipe is made in the background with the -T switch. I guess you can try running ssh user@host -T -vvv to get some more output.

[yottoya]

Yeah, windows is on its last legs with me, and most definitely, it's not worth it.

Looks like I found a reason to go fully Linux.

Closing out this ticket!

[crschnick]

if you still have your window system, you can try this: #257 (comment)