Git@hf.co: Permission denied (publickey)

I am having trouble authenticating with my SSH key when trying to access a Hugging Face Git repository. When I attempt to connect, I receive the following error message:

git@hf.co: Permission denied (publickey).

I have provided more detailed debug information of ssh -vvvT git@hf.co below:

debug1: Next authentication method: publickey
debug1: get_agent_identities: bound agent to hostkey
debug1: get_agent_identities: agent returned 1 keys
debug1: Will attempt key: /Users/kenshin/.ssh/hf_id ED25519 SHA256:P0dAH1Z2UlBk...q8eLtjxg4 explicit agent
debug1: Offering public key: /Users/kenshin/.ssh/hf_id ED25519 SHA256:P0dAH1Z2UlBk...q8eLtjxg4 explicit agent
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
git@hf.co: Permission denied (publickey).

I have verified that:

  1. My private key has not been corrupted or modified.
  2. I have added public key to my ssh account.
  3. I have tried generating new key pairs several times.
  4. My network works fine.

Despite these checks, I am still unable to authenticate successfully. I would greatly appreciate any assistance or guidance you can provide to help me resolve this issue. Please let me know if you need any additional information.

Thank you for your help!

7 Likes

I am facing the same error since yesterday. Did you get any support?

Indeed, it seems there is some problem on hugging face end, I am also facing the same issue since yesterday, checked everything, is there any official hugging face channel where we can report this issue other than this forum ?

I am using almost the same way on Github without any problem,
but it just doesn’t work on Huggingface

Same here, I even re-created my SSH key at the peak of the denial phase.

Also have this trouble since yesterday

any one have the luck to find any solution for this?

same issue here. I use the same ssk key pari on github which works fine.

same issue here

same issue here

i believe its fixed now, working fine for me.

2 Likes

@kenshinn I believe it has been fixed by now, can you retry and confirm if it works on your side ?

Now, it works successfully

1 Like

yes! it works fine now

1 Like