Could this be about https://core.trac.wordpress.org/ticket/39432 Symptoms look very similar and at the time of writing hasn’t been released as 4.7.3. Applying the patch manually fixed the issue on my nginx setup.
Maxmind no longer supports Geolite legacy, just Geolite2 : https://blog.maxmind.com/2018/01/02/discontinuation-of-the-geolite-legacy-databases/
The mistake is putting a server block inside a server block, you should close the main server block then open a new one for the sub domains
sudo nginx -t should test all files and return errors and warnings locations
Your code appears to be using a forward proxy (often just “proxy”), not reverse proxy and they operate quite differently. Reverse proxy is for server end and something client doesn’t really see or think about. It’s to retrieve content from the backend servers and hand to the client. Forward proxy is something the client sets … Read more
As stated by Maxim Dounin in the comments above: When nginx returns 400 (Bad Request) it will log the reason into error log, at “info” level. Hence an obvious way to find out what’s going on is to configure error_log to log messages at “info” level and take a look into error log when testing.
175 43 I have Puma running as the upstream app server and Riak as my background db cluster. When I send a request that map-reduces a chunk of data for about 25K users and returns it from Riak to the app, I get an error in the Nginx log: upstream timed out (110: Connection timed … Read more
I try to start this service but i can´t, the error below occur: