• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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