Introduction

remote: Repository not found means the Git server could not resolve the repository you asked for in the context of your current credentials. That usually comes down to one of four things: the remote URL is wrong, the repository was renamed or deleted, you are authenticating as the wrong identity, or you do not have permission to access a private repository.

The fix is usually quick once you separate “Git cannot find it” from “Git found it but rejected my credentials.” In hosted Git services, those two problems are often intentionally reported with the same message.

First Check the Remote URL

Start by printing the configured remote.

git remote -v

Then compare it with the repository URL shown in the hosting service. If the owner name, organization name, or repository name is even slightly wrong, Git will fail.

To update the remote:

git remote set-url origin [email protected]:example-org/example-repo.git

Or, for HTTPS:

git remote set-url origin https://github.com/example-org/example-repo.git

Confirm the Repository Still Exists

Repositories get renamed, transferred, archived, or deleted. Visit the expected URL in the browser while logged in with the account you think should have access.

If the page does not exist there either, the problem is not your local Git client. The remote target itself changed.

Check Authentication Separately

With SSH, test the identity your client is presenting:

ssh -T [email protected]

That confirms which GitHub account the loaded key maps to. If it is the wrong account, the repository may appear “not found” even though the URL is correct.

With HTTPS, clear stale credentials and authenticate again. Many cases of “repository not found” are really “you authenticated as an account that cannot see this private repository.”

Private Repository Access

For private repositories, correct URL syntax is not enough. Your user, token, or SSH key must have access.

Common failure modes are:

• you were removed from the repository or organization
• the repository moved under a different owner
• the personal access token lacks the required scopes
• your SSH key belongs to a different account than expected

If you are in CI, also check that the bot token or deploy key belongs to the correct repository context.

A Fast Diagnostic Sequence

This sequence usually isolates the issue quickly:

git remote -v
ssh -T [email protected]
git ls-remote origin

git ls-remote origin is useful because it tests remote access without creating a new commit or push attempt.

For HTTPS remotes, you can also inspect the exact URL:

git config --get remote.origin.url

When the Problem Is the Hosting Service URL Shape

Different hosts use different URL patterns. GitHub, GitLab, and Bitbucket do not all use the same path structure, and self-hosted servers may add extra path segments.

That means copying a repository name by memory is risky. Copy the clone URL from the host UI instead of typing it manually.

Common Pitfalls

The most common mistake is assuming the repository exists because the name looks familiar. One missing organization prefix or one renamed repo is enough to break the remote.

Another mistake is testing with the wrong account. On machines with multiple SSH keys or cached HTTPS credentials, Git may authenticate successfully as the wrong user.

People also forget that private repositories often return “not found” intentionally instead of “permission denied.” That is a security feature, not a misleading Git bug.

Finally, do not debug a push first. Use git remote -v, git config --get remote.origin.url, and git ls-remote origin to narrow the issue before attempting more writes.

Summary

• 'Repository not found usually means a bad remote URL, missing repository, wrong identity, or missing permission.'
• Verify the remote URL before changing credentials.
• Test SSH or HTTPS authentication independently so you know which account Git is using.
• For private repositories, access problems often look like “not found” by design.
• Use git ls-remote origin as a clean read-only way to confirm remote access.