Hi Francis,
Thanks a lot for spotting that! I redirected the log for that one to an
`access503.log` file, and indeed I can see requests are sent there.
I looked again at the requests from the browser (chrome), and I can see
something peculiar: the requests for "/" and "/favicon.ico" have a
header "Host: incise.co"; however the other requests have a header
"Host: 92.222.75.87". That's really weird... Could that be the cause of
the problem? If yes, how come the browser sends the IP address for the
"Host" header, which is after all meant to allow servicing different
domains on the same IP address?
Thank you so much for your help!
Fabrice
On 26/06/17 17:26, Francis Daly wrote:
On Mon, Jun 26, 2017 at 12:37:46PM +0100, Fabrice Triboix wrote:
Hi there,
The problem I am having is that when accessing the home page (which
is about 50k of html alone), nginx responds with "503 Service
Temporarily Unavailable" responses.
You have a separate server{} block that does "return 503;" and writes
to the same log file.
Is there any chance that *that* is the server that is handling these
subsequent requests?
If you do one of:
* remove that server{}
* change it to "return 502;"
* change it to log to access503.log
and reload your nginx, do you see any evidence that your "server_name
incise.co;" server is not doing what you want?
f
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
