remote: Repository not found. fatal: repository 'https://github.com/x/y.git/' not found
GitHub/GitLab says the repository doesn’t exist — or you lack access to a private repo.
Seen on:
Git
Meaning
Hosting services return “not found” for private repositories you can’t access. Typos, renamed repos, wrong accounts and cached credentials are typical.
Common causes
- Typo or repo renamed/moved
- Private repo and you’re authenticated as another account
- Cached credentials for a different user
- Token without repo scope
⚡ Quick fix
- Verify the URL in the browser while logged in
- Check git remote -v
- Clear cached credentials or use the right account/token
Detailed fix by platform
Git
git credential-manager erase # or remove github.com from macOS Keychain / Windows Credential Manager
How to diagnose
- URL — Correct owner/repo?
- Account — Which account is used?
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026