504 Gateway Time-out nginx
I got a "series of 504 Gateway Time-out"s during the recent minutes.
Server was overloaded at 13.38 CEST and got better by 13.41. I suggest to avoid doing expensive things like opening many tabs or using Special:SearchTranslations intensively. Can you defer your mass-reporting till after the translation rally?
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in the group: Users.
You can view and copy the source of this page.Purodha Blissenbach (talk)
I've closed this issue. The time-outs are related to a lack of server resources, mainly because ElastisSearch is enormously CPU hungry. We are in the process of requesting more computing resources from our hosting sponsor netcup.de. If we get the requested resources, we can upgrade our current installation to be much quicker...