Server Fault is a question and answer site for system and network administrators. 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

Please help. Everything was working fine. How can I connect to the command line now?

Amazon EC2 server
Ubuntu & Apache2
Only one user (root - not real name) has SSH access, publickey only
All other users allowed SFTP access, chrooted to home directory

What Happened
I connected to the server via SSH.
In a user's home directory, I edited a php file and moved a directory.
I logged out.

Now I can't access the server via SSH. When I try to connect via SSH, my public key is tried but does not allow access. Once the public key fails, it checks other public keys on my machine and then gives Too many authentication failures for.... The public key file has not been modified in months.

Can still connect via SFTP but I am chrooted to the user's home directory.

How can I access my command line prompt? What should I do?

share|improve this question

Contact Amazon Tech support. "Too Many Authentication Failures" tells me either you have the wrong key setting in your client and you have tried too many times with the wrong credentials, someone is trying to hack your account, or someone in your organization is trying to login with a password and failing numerous times.

share|improve this answer
Added clarity to the question regarding the error message. Key never changed. Credentials are the same. Hacking is a possibility but doubtful. – csi Apr 26 '13 at 22:19
My point is that if you are getting that error message, you'll need to talk to them to gain access back. It is a server side problem which could have been caused by someone trying to brute force your root password, etc. It will most likely remain unknown until you can get them to restore your access. – T. B. Apr 27 '13 at 2:15
up vote 0 down vote accepted

How can I access my command line prompt?

Create a copy of the Volume.
From the copied Volume, attach it as a secondary volume to a different instance.
SSH into that instance and mount the new volume.
Use the command line tools to diagnose, edit and copy as needed.
Once fixed, replace the old volume on the corrupt server with the fixed volume.

Hope this answer helps someone else who may be struggling with the same issue.

share|improve this answer
Not to be a shill but I detailed all of the steps above in a blog post.… – csi May 1 '13 at 13:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.