![]() In order to solve the given problem, one should first of all try to add resources to the server, for example, RAM and to increase the number of HTTP processes in Apache. If they are not served in the established time, connection fails. It’s possible that the site workload has increased and Apache gets short of time to give HTTP-responses while the new requests keep gathering in line. ![]() So the essence of this problem is that Apache failed to respond. It should be admitted that 504 Gateway Timeout happens when nginx sends client Apache requests but Apache fails to return HTTP-response within the established limit of time. The problem is usually assigned to nginx and the latter gets strenuously cured. Web developers often observe this kind of mistake on the servers with nginx as the frontend and Apache as the backend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |