• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Two site running server - 504 Gateway Time-out

Hajime Tanaka

Regular Pleskian
We running on VPS Server,
12GB RAM
Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz (4 core(s))
CentOS 7.4 - Core
SSD

We created domain site is large.
We getting error "504 Gateway Time-out" from nginx. We have enabled Nginx and Apache, HTTP2.
 
Nope, Doesn't work. It is still error.
Code:
2018/02/13 02:37:29 [error] 1680#0: *4845 upstream timed out (110: Connection timed out) while reading response header from upstream, client: IPADDRESS, server: unknown.com, request: "GET / HTTP/1.0", upstream: "http://IPADDRESS:7080/", host: "www.unknown.com"
 
Nope, Doesn't work. It is still error.
Code:
2018/02/13 02:37:29 [error] 1680#0: *4845 upstream timed out (110: Connection timed out) while reading response header from upstream, client: IPADDRESS, server: unknown.com, request: "GET / HTTP/1.0", upstream: "http://IPADDRESS:7080/", host: "www.unknown.com"

Your issue is related to Apache, Nginx display an error 504 because Apache was not available. Try to check apache error_logs to see if there are additional info.
 
Your issue is related to Apache, Nginx display an error 504 because Apache was not available. Try to check apache error_logs to see if there are additional info.
There,
error_logs
Code:
[Tue Feb 13 02:09:41.803669 2018] [proxy:error] [pid 30923:tid 140100247693056] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/www/vhosts/system/unknown.com/php-fpm.sock (*) failed
[Tue Feb 13 02:09:41.803721 2018] [proxy_fcgi:error] [pid 30923:tid 140100247693056] [client 108.162.215.193:43820] AH01079: failed to make connection to backend: httpd-UDS, referer: https://www.unknown.com/
[Tue Feb 13 02:16:07.801850 2018] [proxy_fcgi:error] [pid 1432:tid 140593095157504] (70007)The timeout specified has expired: [client 141.101.88.127:45152] AH01075: Error dispatching request to :
[Tue Feb 13 02:16:09.055854 2018] [proxy_fcgi:error] [pid 1432:tid 140593367176960] (70007)The timeout specified has expired: [client 108.162.212.206:45156] AH01075: Error dispatching request to :, referer: http://queuecosm.bid/-36695BKHZ/2I5t?rndad=3130484029-1518484469
[Tue Feb 13 20:32:55.278315 2018] [ssl:warn] [pid 16558:tid 139977020299392] AH01909: RSA certificate configured for unknown.com:443 does NOT include an ID which matches the server name
 
Back
Top