Remote Repository not found – Git push error

Updated on June 26, 2020

remote: Repository not found” – I encountered this error while pushing a code change to the repository.

remote: Repository not found
fatal: repository '' not found

Solution: If you see this error while pushing a code change to the repository, it means that the repository does not exist or you do not have permission to access it! There are a few solutions for this error.

remote: Repository not found – Few suggestions

Check Spelling

Typos errors are very common in the digital world. As repository names are case-sensitive, make sure the spellings are correct.

Check permissions

If you are trying to push to a private repository but do not have permission to view the repository, you’ll receive this error.

Make sure that you have access to the repository in one of the below ways:

  • You’re the owner of the repository
  • A collaborator on the repository
  • A member of a team that has access to the repository.

Check if the repository really exists

Make sure that the repository really exists on GitHub! If you’re trying to push to a repository that doesn’t exist, you’ll end up with this error.

Repository not found? Check your credentials

In rare circumstances, you may not have the proper access to a repository, which happened in my case. I had used the wrong credentials that couldn’t access the repository. I removed the credentials from the credential manager as shown below:

D:\Qiskit> git credential-manager uninstall

And added the new credentials which have permission to access the repository.

D:\Qiskit> git credential-manager install

Now I could easily push to the repository.

Was this article helpful?

Related Articles

Leave a Comment