Last week we did a configuration change that should prevent 503 errors
on the Weblate. You should now see 503 only if the weblate server is
down for real. (But in case of high load, you may experience error 504
directly from weblate server, or error message in case of SQL server
Please let us know if you still see random 503 errors.
openSUSE servers use haproxy for data routing. haproxy has a monitor
feature. By default, haproxy monitors the home page.
But in case of Weblate-2.6, the home page contains list of all projects.
It requires number of database queries, and it requires a non trivial
time. It caused further increase of the load, resulting a late reply.
haproxy assumed that the server is down, and returned 503.