I’m having this problem as well and followed the instructions provided by GH here to no avail.

My SSH settings page doesn’t show an “Approve” button for my SSH key, and my key on GH matches up with what ssh-add -l -E sha256 shows locally.

I temporarily solved the issue by deleting my key in GH, generating a new one, and adding it to GH. Unfortunately, when I tried a git command for the first time today, the issue came back.

I’m on a Mac running macOS Catalina 10.15.5.

Any help would be much appreciated!

Also experiencing the same issue

Brilliant! Glad it’s working for you.

I still think there’s a bug in that GitHub is reporting a misleading error message and the wrong fingerprint.

Will look into how to report bugs to GitHub.

@henwen I reported this issue at https://support.github.com/contact/feedback

I only have the wildcard entry, but your answer helped me solve the problem. I stopped receiving the error when I added these config settings that I copied from your above solution:

PreferredAuthentications publickey
IdentitiesOnly yes

Thank you so so much, this just happened me today and adding

  PreferredAuthentications publickey
  IdentitiesOnly yes

solved my issue.

I concur. This issue’s been plaguing me for the past month! The fix from post #8 (adapted from post #4) worked for me as well.

Thank you all!!!

Had this same issue a few times within two days lost like 4 hrs finding solution or work around. I don't think its solely gh issue because when I ran ssh-add -l -E sha256, there were no identities listed even when there were identities listed prior. This might've occurred after I closed a few shells in the term but read on to see how it could also be a gh issue also . I think its a combo of both.

If there is no identities listed ssh-add -l -E sha256,
add private keys (same file name without the .pub extension):
command: (check https://linux.die.net/man/1/ssh-add)
ssh-add .ssh-dir-path/id_ed25519
( this will ask for paraphrase (password), if u forgot it delete .ssh-dir-path/id_ed25519 file and regenerate a new one and u can save to keychain (check https://linux.die.net/man/1/ssh-keygen)
command: (check https://linux.die.net/man/1/ssh-add)
ssh-add .ssh-dir-path/id_rsa

add to file ssh-dir-path/known_hosts
github.com ssh-ed25519
"your public key" (key in id_ed25519 .pub)
github.com ssh-rsa
"your public key" (key in id_rsa.pub)

Then make sure your key for gh matches by running the command 'gh ssh-key list' this is same as https://github.com/settings/keys once logged in, u will not see the actual public key listed there only its name if u give it one with the -t flag (read below) under ssh keys. What u do see as a sort key is the fingerprint (i think). Now here's where the funny stuff happens, so I deleted the key using 'gh ssh-key delete {id#}' which is listed when u run 'gh ssh-key list',then verify I am not being authenticated during a git push with same error and sure enuff I get error:
ERROR: We're doing an SSH key audit.
Reason: unverified automatically (private key found in a public repository)
Please visit https://github.com/settings/keys/27394849 to approve this key so we know it's safe.
Fingerprint:
SHA256:************************************
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

So I re-add the key with 'gh ssh-key add {ssh-dir-path}/id_ed25519.pub -t "{name:string}", then all works.