dev@local: ~/project — git
dev@local~/project$git clone
remote: Repository not found.
fatal: repository not found
Diagnostics Translation
The remote server could not locate the repository at the specified URL.
waiting for resolution...
MediumVersion Control System

Reviewed for reference consistency: April 11, 2026

Code is Safe

SECURE

Git has paused the operation to protect your code. No data has been lost or corrupted.

What To Know

This usually means the remote address resolved to a host, but the specific repository target was unavailable to your account or no longer exists at that path.

Where Did It Fail?

Working Tree
Your local files
add
Staging Index
Prepared changes
commit
Local Repo
Commit history
push/fetch
Remote Server
GitHub/GitLab
The error occurred during a network exchange. Your local files are untouched, but Git cannot reach the remote server.

Commands That Trigger This

$git clone
Attempting to a private repository without being authenticated
$Pushing to an old URL after a repository was renamed by an administrator
Pushing to an old URL after a repository was renamed by an administrator

Technical Background

01

This error is notoriously ambiguous because it masks authentication failures. If you are certain the repository exists, the issue is almost always missing or expired credentials.

02

Repository-not-found states often trace back to a remote URL that no longer points at a real repository path or no longer matches your level of access.

Underlying Causes

Typo in the remote URL (e.g., misspelled repository name)
The repository was renamed, transferred, or deleted on the server
You lack read access to a private repository

Frequently Asked Questions

If the repo is private and you are not authenticated, the server returns 'Not Found' to prevent unauthorized users from confirming the repository's existence.

Related Git States

permission-denied-publickeyMedium

The remote server rejected your SSH connection because it did not recognize your SSH key.

authentication-failedMedium

The server rejected your credentials during an HTTPS connection.

remote-origin-already-existsLow

You tried to add a remote named 'origin', but one with that name already exists.