You can do this by editing SSH’s configuration files. The solution is to properly manage multiple SSH keys, so that your git client doesn’t send the wrong key to the server. When Github checks if that user has access to the repository, it will likely fail, thus producing the error saying your account does not have permission to use your own repo. Due to the way SSH authentication works, it will still “sign you in” to Git’s remote server, but as the wrong user. This can be a problem if you have multiple accounts and need to use separate keys for each of them. It is not “permission denied,” but instead “permission denied to account.” This is fundamentally different from the first error.

In this case, Github has accepted your SSH key, but it’s still not working correctly even though your local git repo is configured to use the right email address, if you give it the wrong key, it will authenticate you as the wrong user. If you use multiple Git accounts, you may have this error: Permission to Username/Repository.git denied to otheraccount. This is probably the most common Git mistake, and the solution to this is simple- set up an SSH key for your account.īut, you can also run into a very similar looking error message, even after having an SSH key set up properly. If you don’t have an SSH key at all on your account, you’ll almost certainly get the following error when trying to push: Permission denied (publickey).įatal: Could not read from remote repository. If you’re using the latter, you may run into issues with key handling, including Git using the wrong SSH key and signing you into a different account. When connecting to a remote Git server, like Github, your client must authenticate using HTTPS or SSH based tokens.

Git ssh keygen windows