Git – remote: Repository not found

Encountering the “Git remote: Repository not found” error can be frustrating, but it’s usually straightforward to fix. Here’s a simple guide to help you resolve this issue:

Solution 1. Verify the Repository URL

Ensure that the URL of the remote repository is correct. Repository URLs are case-sensitive, so even a small typo can cause problems. To check the current URL, navigate to your project directory and run:

git remote -v

If the URL is incorrect, update it using:

git remote set-url origin <correct-repository-URL>

Solution 2. Confirm Your Access Permissions

If the repository is private, ensure that you have the necessary permissions. If you don’t have access, contact the repository owner to grant you the appropriate rights.

Solution 3. Update Stored Credentials (Most Common Issue)

Outdated or incorrect credentials can lead to authentication issues. To resolve this, remove existing GitHub credentials from your system:

• On Windows:
  1. Open the Control Panel.
  2. Navigate to User Accounts > Credential Manager > Windows Credentials.
  3. Remove any entries related to Git or GitHub.
• On Mac:
  1. Open the “Keychain Access” application.
  2. Search for entries related to GitHub.
  3. Delete the relevant items.

After clearing the old credentials, try accessing the repository again. You’ll be prompted to enter your username and password, allowing you to authenticate with the updated credentials.

Solution 4. Check Repository Existence

Ensure that the repository you’re trying to access still exists and hasn’t been renamed or deleted. You can do this by visiting the repository URL in your web browser.

By following these steps, you should be able to resolve the “Git remote: Repository not found” error and continue working on your project.

Conclusion

Learn more about using the Git & GitHub from their original learning resources here