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.
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.
<!-- 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
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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: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.
@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.