-
Notifications
You must be signed in to change notification settings - Fork 83
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
Error connecting to Debian / OpenSSH 7.4 #40
Comments
Looks like something might have gone wrong in KEX since the client is forcing a disconnection Probably easier to debug if you can provide the client's side by adding:
|
I added a few console logs of my own.
Result:
It seems that the transport.disconnect is raising an error, before |
I can tell you off-list the hostname of the server I'm connecting to, if you want to try it for yourself. It's on the Internet. |
Note: I am having the same issue with Ubuntu 20.04 connecting to a RHEL server... I tried connecting through the server manually and received an error saying that it was trying to request diffie-hellman-group1 algorithm. I enabled that globally in the /etc/ssh/ssh_config using KexAlgorithms=+diffie-hellman-group1-sha1 and was able to connect directly but not through SSHy. I believe this is an error when trying to connect to an antiquated server that is not on the latest SSH version. I say this because I can connect to other servers fine but the one I am having trouble with is very old and has not been updated in a minute. @candlerb is your distant server running the latest SSH version? |
And when logged onto that machine:
|
Trying to connect to a Debian 9.13 server, SSHy just shows
WebSocket connection failed: Error in connection establishment: code 1005
in the terminal window. It doesn't make a difference whether a correct or invalid username/password is given.The browser console shows:
so it appears that something went wrong during DH exchange.
Running the server in debug mode (
/usr/sbin/sshd -ddd -p 99
and connect to port 99), the server shows:It would be good to improve the error handling in this situation (#39) to give a more meaningful error, as well as actually fixing the issue.
The text was updated successfully, but these errors were encountered: