Process: 8883 ExecStop=/sbin/start-stop-daemon -quiet -stop -retry QUIT/5 -pidfile /run/nginx.
Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Sun 12:35:25 UTC 16min ago This is the nginx status: rvice - A high performance web server and a reverse proxy server Proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for # Include the SSL configuration from cipherli.st Ssl_certificate_key /etc/letsencrypt/live//privkey.pem Ssl_certificate /etc/letsencrypt/live//fullchain.pem # HTTPS - proxy all requests to the Node app Let us deal the firewall problem separately so that it won’t affect website performance. I am getting 504 timeouts message from nginx when my PHP script is running longer than usual.
Firewall configuration fault fix: Firewall configuration may also be the hidden reason for 504 errors. Prevent nginx 504 Gateway timeout using PHP settimelimit(). So I have nginx reverse proxy for a node js app. To make changes in Nginx webserver select the file by redirecting to the pathway /etc/nginx/nf. 3 12:37:32 9128#9128: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 84.253.220.134, server:, request: "GET / HTTP/2.0", upstream: "", host: "" Nginx 504 Gateway Timeout HTTP 504 504 Error Gateway Timeout(504) A blank white screen What are the Causes and Fixes for 504 Gateway timeout Error From where you should start troubleshooting the error Without prior understanding of the error, you will be caught in a vicious circle troubleshooting, looking here and there to find the cause. After re-installing the ssl certs from let’s encrypt, nginx gave me 504 gateway-timeout. The autorenew of my SSL certificate failed for some unknown reason.