Repository Not Found
remote: Repository not found - fatal: repository not found - over HTTPS or SSH, the repository is missing or not visible to you.
Repository Not Found
Symptom
Over HTTPS, signed in:
remote: Repository not found
fatal: repository 'https://<INSTANCE>.git.eu/<USERNAME>/does-not-exist.git/' not found
Over SSH:
Repository not found
fatal: Could not read from remote repository.
Cause
You are signed in, but the repository is not visible to you:
- the owner or repository name in the URL is wrong;
- the repository was renamed, moved to another owner, or deleted;
- the repository is private and you are not a collaborator. git.eu gives the same answer as for a missing repository, so it never tells who can see what.
Diagnose
1. Show the URL git uses:
git remote -v
2. Open the repository page on the instance website, signed in with the same account. If the page does not open either, the repository is missing or not shared with you.
Fix
Option A - Fix the URL (recommended)
Copy the clone URL from the repository page and set it:
git remote set-url origin https://<INSTANCE>.git.eu/<USERNAME>/<REPO>.git
Option B - Ask for access
For someone else's private repository, ask the owner to add you as a collaborator.
Verify
git ls-remote origin
It lists the branches and tags of the repository.
Prevent
- Copy clone URLs from the repository page.
- After a rename, update the remote of every clone with
git remote set-url.