A high traffic site that I haven’t touched for about 4 months recently started spitting 504 Gateway Time-out Errors.
Problem is that I don’t have the machine I originally developed this site on, so I’m trying to fix it manually before I get Trellis all setup again.
The error is:
upstream timed out (110: Connection timed out) while reading response header from upstream, client: 188.8.131.52, server: 184.108.40.206, request: "POST /ebook/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-wordpress.sock", host: "220.127.116.11", referrer: "http://18.104.22.168/ebook/"
Probably worth noting that the easiest way to replicate this error is to put an email in on the /ebook/ page (which is using gravity forms). Since I don’t have the site cloned to my computer yet, I’m just making manual changes to the staging server.
Here’s what I’ve tried so far:
- Turning off all plugins (except Gravity Forms, because the site works fine when not using Gravity Forms)
- Restarting Server
- Restarting nginx
- Restarting php7.1-fpm
- Manually editing and increasing buffers: fastcgi_buffers 16 16k;
& fastcgi_buffer_size 32k;
- Restarting nginx, php-fpm, and entire server
fastcgi_read_timeout 600s;to nginx.config html block (right underneath the fastcgi buffer sizes).
Since this site is fairly high traffic, I need to resolve this asap and willing to pay for a consult if needed. Thanks!
Most circulated related articles/resources I’ve tried out: