github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-21 07:01:20 -05:00
Code Issues 140 Packages Projects Releases 100 Wiki Activity

[GH-ISSUE #270] Migration Issue #1233

New Issue
Closed
opened 2026-04-21 23:14:13 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-21 23:14:13 -05:00
Owner
Copy Link

Originally created by @mattboston on GitHub (Apr 15, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/270

As mentioned in #260 I migrated to a new network and changed IPs. To fix that issue I added GITEA_URL=http://192.168.5.250:3000/ to my docker compose and that brought everything up. Once I logged back in, I went to one of the repos and told it to sync and I'm getting this in the Activity Log:

Operation failed
April 15, 2026 at 09:40 AM
Repo: reports

Pre-sync snapshot failed: git command failed: Cloning into bare repository '/tmp/gitea-mirror-backup-Yj3vks/repo.git'...
fatal: unable to access 'http://192.168.1.5:3000/mattboston/reports.git/': Failed to connect to 192.168.1.5 port 3000 after 9 ms: Could not connect to server

What's strange is some syncs for some of my other repos are successful. Both GH repos are mine, both Gitea repos are mine. It's like some of the Gitea Mirror repos cached the old IP.

Originally created by @mattboston on GitHub (Apr 15, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/270 As mentioned in #260 I migrated to a new network and changed IPs. To fix that issue I added `GITEA_URL=http://192.168.5.250:3000/` to my docker compose and that brought everything up. Once I logged back in, I went to one of the repos and told it to sync and I'm getting this in the Activity Log: ``` Operation failed April 15, 2026 at 09:40 AM Repo: reports Pre-sync snapshot failed: git command failed: Cloning into bare repository '/tmp/gitea-mirror-backup-Yj3vks/repo.git'... fatal: unable to access 'http://192.168.1.5:3000/mattboston/reports.git/': Failed to connect to 192.168.1.5 port 3000 after 9 ms: Could not connect to server ``` What's strange is some syncs for some of my other repos are successful. Both GH repos are mine, both Gitea repos are mine. It's like some of the Gitea Mirror repos cached the old IP.
GiteaMirror commented 2026-04-21 23:14:15 -05:00
Author
Owner
Copy Link

@mattboston commented on GitHub (Apr 16, 2026):

Closing ticket. Found the issue. I had also migrated my Forgejo server. It seems like it was caching the old ip (192.168.1.5). Once I added the following to that docker container, it worked.

      - FORGEJO__server__ROOT_URL=http://192.168.5.250:3000
      - FORGEJO__server__LOCAL_ROOT_URL=http://192.168.5.250:3000
      - FORGEJO__server__SSH_DOMAIN=192.168.5.250
      - FORGEJO__server__DOMAIN=192.168.5.250
      - FORGEJO__server__HTTP_PORT=3000
      - FORGEJO__server__PROTOCOL=http
<!-- gh-comment-id:4261624940 --> @mattboston commented on GitHub (Apr 16, 2026): Closing ticket. Found the issue. I had also migrated my Forgejo server. It seems like it was caching the old ip (192.168.1.5). Once I added the following to that docker container, it worked. ``` - FORGEJO__server__ROOT_URL=http://192.168.5.250:3000 - FORGEJO__server__LOCAL_ROOT_URL=http://192.168.5.250:3000 - FORGEJO__server__SSH_DOMAIN=192.168.5.250 - FORGEJO__server__DOMAIN=192.168.5.250 - FORGEJO__server__HTTP_PORT=3000 - FORGEJO__server__PROTOCOL=http ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#1233
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?