What does "remote origin already exists" mean?

It means you ran "git remote add origin " but a remote named "origin" is already configured in your repository. Git does not allow two remotes with the same name. You need to either update the existing remote URL, remove it first, or use a different name for the new remote.

What is the difference between git remote set-url and remove + add?

Using "git remote set-url origin " updates the URL while keeping all tracking branch configurations intact. Removing and re-adding the remote clears the tracking configuration, which means you may need to set up upstream branches again with "git push -u origin main". In most cases, set-url is the better choice.

Can I have multiple remotes in one repository?

Yes. You can add as many remotes as you want, each with a unique name. For example, "origin" can point to your GitHub fork while "upstream" points to the original project. Use "git remote add " with any name you choose.

How do I check what URL origin is currently pointing to?

Run "git remote -v" to list all remotes with their URLs. You will see the fetch and push URLs for each remote. If you only want to see the URL for origin, run "git remote get-url origin".

I cloned a repo and want to push to my own fork. What should I do?

After cloning, origin points to the original repository. Rename it to "upstream" with "git remote rename origin upstream", then add your fork as origin with "git remote add origin ". This lets you pull updates from upstream and push your work to your fork.

remote origin already exists — How to fix this Git error

You tried to add a remote named "origin", but one already exists. Here is how to update it, replace it, or work with multiple remotes.

Learn Git step by step

Fatal Error

What this error means

In Git, a remote is a named reference to another repository, usually hosted on a service like GitHub, GitLab, or Bitbucket. The name origin is the conventional default for the primary remote.

When you run git remote add origin <url>, Git tries to register a new remote with the name "origin". If a remote with that name already exists in your configuration, Git stops and shows this error.

This is not a serious problem. It simply means you need to update the existing remote's URL instead of adding a new one, or remove the old remote first. Your local files and commit history are completely unaffected.

terminal — remote already exists

$git remote add origin https://github.com/user/repo.git

fatal: remote origin already exists.

Why it happens

Running git remote add twice

You already ran git remote add origin <url> once and are trying to run it again with a different URL. Git does not overwrite existing remotes — it throws this error instead to prevent accidental changes.

Cloned repo already has origin

When you git clone a repository, Git automatically sets up a remote named "origin" pointing to the URL you cloned from. If you then try to add origin again, it conflicts with the one set up during the clone.

Copying config from another project

If you copied a .git/config file or followed setup instructions from another project, the remote "origin" may already be defined in the configuration before you run the add command.

How to fix it

Three approaches: update the URL in place, remove and re-add, or rename the old remote.

1. Update the URL (recommended)

terminal — set-url

# Update the existing remote URL instead of adding a new one

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

# Verify the change

$git remote -v

origin https://github.com/user/new-repo.git (fetch)

origin https://github.com/user/new-repo.git (push)

# Remote URL updated successfully

2. Remove and re-add

terminal — remove + add

# Remove the existing remote, then add the new one

$git remote remove origin

$git remote add origin https://github.com/user/new-repo.git

# Verify the remote is set correctly

$git remote -v

origin https://github.com/user/new-repo.git (fetch)

origin https://github.com/user/new-repo.git (push)

3. Rename and add new

terminal — rename

# Keep the old remote under a different name

$git remote rename origin old-origin

$git remote add origin https://github.com/user/new-repo.git

# Now you have both remotes available

$git remote -v

old-origin https://github.com/user/old-repo.git (fetch)

old-origin https://github.com/user/old-repo.git (push)

origin https://github.com/user/new-repo.git (fetch)

origin https://github.com/user/new-repo.git (push)

How to prevent it

Check remotes before adding

Run git remote -v before adding a new remote. This shows you all configured remotes and their URLs. If origin is already there, use set-url to update it instead of add.

Use git clone for new projects

When starting work on an existing remote repository, use git clone <url> instead of manually initializing and adding a remote. Clone handles the remote setup automatically and you never need to run git remote add.

Use descriptive remote names

If you work with multiple remotes (e.g., a fork and the upstream project), give each a descriptive name: origin for your fork and upstream for the original. This avoids naming conflicts entirely.

Related commands

git remote

Manage remote repository connections and URLs

git clone

Clone a repository and set up origin automatically

git push

Upload local commits to a remote repository

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

FAQ — remote origin already exists

Master Git remotes with GitQuest

Practice pushing, pulling, and managing remotes through interactive challenges. Build real confidence with Git.

Start learning Git