PuTTY gives "Network error: Software caused connection abort" and closes....why?

March 1, 2015 43.9k views

I want to use PuTTY with username and password instead of ssh keys.

I edited /etc/ssh/sshd_config and uncommented '#PasswordAuthentication yes '

Then I restarted ssh with 'service ssh restart'

But, when I try and use PuTTY to log into server PuTTY does not connect and gives the "Network error: Software caused connection abort" message.

What am I screwing up?

1 comment
  • does putty have a way to add options? Like: ssh -v youruser@yourdomain.com

    adding the -v will give you some more output which can help figure out what is going on.

    Also, be sure to check permissions on your .ssh folder for your user:

    chmod go-wrx ~
    chmod 700 ~/.ssh
    chmod 600 ~/.ssh/authorized_keys
4 Answers

If you are continually encountering this issue I would recommend attempting to log into the console in the control panel. If you have a password and shell set for your user you will be able to log in there as it does not depend on your ssh service. I would then recommend checking /var/log/auth.log and the other log files in /var/log for your ssh login attempts and you should find more information on why they failed.

Hi! I am having the same problem. I can acces my droplet via "Console Acces" inside my browser, but not via Putty. I have tried both user/pass and public/private key. I get the same "Network error: Software caused connection abort".

*I am using Windows 10

  • Same Problem here also. Seems that its the Problem of windows OS. Tried from different machine and it works there. However, the Putty and Filezilla/ Cyberduck shows the error on my PC.
    Tried formatting the whole PC and install fresh windows 10 with no luck.

Had the same trying to connect via putty to a netapp. what worked for me was settings a different new ip on the nic of the netapp, and then setting the old correct ip on that same nic again.

Does anyone find a good answer on this?

I am having same issue, but as in other forums I get it temporarily resolved by resetting my Win 10's DNS cache using ipconfig /flushdns etc. But it is not a permanent solution and reappear after 1-2 days of work.

Have another answer? Share your knowledge.