Push Failed: Failed With Error: Could Not Read From Remote Repository.

Earlier you lot tin can read from a private repository or write to a Git repository, you must be authenticated. If you use the wrong Uniform Resource Locator (URL) to connect to a repository, or accept incorrectly prepare your Secure Crush (SSH) authentication, yous'll encounter the "fatal: Could not read from remote repository" fault.

This guide discusses what this error means and why you may run across it. Information technology walks you through 2 potential solutions so you can overcome this trouble when using Git.

fatal: Could not read from remote repository

SSH is a protocol for authenticating with remote devices. SSH is normally used to cosign with Git because you don't demand to type in your countersign every time you authenticate.

Every platform has its ain way of authenticating users over SSH. Using GitHub, for instance, you must provide your SSH key on their dashboard. Then, you can utilize the SSH URL associated with your repository to authenticate with GitHub.

By default, the private SSH key for your device will be in a file chosen ~/.ssh/id_rsa. This file is in the hidden .ssh directory in your root folder. This central volition simply exist if you accept generated information technology. Otherwise, you'll need to utilise the ssh-keygen command to generate a new fundamental.

If y'all have not correctly gear up SSH authentication, Git will be unable to verify your identity.

The two common causes to the "fatal: Could not read from remote repository" error are:

• Not adding your SSH key to the SSH agent
• Using a HTTP URL to connect to a repository

Allow'southward discuss each of these causes.

81% of participants stated they felt more confident about their tech job prospects after attending a bootcamp. Get matched to a bootcamp today.

The average bootcamp grad spent less than six months in career transition, from starting a bootcamp to finding their first job.

Cause #1: SSH Agent Issue

The SSH agent stores your SSH key. When you endeavour to authenticate with a Git repository over SSH, Git will check the SSH amanuensis for your key.

Your SSH key can be removed from the SSH agent for various reasons. This will make information technology impossible to authenticate with a Git repository.

Let's try to clone a Git repository that is individual to our local automobile:

git clone git@github.com:career-karma-tutorials/ck-git

When nosotros try to sign in, the Git command line returns an error:

fatal: Could non read from remote repository.

This mistake informs us nosotros have an authentication event. If you encounter an SSH authentication issue, your first port of phone call is to add your primal to the SSH keychain:

This will add together our id_rsa key to the keychain.

Another common mistake is to add together the incorrect primal to your keychain. If you utilize a key with a different name than id_rsa to authenticate with Git, make sure yous add that key to your keychain and not the id_rsa key.

Find Your Bootcamp Match

• Career Karma matches you with tiptop tech bootcamps
• Become sectional scholarships and prep courses

Crusade #2: Using a HTTP URL

There are two ways you tin authenticate with Git: over HTTP and SSH. The Hypertext Transfer Protocol (HTTP) method requires specifying your username and password to a Git server to access a repository.

To authenticate with HTTP, you'll use a URL that looks similar this:

https://github.com/career-karma-tutorials/ck-git

Yous cannot use this URL to connect to a Git server over SSH. This is because SSH and HTTP are different protocols. If you try to sign in to the above URL using SSH, yous'll be prompted to enter your username and password.

We've got to employ an SSH URL to connect to a repository over SSH. You can verify the URLs that yous use to connect to a remote repository using the git remote -v command:

origin    https://github.com/career-karma-tutorials/ck-git (fetch) origin    https://github.com/career-karma-tutorials/ck-git (push)

We can run into that our "origin" remote uses HTTP instead of SSH. For an existing repository, nosotros can change our URL to apply SSH using the git remote set-url command:

git remote set-url origin git@github.com:career-karma-tutorials/ck-git

This control sets the "origin" URL to exist equal to our SSH URL. At present that we've run this control, our existing Git repository will utilize the SSH URL to connect to the remote version of the repository.

If you are cloning a new repository, you don't demand to change the URL with which you are working. Instead, you just need to make sure you use an SSH URL to clone the repo:

git clone git@github.com:career-karma-tutorials/ck-git

At present, we can run commands like git pull, git commit, and git push on our repository considering we have the correct admission privileges.

Conclusion

The Git "fatal: Could non read from remote repository" error occurs when there is an issue authenticating with a Git repository. This is common if you have incorrectly set SSH hallmark.

To solve this error, brand certain your SSH fundamental is in your keychain and you connecting to a repository using the correct URL.

maguirewilk1952.blogspot.com

Source: https://careerkarma.com/blog/git-fatal-could-not-read-from-remote-repository/

Bagikan Artikel ini