Good morning. I’m running a self‑hosted Gitea instance in a Docker container on my server. One of my repositories has a Mirror Configuration enabled to sync with an external repository on Codeberg (https://codeberg.org). The sync worked flawlessly for almost a year. However, after updating my Gitea Docker container to version 1.26.2, the synchronization stopped working. I now get the following error in Gitea:
push failed: fatal: unable to access 'https://codeberg.org/[domain]/[reponame].git/':
TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
fatal: unable to access 'https://codeberg.org/[domain]/[reponame].git/':
TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
I contacted Codeberg to check whether the issue was on their side, but they confirmed that nothing has changed on their end in the past month. They also pointed out that “your Git push is failing because the TLS/SSL connection to Codeberg is being interrupted before the handshake completes. This is almost never a Codeberg problem.” . They are probably right, especially since the issue started immediately after updating Gitea to version 1.26.2.
I also have other repositories mirrored to GitHub, and those mirrors continue to work normally, both before and after the update to version 1.26.2.
Does anyone have an idea what might be causing this? Any help would be greatly appreciated.
Thanks in advance.
BIG PANIC!
This morning I noticed that Gitea version 1.26.3 had been released, so I immediately updated my Docker container. After the upgrade, I discovered that I can no longer access about half of my repositories. Instead, I’m greeted with the following error:
Code
500 Internal Server Error - An error occurred: GetCommitsInfo, read |0: file already closed
The same message appears in the Docker logs:
Code
2026-06-21T09:52:10.167973365Z [con_Gitea] 2026/06/21 09:52:10 HTTPRequest [I] router: completed GET /[owner]/[reponame] for [192.168.0.1:52403]:0, 500 Internal Server Error in 1363.8ms @ repo/view_home.go:389(repo.Home)
2026-06-21T09:53:44.305241694Z [con_Gitea] 2026/06/21 09:53:44 HTTPRequest [I] router: completed GET / for [192.168.0.1:55177]:0, 200 OK in 9.9ms @ web/home.go:32(web.Home)
On top of that, the mirroring to Codeberg is still failing.
So at the moment, not only is mirroring broken, but half of my repositories are completely inaccessible. Today is Sunday, so my colleagues might not notice yet, but tomorrow everyone will need access. I really need help.
Hi again. Version 1.26.4 is now installed, which resolved the issue with repositories that were previously not visible; thanks for your help there. However, the problem with mirroring to Codeberg persists. I just tested this also using a newly generated Codeberg Access Token, but the error message remains exactly the same as before. Additionally, when testing repositories that mirror to GitHub, those work correctly, it seems isolated only to Codeberg. Do you have any ideas on what might be causing this? Thanks again for your assistance.
@delvh: Yes, I know that Codeberg uses Forgejo, but that is not the point; it is still Git. This does not explain why mirroring worked without issues for almost a year and suddenly stopped after updating Gitea to 1.26.2 (and now 1.26.4). It also fails to address why mirroring with GitHub works fine, but mirroring to Codeberg does not.
