Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a simple dedicated debian server at a hosting facility. It has been happily allowing me to manually enter both username and password for access via ssh for many years as I haven't needed to bother with Public Key Authentication to access the box.

I no longer can login to the system via ssh. I am prompted for my username, which I enter, wait 20 seconds, before I am dropped by my box.

Things i've tried: PuTTY 0.63 from a Windows 8.1 system and ssh OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 from terminal on an OS X Mavericks install.

The system is responding with: 22/tcp open ssh OpenSSH 6.4p1 Debian 2 (protocol 2.0)

Over the weekend my dedicated server was physically migrated to a new data center and fired back up with the same dedicated IPs. Nothing changed on the box by me before a 'shutdown -h now' was issued in preparation of the system's movement.

The system is back up now and all Apache, MySQL, FTP, and various other services are up and running again. I can access them all with the credentials I have always used, except... ssh.

I have been able to determine the server's time is 4 hours 55 minutes behind EST via timestamps of dummy files placed via ftp and I have synchronized my local system to this time.

I have also started to have the issue that while PuTTY gets a username prompt and then twenty seconds of nothing, the "proper" terminal ssh from OS X Mavericks doesn't get any response at all.

I have a ticket open with the dedicated server company, but this is after having my first ticket closed with "I was able to SSH into your system and after doing some troubleshooting everything seems to be up and working fine." I reopened the ticket as nothing has changed for me.

Anyone have any ideas?

share|improve this question
Try deleting your local known hosts in your putty config or registry HKEY_CURRENT_USER\SoftWare\SimonTatham\PuTTY\SshHostKeys. Generally, if SSH times out, it's because the system doesn't trust you or the SSH server is hanging. – CIA Feb 19 '14 at 4:03
Alas and alack. No change. SSH Host Keys nuked. Attempted to login and was successfully prompted to approve. Username successfully entered. Using username "blah blah blah". was successfully echoed. 20 seconds of no other responses and I received the "Server unexpectedly closed network connection" that I have been receiving. – Qribak Feb 19 '14 at 4:19
In some instances, this is due to a partition being full, meaning the system had no space left to log your login attempt, therefor, denying you access. Do you have remote management tools available other than SSH? – CIA Feb 19 '14 at 4:22
Before the move I cleaned the box up. I currently have 133.46 GB Free Space, as currently reported by a logging service running through Apache. Just checked again to provide current info. Unless there is a remote management tool installed that I have completely forgotten about, or unknown to me that would be running by default, I have no others. SSH has been my only means of management. Discovered open port 80/tcp. Discovered open port 113/tcp. Discovered open port 53/tcp. Discovered open port 111/tcp. Discovered open port 22/tcp. – Qribak Feb 19 '14 at 4:24
Have the tech support people email you a copy of the /var/log/auth.log file and check to see if you get a more descript error. Also, have them check /etc/hosts.deny to make sure your connecting IP isn't listed here and verify /etc/hosts.allow doesn't have something weird in it. – CIA Feb 19 '14 at 4:38

You must log in to answer this question.

Browse other questions tagged .