1. Home
  2. GitHub
  3. Errors and problems
  4. Repository not found

Error codeGitHubGit command line

GitHub: "Repository not found"

Wrong URL or no access to the repo

Git could not find the repository. GitHub says it either does not exist under that name or your account has no permission to see it.

Is GitHub down right now? Major outage: 787 problem reports in the last hour. Many people are having trouble, so this error may come from GitHub's side: waiting can be enough.
Fix it

How to fix "Repository not found"

  1. Copy the clone URL from the repository page instead of typing it.

  2. Run git remote -v and fix the URL with git remote set-url if it is wrong.

  3. Make sure the account you sign in with is the owner, a collaborator or on a team with access.

  4. Run ssh -T [email protected] to check that your SSH key is linked to the right account.

  5. Check that the repository really exists on GitHub.

From GitHub's help pages: docs.github.com, in our words. Checked on 5 November 2026. If the steps do not help, GitHub's own support is the next stop.

More

More GitHub errors and common problems

All GitHub errors and common problemsLive GitHub status