# Huggingface says ssh-keygen Key is invalid

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-says-ssh-keygen-key-is-invalid%2F125466%3E%5C
**Category:** Beginners\
**Created:** [November 18, 2024, 1:51am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-says-ssh-keygen-key-is-invalid%2F125466 "2024-11-18T01:51:27Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 18, 2024, 3:51am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-says-ssh-keygen-key-is-invalid%2F125466%2F4 "2024-11-18T03:51:44Z")

</div>

In the case of a 403 error, account-based restrictions are often suspected, but in the case of a 400 error, what could it be?  
The authentication-related functions of HF often have bugs, so I think that some setting is probably wrong somewhere that we don’t know about…

> [@Unable to clone repository via ssh](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Funable-to-clone-repository-via-ssh%2F79478)%3A
>
> I followed [Git over SSH](https://huggingface.co/docs/hub/security-git-ssh#generating-a-new-ssh-keypair) to test my SSH authentication (base) ➜ ssh -T git@hf.co Hi ivnle, welcome to Hugging Face. ivnle is the correct account that I added my public key to, but I’m unable to clone this repository. (base) ➜ git clone hf.co:datasets/bigcode/starcoderdata data/starcoderdata-raw Cloning into 'data/starcoderdata-raw'... ivanlee@hf.co: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the reposi…

---

_[View the full topic](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-says-ssh-keygen-key-is-invalid%2F125466)._