// troubleshooting guide · gitea
Gitea Migration From GitHub Failed or Timed Out
- Status
- Workaround available
- platforms:
- Self-hosted
- updated:
- November 16, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · gitea/migration-failed4 FIXES
// quick answer
Use a valid token, handle GitHub rate limits and check server memory. A Failed status can still have copied files, so inspect before retrying.
Most likely fix: Use a proper token
How to fix it
// try these in order, the most common fix is first
FIX 1Use a proper token
- 01Create a GitHub token with repo access
- 02Paste it in the migration form
Did this fix it?FIX 2Handle rate limits
- 01Use multiple tokens on a recent Gitea version
- 02Migrate in smaller batches
Did this fix it?FIX 3Fix killed clones
- 01Check server memory and timeouts
- 02Read the migration error in Gitea's log
Did this fix it?FIX 4Check before retrying
- 01Inspect whether the repository was partially created
- 02Delete or rename it if you get a name conflict
Did this fix it?
SANDBOX · gitea RUNS IN YOUR BROWSER
Try it: push, review, run CI and merge in a code host and cloud workspace
A hands-on Gitea-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
Migration shows Failed, authentication failed, Clone: signal: killed, fatal: early EOF, or runs very slowly.
Why it happens
- C-01GitHub API rate limits on large repos with issues and PRs
- C-02Invalid or under-scoped token
- C-03Server killed the clone (low memory)
- C-04Repository name already exists (409)
// this guide also covers
- migrate github to gitea failed
- gitea migration timeout
- gitea clone signal killed
Still not working?
If Gitea keeps failing, you're not alone. See every Gitea problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Gitea errors
- Gitea Actions Jobs Stuck in Waiting (No Matching Runner)
- Gitea SSH Permission Denied (publickey) or Connection Refused
- Gitea 500 Internal Server Error
- Gitea Reverse Proxy Wrong URLs or Redirect Loop (ROOT_URL)
- Gitea Push 413 Request Entity Too Large (LFS Upload Fails)
- Gitea Webhook Not Working (ALLOWED_HOST_LIST Error)
- Gitea Email Notifications Not Sending (SMTP Error)
- Why Is Gitea Using So Much Memory or CPU?