Im going to mark this as resolved, but if you still see issues in the coming days, feel free to bump this and contact us through our support channels. I want to apologize for any inconvenience this may have caused and we appreciate you reporting this issue and bringing it to our attention. Since it is an HTTP status code, that means it is being thrown by a web server. After a few hours of monitoring everything looks good and we’re now considering this issue resolved. The 504 Gateway timeout is an HTTP status code. The issue has been addressed by our team and they have deployed a fix. Instead of just affecting the sites or customers who were making these bad requests, it put unforseen pressure on all of our servers, causing them to error out as you were seeing on occasion. Our team did some investigating and was able to isolate the issue to a misconfiguration with how we setup our NGINX servers (part of our hosting stack) to terminate bad requests. The error may be a temporary occurrence due to too much traffic toward the server or site. I wanted to update you on the issues you reported around the intermittent 504 errors. The 504 (Gateway Timeout) status code indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request. Hay varias razones por las que el servidor puede estar experimentando un timeout. Sea cual sea el caso, visitante o administrador, hay que saber reaccionar ante tal problema. En efecto, se trata de un error del servidor. Josh here, from the Webflow Engineering Management Team. 504 gateway timeout es un error cuya resolución suele estar fuera del alcance del visitante del sitio web.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |