And, by sheer coincidence, a #forgejo security release was scheduled for today, which now cannot be distributed as long as codeberg.org is not reachable.
So, if you run forgejo with the internal ssh server enabled, switch that off until the fix can be installed.
"We therefore currently recommend that, if you are using the internal SSH server (Docker with ssh.START_SSH_SERVER = true), you disable it for the time being or prevent access to it."
https://floss.social/@forgejo/117636334439245475
Open quoted post Quoting
Attention: A #Forgejo security release is scheduled for today. The patches were temporarily publicly accessible as part of the release process. Due to urgent issues with #Codeberg, we are unable to proceed with the release. We are in contact with Codeberg and are working to find a solution.
We therefore currently recommend that, if you are using the internal SSH server (Docker with ssh.START_SSH_SERVER = true), you disable it for the time being or prevent access to it.
#forgejorelease
Open quoted post