Sshexchangeidentification: read: Connection reset by peer This basically means the TCP connection was 'reset' immediately after being accepted by the server. Common reasons for this are: The remote SSH server software is malfunctioning (e.g. How to solve SSH Ubuntu - sshexchangeidentification: read: Connection reset by peer.
Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upHave 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
commented Oct 6, 2017
I just installed vagrant ,virtualbox, forked and cloned the fullstack-nanodegree-vm repo, then vagrant up and the machine is running, however when i try to vagrant ssh to it, i get: |
commented Nov 7, 2017
If you're on windows, you might need to change your BIOS settings. Once you get into the settings, you have to change a 'disabled' to 'enabled' |
commented Nov 19, 2017 • edited
edited
I am getting the exact same error on Windows 10 running virtualbox. What BIOS setting would I have to change? Thanks. |
commented Nov 19, 2017
To enable virtualization. |
commented Nov 19, 2017
Getting virtualization to run isn't the problem. llelgt said he has the machine running as do I. The specific error is 'ssh_exchange_identification: read: Connection reset by peer' when running vagrant up or vagrant ssh. |
commented Jan 8, 2018
I'm getting the same error, using Windows 7 Enterprise |
commented Jan 10, 2018
Hello, i'm getting the same error on Windows 7 Ultimate |
commented Jan 18, 2018
getting below message:
i am using windows 7 Enterprise and i installed virtualbox, vegrant in VDI machine. please let me know how to resolve the above issue. |
commented Jan 31, 2018
same problem here? |
commented Feb 16, 2018
Hello, I had the same issue, it was that the SSH key is insecure, you can see the issue if you do |
commented Mar 21, 2018
I have the same problem. Does anybody know how to slove? Whether in linux or windows, i met the same error information: ssh_exchange_identification: read: Connection reset by peer |
commented Apr 23, 2018
I have the same problem. Been trying for weeks to run vagrant. What if 'Getting started' actually worked and wasn't a dependency hell. |
commented Jun 7, 2018 • edited
edited
I have the same problem too. I tried to
|
commented Feb 28, 2019 • edited
edited
I had the same issue. The following commands worked for me.
|
commented Apr 26, 2019
same problem but my virtualization is enabled and it is not fixed anyone have any more ideas |
commented Jun 10, 2019
turn off hyper-V (windows features). |
commented Jun 11, 2019
so this (for me) ended up being a painfully simple problem where my coding-enviroment was in usersdesktopoverdrive and the overdrive was the problem i just had to move it out of the overdrive folder |
I cannot connect to my server via ssh using my computer, but I can connect to this server via my cell phone using termius app. I have checked /etc/hosts.allow
and /etc/hosts.deny
and my iptables, and I have alse searched google, it seems no answer fits this problem. I don't know how to solve it , here is ssh -v 183.17.228.80
output
I can ping this server, here is telnet
12 Answers
That actually means that your IP is blacklisted by the server. Try to whitelist your IP address to be able to login
Just reboot your server which you want to ssh. It worked for me, previously I was facing the same issue.
The way I solved the problem is I went to the host machine and ran a few commands.
I got connected to the machine after that.
karelThe above error happen when you have limit of failed try to authenticate to the server and you have too many ssh keys on your client (more than value of MaxAuthTries)
What you can try is to increase the value of MaxAuthTries and restart sshd daemon. Or you can limit the number of keys in your ~/.ssh
directory and use subdirectories and ~/.ssh/config
file to define key per host/group of hosts
I'm using my cellular hot spot to connect to the web, while I was working the console froze, and I couldn't connect any more ssh_exchange_identification: read: Connection reset by peer
I tried to reset the SRV but it didn't help
Only when I change my network connection (to a hotspot on a different cellular) I could connect again.
NOTE: I can still use the old connection to connect to SRVs on a different AWS, strange...
To solve the issue, proceed as follows:
- Reboot your server from server online terminal.
If this does not work,
- Edit the file
$HOME/.ssh/known_hosts
- Delete any content inside this file, when it will reconnect to any servers you ssh then you must re-accept connections.
I had this same thing happen, and needed to ssh -v 'ip addr' and then i saw that i needed to accept the certificate.Also may be an ACL or route rule blocking putty: example -
Putty client has 10.x.x.x addr with firewalls blocking enterprise network from talking to DMZ hosts, but your cell phone at 58.x.x.x whatever public ip address can talk to the dmz host youre trying to reach.
so I'd look at the ssh -v info when you try to connect again, see if you can glean any info, and then check if there are rules keeping you from getting to your server at a firewall or router level, not in a denyhosts file on the server itself.
Create an new ssh key pair for user authentication. SSH Keys and Public Key Authentication guide
Just follow the guide.
There may be many reasons but one of most possible reason can be(in my case it was) ssh / port 22 is not allowed by firewall.
You can allow ssh connection by User-interface (some providers allow that) or If you have any alternative method to login (Ex. digitalocean provide a console button ) you can run below command
It looks like ssh daemon on the server is hung. Are you sure it is running? When you telnet to ssh, you have to see a signature. Something like:
What I see from your output is ssh daemon not responding on server side. I recommend to connect via IP-KVM (or in some other way) to the remote machine and restart sshd.
This could be because you do not have an openssh server running on your ubuntu. You can run the below command to check the status of your openssh server.
If the status is not active (running)
, you might want to install and/or start the openssh-server. You can do so with the commands shown below.
- Check that sshd in installed and running of the server.
- Make sure that the daemon is installed and started.You must be able to 'man sshd'. I think that package it is in is open-ssl, and you will need to start the daemon ( and stop it when you don't need it.).