Plesk for Linux
kb: technical
ABT: Group A
Applicable to:
- Plesk for Linux
Symptoms
-
A website is not accessible. The following error is shown in a browser:
504 Gateway Time-out
-
The following error message can be found in the domain error log file
/var/www/vhosts/example.com/logs/error_log:[proxy_fcgi:error] [pid 42290:tid 140458047010560] (70007)The timeout specified has expired: [client 203.0.113.2:54693] AH01075: Error dispatching request to :, referer: http://example.com/gallery
-
The following error message can also be found in the domain proxy error log file
/var/www/vhosts/example.com/logs/proxy_error_log:[error] 2766#0: *19950 upstream timed out (110: Connection timed out) while connecting to upstream, client: 203.0.113.3, server: example.com, request: "GET / HTTP/2.0", upstream: "https://203.0.113.2:7081/", host: "example.com"
Cause
Website misconfiguration.
Resolution
- Connect to the server using SSH.
- Run the following command to rebuild domain configuration files:
# plesk repair web example.com
Comments
2 comments
It doesn't help to us. We found after days of searching possible cause in cron job for Magento 2.3. Plesk runs new cron job as "root" (if you put task inside) and cron job task change files/directory permission by deleting cache in folder for example to "root" folder permission. After that an application cant access to the files with root permission. Problem is because admin cant add task in the name of other system user named by subscription in Plesk. And files in application needs such rights and groups in Magento 2.3. Solution is changing task which correct files permissions on the end of processing but easier would be if we can add cron jobs via admin in the name of subscription user. It seems Magento 1.9 can read from root cache folder but Magento 2.3 wont.
None of this works, and this is causing me getting all my clients fully angry !
Please sign in to leave a comment.