GitHub Git github.com: Permission denied error with existing deploy keys

#1

Post by unixfox » Tue, Jul 21, 2026, 10:15 AM UTC

Am I only the one getting this error on existing deploy keys on GitHub:

git@github.com: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

A deploy key that used to work does not anymore.

It has been happening for the last 2 hours. And this happens to several of my deploy keys, like 4 already affected.

Re: GitHub Git github.com: Permission denied error with existing deploy keys

#2

Post by johnroseftl » Tue, Jul 21, 2026, 10:40 AM UTC

Same thing for me. Had to rotate the key.

Re: GitHub Git github.com: Permission denied error with existing deploy keys

#3

Post by bastiao » Tue, Jul 21, 2026, 10:40 AM UTC

same here, https://www.githubstatus.com/incidents/g40zcbvchny4

Re: GitHub Git github.com: Permission denied error with existing deploy keys

#4

Post by bastiao » Tue, Jul 21, 2026, 10:42 AM UTC

johnroseftl wrote: post #2

Same thing for me. Had to rotate the key.

does it work after rotate the key? Actually I tried, but this happening with deployed keys at user profile.

Re: GitHub Git github.com: Permission denied error with existing deploy keys

#5

Post by johnroseftl » Tue, Jul 21, 2026, 10:46 AM UTC

bastiao wrote: post #4

johnroseftl wrote: post #2

Same thing for me. Had to rotate the key.

does it work after rotate the key? Actually I tried, but this happening with deployed keys at user profile.

Yep it did. At least for us. Repo deploy key.

Re: GitHub Git github.com: Permission denied error with existing deploy keys

#6

Post by sph » Tue, Jul 21, 2026, 12:07 PM UTC

No, but I can’t seem to reply to notifications via email any more: https://news.ycombinator.com/item?id=48991146

Re: GitHub Git github.com: Permission denied error with existing deploy keys

#7

Post by yaldasoft » Tue, Jul 21, 2026, 12:08 PM UTC

had to rotate key, was using RSA now using SSH. Not sure if thats the fix but it was down for 3 hours based on our CI stats.