Plesk for Linux
kb: technical
Applicable to:
- Plesk for Linux
Symptoms
- The website example.com uses a PHP script and shows a
502 Bad Gateway
error when opened via a browser. - The following error is recorded in Domains > example.com > Logs or in
/var/www/vhosts/example.com/logs/error_log
file when reproducing the issue:
CONFIG_TEXT: AH01075: Error dispatching request to : (polling)
Cause
The website's PHP code is taking too long to execute and exceeds the currently configured default timeout limit.
Resolution
Increase the PHP timeout limits:
2. Add the following lines to Domains > example.com > PHP Settings > Additional configuration directives:
CONFIG_TEXT: fastcgi_send_timeout 120s;
fastcgi_read_timeout 120s;
Or increase the values if they are already configured
Comments
1 comment
One of my sites today out of nowhere stopped responding to http requests. Plesk panel and other sites on same server would load fine.
I tried disabling cloudflare, restarting apache and nginx, nothing seem to help.
It worked after I .. refreshed the config a bit by going to that domain settings, changing FTP password and saving. I am sure the password was not related, but it saved the config for that domain in Plesk and that fixed it.
This could be a more serious issue with plesk and I am not sure what caused it.
When this happen, I was editing some PHP pages from the site, pages that used an over average amount of memory (2-3 GB). But I was not changing anything in plesk config or site settings, db, etc.
Maybe some Plesk helper scripts stop working when running PHP pages with higher timeout or higher memory usage, and maybe saving a new site FTP password restarted some plesk helper scripts.
Please sign in to leave a comment.