Let’s first being with the usual stuff, I know you mentioned you’ve actually checked the permissions and other stuff like that but let me post how they should be just in case:
- Your home directory ~, your ~/.ssh directory and the ~/.ssh/authorized_keys file on the remote machine must be writable only by you:
rwxr-xr-x are fine, but
rwxrwx---is no good, even if you are the only user in your group (if you prefer numeric modes: 700 or 755, not 775).
~/.ssh or authorized_keys is a symbolic link, the canonical path (with symbolic links expanded) is checked.
- Your ~
/.ssh/authorized_keys file (on the remote machine) must be readable (at least 400), but you’ll need it to be also writable (600) if you will add any more keys to it.
- Your private key file (on the local machine) must be readable and writable only by you: rw——-, i.e. 600.
Now that we’ve passed the standard stuff, let’s get going on the more interesting stuff.
If you try and run thus on your droplet
/usr/sbin/sshd -d -p 2222
Can you connect then without a password, using the SSH key? What does the debug information says on your droplet? It should state something like
In this case, what you can do is temporarily stop the SSH daemon and replace it with one in debug mode. Don’t worry, stopping the SSH daemon won’t kill any existing connections. This means it’s possible to run this without being connected to the droplet’s Console but it’s somewhat risky. If the connection does get broken for any kind of reason, you’ll need to connect using your droplet’s console. Anyway, you can run the following
service ssh stop
service ssh start
If it again runs with the debug mode being on, then for sure it’s the SELinux causing the issues, it’s most probably set to Enforcing. The .ssh dir will probably be mislabeled. Look at
/var/log/audit/audit.log. Check with ls -laZ and then Run
restorecon -r -v /path/to/users/.ssh.