Hi,
I just rebuilded a droplet to Debian 10 and i’m getting Permission denied (publickey) error on ssh access, i followed the guide of DO documentation but i’m still getting the same error. I’ve already try deleting the old known_hosts, removing entries of the old server, but nothing seems to work.
Thanks
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Hi @afboteros,
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:
rwx------
andrwxr-xr-x
are fine, butrwxrwx---
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./.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.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
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
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 Runrestorecon -r -v /path/to/users/.ssh
.Regards, KDSys