How to fix fatal: repository 'https://github.com/user/repo' not found in Git

GitBEGINNERMEDIUMUpdated Dec 6, 2025· 340 views

This error appears when Git cannot access a remote repository due to authentication issues, missing permissions, or an incorrect URL. The fix typically involves verifying your credentials or requesting repository access.

Quick fix

Fixes fatal: repository 'https://github.com/user/repo' not found

# Check your current remote URL
git remote -v
  1. Verify the repository URL exists
  2. Check your authentication status
  3. Re-authenticate or update credentials
  4. Create and use a Personal Access Token (PAT)
git — error
# Check your current remote URL
git remote -v
fatal: repository 'https://github.com/user/repo' not found

What this error means

This error occurs when Git cannot locate the remote repository at the specified URL. The message "fatal: repository not found" is somewhat misleading because it can appear not only when the repository truly doesn't exist, but also when you lack proper authentication or authorization to access it. GitHub, GitLab, and other hosting providers return this generic "not found" message for security reasons: they don't reveal whether a private repository exists if you don't have access to it. This means the same error can indicate a genuine typo in the URL, a deleted repository, or simply that your credentials are incorrect or expired. If you previously had access to a repository and suddenly receive this error, the most likely cause is an authentication problem—perhaps an expired Personal Access Token, recently enabled Two-Factor Authentication, or cached credentials that no longer work.

Typical symptoms

  • Git clone command fails with "repository not found" message
  • Git push fails even though you have local commits
  • Git fetch or pull operations cannot reach the remote
  • Error appears for both HTTPS and SSH URLs
  • Private repository appears to not exist despite being created

Common causes

  1. Authentication credentials are missing, expired, or incorrect (most common)
  2. You are not a collaborator on a private repository
  3. The repository URL contains a typo or case mismatch
  4. The repository was deleted, renamed, or transferred to another owner
  5. Personal Access Token (PAT) is missing required scopes
  6. Two-Factor Authentication (2FA) was recently enabled but credentials were not updated
  7. Cached credentials in Git Credential Manager are stale
  8. SSH key is not added to your GitHub/GitLab account or lacks organization approval

How to fix "fatal: repository 'https://github.com/user/repo' not found"

1Verify the repository URL exists

Open the repository URL in your browser to confirm it exists and you have access:

bash
# Check your current remote URL
git remote -v

If the repository was renamed or transferred, update the URL:

bash
git remote set-url origin https://github.com/correct-user/correct-repo.git
2Check your authentication status

Test if you can authenticate with GitHub/GitLab:

For SSH:

bash
ssh -T git@github.com
# Should respond: "Hi username! You've successfully authenticated"

For HTTPS (GitHub CLI):

bash
gh auth status
3Re-authenticate or update credentials

If authentication failed, re-authenticate:

Using GitHub CLI (recommended):

bash
gh auth login

Clear cached credentials and try again:

*Windows (Credential Manager):*
1. Open Control Panel > Credential Manager
2. Remove entries for github.com or gitlab.com

*macOS (Keychain):*

bash
git credential-osxkeychain erase
host=github.com
protocol=https
# Press Enter twice

*Linux:*

bash
git config --global --unset credential.helper
4Create and use a Personal Access Token (PAT)

GitHub no longer accepts passwords for Git operations. Create a PAT:

1. Go to GitHub Settings > Developer settings > Personal access tokens > Tokens (classic)
2. Click Generate new token
3. Select scopes: at minimum repo (full control of private repos)
4. Generate and copy the token

Use the token as your password when prompted:

bash
git clone https://github.com/user/repo.git
# Username: your-username
# Password: paste-your-token-here

Or embed it in the URL (for scripts):

bash
git clone https://your-token@github.com/user/repo.git
5Request repository access

If it's a private repository you don't own, request access:

1. Contact the repository owner or organization admin
2. Ask to be added as a Collaborator (for personal repos) or to the appropriate Team (for org repos)
3. Accept the invitation sent to your email
4. Try cloning again after access is granted

6Switch from HTTPS to SSH (or vice versa)

Sometimes switching protocols resolves authentication issues:

Switch to SSH:

bash
git remote set-url origin git@github.com:user/repo.git

Switch to HTTPS:

bash
git remote set-url origin https://github.com/user/repo.git

If using SSH, ensure your key is added:

bash
# List SSH keys
ls -la ~/.ssh/

# Add key to ssh-agent
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519

Advanced notes

Why "repository not found" instead of "access denied"?

Git hosting services intentionally use vague "not found" errors for security. Revealing that a private repository exists (but you lack access) would leak information to potential attackers. This design choice, while secure, makes troubleshooting harder.

Organization-owned repositories and SAML SSO:

If your organization uses SAML Single Sign-On, your Personal Access Token must be explicitly authorized for SSO access. After creating a PAT, click "Configure SSO" next to the token and authorize it for your organization.

SSH keys and OAuth applications:

SSH keys generated by third-party Git clients (like GitKraken) may be tied to an OAuth application. These keys require explicit organization approval if you're accessing org-owned repositories. Consider generating a standard SSH key pair independently.

Enterprise Server vs GitHub.com:

Ensure you're using the correct host. GitHub Enterprise Server installations have different URLs (e.g., github.mycompany.com instead of github.com). Credentials don't transfer between instances.

Fine-grained PATs:

GitHub's newer fine-grained Personal Access Tokens require explicit repository permissions. If you created a fine-grained PAT, verify it grants access to the specific repository you're trying to reach.

Frequently asked questions

What does "fatal: repository 'https://github.com/user/repo' not found" mean?
This error occurs when Git cannot locate the remote repository at the specified URL. The message "fatal: repository not found" is somewhat misleading because it can appear not only when the repository truly doesn't exist, but also when you lack proper authentication or authorization to access it. GitHub, GitLab, and other hosting providers return this generic "not found" message for security reasons: they don't reveal whether a private repository exists if you don't have access to it.
How do I fix "fatal: repository 'https://github.com/user/repo' not found"?
This error appears when Git cannot access a remote repository due to authentication issues, missing permissions, or an incorrect URL. The fix typically involves verifying your credentials or requesting repository access.
What causes "fatal: repository 'https://github.com/user/repo' not found"?
Authentication credentials are missing, expired, or incorrect (most common) You are not a collaborator on a private repository The repository URL contains a typo or case mismatch
Is the "fatal: repository 'https://github.com/user/repo' not found" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading