Migrate From Gitea not working for me #6177

Closed
opened 2025-11-02 06:47:09 -06:00 by GiteaMirror · 32 comments
Owner

Originally created by @airdogvan on GitHub (Oct 20, 2020).

Already have a working Gitea site. Trying to mirror some repositories to new instance via Migrate.

Both source and destination: (different machines and urls)
Git version 1.14.0+dev-33 running on docker (Ubuntu)

Steps:

  • New migration
  • Gitea
  • https url of existing repo
  • Access token (generated on source instance (setting, generate token)

Click on Migrate Repository
New screen comes with animated cup of tea.
Migration failed.
image

Originally created by @airdogvan on GitHub (Oct 20, 2020). Already have a working Gitea site. Trying to mirror some repositories to new instance via Migrate. Both source and destination: (different machines and urls) Git version 1.14.0+dev-33 running on docker (Ubuntu) Steps: - New migration - Gitea - https url of existing repo - Access token (generated on source instance (setting, generate token) Click on Migrate Repository New screen comes with animated cup of tea. **Migration failed.** ![image](https://user-images.githubusercontent.com/31630759/96649622-5b642580-12e6-11eb-8b31-6143751e184c.png)
GiteaMirror added the type/bug label 2025-11-02 06:47:09 -06:00
Author
Owner

@techknowlogick commented on GitHub (Oct 20, 2020):

Are you able to provide relevant logs?

@techknowlogick commented on GitHub (Oct 20, 2020): Are you able to provide relevant logs?
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

2020/10/20 17:05:17 Completed GET /user/events 200 OK in 24.188209361s
2020/10/20 17:05:17 Started POST /repo/migrate for 172.21.0.1
2020/10/20 17:05:17 Completed POST /repo/migrate 302 Found in 125.179689ms
2020/10/20 17:05:17 Started GET /user/samba for 172.21.0.1
2020/10/20 17:05:17 Completed GET /user/samba 200 OK in 8.662384ms
2020/10/20 17:05:18 Started GET /user/avatar/userx/-1 for 172.21.0.1
2020/10/20 17:05:18 Completed GET /user/avatar/userx/-1 302 Found in 3.69346ms
2020/10/20 17:05:18 Started GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng for 172.21.0.1
2020/10/20 17:05:18 Completed GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng 200 OK in 12.861725ms
2020/10/20 17:05:18 Started GET /manifest.json for 172.21.0.1
2020/10/20 17:05:18 Completed GET /manifest.json 200 OK in 1.64126ms
2020/10/20 17:05:18 Started GET /user/events for 172.21.0.1
2020/10/20 17:05:19 modules/task/task.go:51:handle() [E] Run task failed: 404 Not Found
2020/10/20 17:05:19 Started GET /serviceworker.js for 172.21.0.1
2020/10/20 17:05:19 ...les/public/public.go:156:handle() [I] [Macaron] [Static] Serving /serviceworker.js
2020/10/20 17:05:19 Completed GET /serviceworker.js 304 Not Modified in 181.654µs
2020/10/20 17:05:20 Started GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng for 172.21.0.1
2020/10/20 17:05:20 Completed GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng 404 Not Found in 6.652601ms

I did provide the correct repo url (double checked both in browser and from cli with git clone.

@airdogvan commented on GitHub (Oct 21, 2020): 2020/10/20 17:05:17 Completed GET /user/events 200 OK in 24.188209361s 2020/10/20 17:05:17 Started POST /repo/migrate for 172.21.0.1 2020/10/20 17:05:17 Completed POST /repo/migrate 302 Found in 125.179689ms 2020/10/20 17:05:17 Started GET /user/samba for 172.21.0.1 2020/10/20 17:05:17 Completed GET /user/samba 200 OK in 8.662384ms 2020/10/20 17:05:18 Started GET /user/avatar/userx/-1 for 172.21.0.1 2020/10/20 17:05:18 Completed GET /user/avatar/userx/-1 302 Found in 3.69346ms 2020/10/20 17:05:18 Started GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng for 172.21.0.1 2020/10/20 17:05:18 Completed GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng 200 OK in 12.861725ms 2020/10/20 17:05:18 Started GET /manifest.json for 172.21.0.1 2020/10/20 17:05:18 Completed GET /manifest.json 200 OK in 1.64126ms 2020/10/20 17:05:18 Started GET /user/events for 172.21.0.1 2020/10/20 17:05:19 modules/task/task.go:51:handle() [E] Run task failed: 404 Not Found 2020/10/20 17:05:19 Started GET /serviceworker.js for 172.21.0.1 2020/10/20 17:05:19 ...les/public/public.go:156:handle() [I] [Macaron] [Static] Serving /serviceworker.js 2020/10/20 17:05:19 Completed GET /serviceworker.js 304 Not Modified in 181.654µs 2020/10/20 17:05:20 Started GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng for 172.21.0.1 2020/10/20 17:05:20 Completed GET /user/samba/status?_csrf=df8zVeNob7xHGSM4sHyZTtNHxpI6MTYwMzIzODYzMjg5NjkyMTQ4Ng 404 **Not Found** in 6.652601ms I did provide the correct repo url (double checked both in browser and from cli with git clone.
Author
Owner

@techknowlogick commented on GitHub (Oct 21, 2020):

These are the web requests, but we need to see what is going on with Gitea itself. Here is a guide on how to enable that information via logging: https://docs.gitea.io/en-us/logging-configuration/#debugging-problems

@techknowlogick commented on GitHub (Oct 21, 2020): These are the web requests, but we need to see what is going on with Gitea itself. Here is a guide on how to enable that information via logging: https://docs.gitea.io/en-us/logging-configuration/#debugging-problems
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

@airdogvan in general if a migration has a problem ... you should find the reason in System Notices (lhttp://localhost:3000/admin/notices)

just "Delete All Notices" and try migration again, now it should pop up with the reason - this one we need ...

or if the repo you try to migrate is public, it would be nice if you can share it with us so we can test too :)

@6543 commented on GitHub (Oct 21, 2020): @airdogvan in general if a migration has a problem ... you should find the reason in **System Notices** (lhttp://localhost:3000/admin/notices) just "Delete All Notices" and try migration again, now it should pop up with the reason - this one we need ... or if the repo you try to migrate is public, it would be nice if you can share it with us so we can test too :)
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

give me a moment, as said running docker here, what I posted was the result of docker logs. When I go inside the container, nothing in the log direcoty

@airdogvan commented on GitHub (Oct 21, 2020): give me a moment, as said running docker here, what I posted was the result of docker logs. When I go inside the container, nothing in the log direcoty
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

no notifs to clear

@airdogvan commented on GitHub (Oct 21, 2020): no notifs to clear
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

and according to docs, if logs not started in running system, have to restart to get logs...
which seems to be the case for gitea docker containers

@airdogvan commented on GitHub (Oct 21, 2020): and according to docs, if logs not started in running system, have to restart to get logs... which seems to be the case for gitea docker containers
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

if you got the info to my site, can I delete that post?

@airdogvan commented on GitHub (Oct 21, 2020): if you got the info to my site, can I delete that post?
Author
Owner

@techknowlogick commented on GitHub (Oct 21, 2020):

and according to docs, if logs not started in running system, have to restart to get logs...

correct. any config change to app.ini requires a restart of the binary (slight note: there are CLI commands that don't make this 100% accurate)

@techknowlogick commented on GitHub (Oct 21, 2020): > and according to docs, if logs not started in running system, have to restart to get logs... correct. any config change to app.ini requires a restart of the binary (slight note: there are CLI commands that don't make this 100% accurate)
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

@airdogvan I can confirm this bug and it do not log an error at all, witch should not be the case

@6543 commented on GitHub (Oct 21, 2020): @airdogvan I can confirm this bug and it do not log an error at all, witch should not be the case
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

only notices in /admin/notices are about cron

@airdogvan commented on GitHub (Oct 21, 2020): only notices in /admin/notices are about cron
Author
Owner

@techknowlogick commented on GitHub (Oct 21, 2020):

@airdogvan your instance is running a development version from august, are you able to update to the latest RC for 1.13?

@techknowlogick commented on GitHub (Oct 21, 2020): @airdogvan your instance is running a development version from august, are you able to update to the latest RC for 1.13?
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

as said this is docker, just pulled the most recent image 2 hours ago
image: gitea/gitea:latest

@airdogvan commented on GitHub (Oct 21, 2020): as said this is docker, just pulled the most recent image 2 hours ago image: gitea/gitea:latest
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

@techknowlogick do we have an issue on the docker side too?

@6543 commented on GitHub (Oct 21, 2020): @techknowlogick do we have an issue on the docker side too?
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

you don't need my site anymore right, made the repo private again... if that's ok

@airdogvan commented on GitHub (Oct 21, 2020): you don't need my site anymore right, made the repo private again... if that's ok
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

note: pure git migration works, gitea without options don't!

@6543 commented on GitHub (Oct 21, 2020): note: pure git migration works, gitea without options don't!
Author
Owner

@techknowlogick commented on GitHub (Oct 21, 2020):

If you go to /api/v1/version it says 1.13.0+dev-404-g4e1c7cc4e is the version which is a commit from august 12. Is there any caching with your docker images? try.gitea.io checks every 5 minutes for a new image and updates it. and the latest image is reporting 1.14.0+dev-36-gb9850375f as the version.

@techknowlogick commented on GitHub (Oct 21, 2020): If you go to `/api/v1/version` it says `1.13.0+dev-404-g4e1c7cc4e` is the version which is a commit from august 12. Is there any caching with your docker images? try.gitea.io checks every 5 minutes for a new image and updates it. and the latest image is reporting `1.14.0+dev-36-gb9850375f ` as the version.
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

@airdogvan I'd like to test against this if I'm allowed to - you can make it private and add me as colaborator with read access :)

@6543 commented on GitHub (Oct 21, 2020): @airdogvan I'd like to test against this if I'm allowed to - you can make it private and add me as colaborator with read access :)
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

who do I add 6543?

@airdogvan commented on GitHub (Oct 21, 2020): who do I add 6543?
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

@airdogvan https://git/proj/settings/collaboration

@6543 commented on GitHub (Oct 21, 2020): @airdogvan https://git/proj/settings/collaboration
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

yes I know but I need to know who to add...
you can send details at airdogvan@mailinator.com

@airdogvan commented on GitHub (Oct 21, 2020): yes I know but I need to know who to add... you can send details at airdogvan@mailinator.com
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

@airdogvan created an account -> https://git/6543

@6543 commented on GitHub (Oct 21, 2020): @airdogvan created an account -> https://git/6543
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

or do I just add 6543?

@airdogvan commented on GitHub (Oct 21, 2020): or do I just add 6543?
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

done

@airdogvan commented on GitHub (Oct 21, 2020): done
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

thx - I'll try to find the issue :)

@6543 commented on GitHub (Oct 21, 2020): thx - I'll try to find the issue :)
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

would be grateful if you removed public references to my site...

@airdogvan commented on GitHub (Oct 21, 2020): would be grateful if you removed public references to my site...
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

thanks

@airdogvan commented on GitHub (Oct 21, 2020): thanks
Author
Owner

@airdogvan commented on GitHub (Oct 21, 2020):

ok I'll leave you to it. Let me know if I can do something to help.

And thanks so much for the prompt reaction...

@airdogvan commented on GitHub (Oct 21, 2020): ok I'll leave you to it. Let me know if I can do something to help. And thanks so much for the prompt reaction...
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

gitea version: 1.13.0+dev-404-g4e1c7cc4e as source - who fail to migrate

@6543 commented on GitHub (Oct 21, 2020): gitea version: `1.13.0+dev-404-g4e1c7cc4e` as source - who fail to migrate
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

found two issues ...

@6543 commented on GitHub (Oct 21, 2020): found two issues ...
Author
Owner

@6543 commented on GitHub (Oct 21, 2020):

... #13229 <- if you are in the middle of nowere checking version makes no sence ...
... #13230 <- error is not getting loged

@6543 commented on GitHub (Oct 21, 2020): ... #13229 <- if you are in the middle of nowere checking version makes no sence ... ... #13230 <- error is not getting loged
Author
Owner

@airdogvan commented on GitHub (Oct 22, 2020):

going to have to wait till a new docker image is online, just pulled a minute ago and same version as yesterday...

@airdogvan commented on GitHub (Oct 22, 2020): going to have to wait till a new docker image is online, just pulled a minute ago and same version as yesterday...
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6177