Elektrine lite

← Feed

@codebergstatus@social.anoxinon.de

2026-05-08 17:07 UTC

It has been in the works for months, but the recent increase of downtime has accelerated work. We've moved from Caddy to HAProxy for codeberg.org traffic. Starting over with a new reverse proxy has enabled us to make choices that enable us to set up HAProxy to scale with our increasing traffic. For example, traffic is split (when possible, decided via heuristics) over several instances to load balance expensive traffic. We hope to share more details at a later time about this change.

Replies (5)

  • You might've encountered a 504 error, which means Forgejo did not respond within a specified timeout (15s in most cases). When we used Caddy, we did not configure timeouts, and it would indefinitely wait for a request to finish. This is not ideal when Forgejo is under high load and gets increasingly more traffic. For HAProxy we have set a max amount of requests and timeouts to prevent (and possibly recover from) Forgejo from a state where it's overloaded and stops responding.

    Open ##5018722

  • @codebergstatus@social.anoxinon.de Yo dawg, I heard you like load balancing, so I balanced your load balancing so you can be highly available while you're highly available. 😜 (Aww, they edited their toot so this joke doesn't make sense any more. That's no fun!)

    Open ##5018736

  • @thomas@metalhead.club 2026-05-08 18:25

    @codebergstatus@social.anoxinon.de awesome! Thanks for working on this 💪

    Open ##5018737

  • @kev@fosstodon.org 2026-05-08 18:52

    @codebergstatus@social.anoxinon.de I'm trying to create some new repos as part of a migration but keep getting a 504 error - I assume that's because of this work?

    Open ##5018738

  • @melroy@mastodon.melroy.org 2026-05-16 01:15

    @codebergstatus@social.anoxinon.de expect more traffic now. Since Theo Browne featured you very positively recently. I bet you will get many more on-boarding soon. Edit: at least we all start donating now.

    Open ##5018742