@codebergstatus@social.anoxinon.de
2026-05-08 17:07 UTC
Replies (5)
-
@codebergstatus@social.anoxinon.de 2026-05-08 19:37
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.
-
@argv_minus_one@mastodon.sdf.org 2026-05-08 17:10
@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!)
-
@thomas@metalhead.club 2026-05-08 18:25
@codebergstatus@social.anoxinon.de awesome! Thanks for working on this 💪
-
@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?
-
@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.