My setup originates with Laravel Forge connecting to various GitHub repos. I’ve been running a dozen sites without issue for about 6 months. All of a sudden, yesterday I started getting this permission denied (publickey) error in the DigitalOcean Console when I run any
git push or
git pull command.
I’ve been through these articles:
They all recommend roughly the same solution:
sudo nano /etc/ssh/sshd_config
PasswordAuthentication yeswhich I shouldn’t need to do since this is SSH, not password auth
PublickeyAuthentication yesor in my case, uncomment it
sudo service sshd reload
I’ve tried all these steps multiple times but I still can’t get reconnected to my git repositories.
I’ve also reviewed the Forge SSH Keys instructions and confirmed the server key provided is the correct server key in
Any additional ideas for 2020? I’m running Ubuntu 18.04.3
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.
I was logged in as the
rootuser accidentally, instead of my usual git user
So mucked up my file permissions by trying to
git addfiles, and once I got logged into the correct user, I had to reset my file permissions in the
/.git/objectsfolder of my site(s) because they were owned by
This discussion answer was helpful.
If I understand correctly, Laravel Forge is used like a central hub which pushes your Git project to different DigitalOcean Droplets, correct?
If that’s correct, then it seems for some reason the droplet isn’t accepting SSH connections via SSH keys. Let’s start troubleshooting. Firstly, can you see if you are able to SSH using your own terminal or if you are getting the same error?
Try to run the following command on the droplet and then connect from the computer/environment using the said key
You should be able to connect and receive something like the following on your Droplet :
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 Run
restorecon -r -v /path/to/users/.ssh.
Want to learn more? Join the DigitalOcean Community!
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.
Sign up now