Cannot push/pull to freshly migrated Gitea #5020

Closed
opened 2025-11-02 06:11:08 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @netorica on GitHub (Mar 7, 2020).

  • Gitea version (or commit ref):
  • Git version: 1.11.1
  • Operating system: Ubuntu
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I have successfully migrated my gitea to another server following the documentation here
https://docs.gitea.io/en-us/backup-and-restore/

The old and new server has not software difference except that the new server has bigger disk space and a additional 8GB memory from the old one.

Now I am facing issues with pushing to git repositories that i have an access to push and pull before.

I was able to push to pull/push when i have just delete and reinsert again my old pub key. I am worrying about my other 12 users that cannot push or pull anymore as 5 of them are servers. Is there a possible way that the keys can someone be refreshed internally?

The paths are not different at all, everything is almost the same even the migrated gitea version

Any ideas that could help solve my issues?

Thanks
...

Screenshots

Originally created by @netorica on GitHub (Mar 7, 2020). - Gitea version (or commit ref): - Git version: 1.11.1 - Operating system: Ubuntu - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I have successfully migrated my gitea to another server following the documentation here https://docs.gitea.io/en-us/backup-and-restore/ The old and new server has not software difference except that the new server has bigger disk space and a additional 8GB memory from the old one. Now I am facing issues with pushing to git repositories that i have an access to push and pull before. I was able to push to pull/push when i have just delete and reinsert again my old pub key. I am worrying about my other 12 users that cannot push or pull anymore as 5 of them are servers. Is there a possible way that the keys can someone be refreshed internally? The paths are not different at all, everything is almost the same even the migrated gitea version Any ideas that could help solve my issues? Thanks ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/stale label 2025-11-02 06:11:08 -06:00
Author
Owner

@guillep2k commented on GitHub (Mar 7, 2020):

Please migrate to 1.11.2 (out as of yesterday), there are critical bugfixes that probably affect your issue.

@guillep2k commented on GitHub (Mar 7, 2020): Please migrate to 1.11.2 (out as of yesterday), there are critical bugfixes that probably affect your issue.
Author
Owner

@zeripath commented on GitHub (Mar 8, 2020):

Following that you will likely need to do the Resynchronise Hooks task from the admin settings page.

@zeripath commented on GitHub (Mar 8, 2020): Following that you will likely need to do the Resynchronise Hooks task from the admin settings page.
Author
Owner

@stale[bot] commented on GitHub (May 7, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 7, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (May 22, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (May 22, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5020