GitHub Actions "A runner with the same name already exists"
GitHub requires unique runner names within a scope. Registering a new runner with a name still held by a stale or live registration fails until you replace or rename it.
What this error means
config.sh fails during self-hosted runner registration with a duplicate-name error.
github-actions
Error: A runner with the same name already exists.
Use --replace to replace the existing runner, or choose a different name.Common causes
Stale registration not removed
A previous runner with that name was not deregistered (host died without cleanup).
Reusing a name across hosts
Two machines try to register with the same name.
How to fix it
Replace or rename the registration
- Re-run config.sh with --replace to take over the existing name, or
- Choose a unique name (e.g. include the hostname).
- Remove the stale runner from Settings > Actions > Runners if it lingers.
shell
./config.sh --url https://github.com/ORG/REPO --token TOKEN --name "runner-${HOSTNAME}" --replaceHow to prevent it
- Use unique, host-derived runner names.
- Deregister runners on host teardown.
Related guides
GitHub Actions "Runner registration failed: 404" (wrong URL or token)Fix self-hosted runner registration failing with HTTP 404, caused by a wrong repo/org URL or an invalid regis…
GitHub Actions "The self-hosted runner is offline"Fix jobs that never start because the targeted self-hosted runner is offline or disconnected.
GitHub Actions Self-Hosted Runner Registration Failed (config.sh)Fix self-hosted runner registration failures with config.sh - an expired registration token, a wrong URL/scop…