Are you facing the “Digitalocean Droplet Server Refused Our Key” issue? Read the article to know more about some quick solutions. Bobcares, as a part of our DigitalOcean Managed Service offers solutions to every query that comes our way.

Fixing the “Digitalocean Droplet Server Refused Our Key” Issue

Here are some steps we can try to troubleshoot if we are unable to access the DigitalOcean Droplet via SSH using a key pair we have generated and added to the authorised keys file:

1. Verify the permissions on the authorised keys file. It should have read and write permissions of the owner when we are currently root user.

2. Ensure that keys for authentication are accepted by the ssh daemon. To verify this, search for the subsequent lines in the following:

3. Check the /var/log/secure or /var/log/auth.log files for error messages. There might be information in these log files explaining why the server is rejecting the key.

4. Regenerating the key pair and adding the new public key to the authorised keys file is an option to try if everything else fails. Use the following commands on the local computer to accomplish this:

5. Verify that the Droplet’s firewall rules are set up to accept incoming connections on port 22, which is the standard SSH port. We can use the following command to verify this:

[Want to learn more? Click here to reach us.]

Conclusion

We should be able to diagnose the problem and get back into the Droplet via SSH by completing these steps. We must think about making a new Droplet and moving the files and apps to it if we are still having trouble accessing the original one.