• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Gateway timeout

cits

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian Web Admin Se Edition Version 18.0.61 Update #5
I am using an aws cloud instance with latest plesk obsidian to run some wordpress websites. One of the website has about 30gb of contents. Currently I am getting was Gateway timeout from nginx. After searching for some fixes, found Issue - Prestashop 8 : very slow and error "504 Gateway Time-out - Nginx" and I stopped nginx. For every restart of apache, the site runs for some minutes and then get the gateway timeout error
 
Probably too many requests are sent to the web server so that it is getting slower and slower with every new request. You can
a) Check the access_log of the web server whether bad bots are hitting the website. Block them.
b) Check the number of PHP-FPM instances that are created (ps aux | grep php-fpm). If there are many for your website, but (a) has already been ruled out, reduce the max script runtime in the PHP settings drastically (e.g. to only 5 seconds), as there seem to be long running scripts in your website.
c) Make sure that your shop can access resources fast. If the shop has to wait on resources, many additional PHP-FPM instances can build-up which will again result in the webserver to become unresponsive. Does the shop wait on responses from external sources for example?
 
Back
Top