-
Notifications
You must be signed in to change notification settings - Fork 785
"Broken pipe" when trying to connect with pseudo-terminal allocation disabled #2024
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is an SSHD issue in 8.9 - #1993 |
Okay, sorry for the trouble. Seems like it is already fixed in 9.1. Did not try 9.1 earlier since it had an extra notice of being a beta-release and non-production ready. I'm curious as all the releases here are marked Beta. Where do I find production releases? |
Yes, all GitHub releases are beta releases. The production releases are available in Windows as a feature-on-demand - https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse?tabs=gui. |
I was getting the issue on OpenSSH 8.6, installed from Windows 11 directly. Then I updated to 8.9 to see if the issue resolves or not. I was getting the same issue on multiple Windows 11 machine when installed with Optional Features. Just in case this helps. I'll anyway resolve this issue since it is fixed in an upcoming version. |
Still having this exact issue on 9.1, but seems to be fixed in 9.2. Installed 9.2 via winget install "openssh beta" Leaving a comment in case someone else sees this |
Uh oh!
There was an error while loading. Please reload this page.
Prerequisites
Steps to reproduce
I have OpenSSH server running on a Windows 11 machine.
When I try to ssh into that machine using
-T
options, the connection dies after successful authentication withclient_loop: send disconnect: Broken pipe
Expected behavior
The connection should keep alive.
Actual behavior
The server crashes and the connection is closed with `client_loop: send disconnect: Broken pipe`
Error details
Server logs
Client Logs
Environment data
Server
Client
Version
OpenSSH_for_Windows_8.9p1, LibreSSL 3.4.3
Visuals
No response
The text was updated successfully, but these errors were encountered: