I finally found out the root cause of the problem. I initially installed
wordpress by accessing the server directly using its IP address (when
the DNS was not up and running yet). Apparently, wordpress decides to
save that into its database and serves the links based on that...
I deleted the w
Hi Francis,
You are right, most links in the wordpress html start with
"http://92.222.75.87/..."; so that's the problem.
I'll try to get that fixed.
Many thanks for your help!
Fabrice
On 27/06/17 00:16, Francis Daly wrote:
On Mon, Jun 26, 2017 at 06:24:50PM +0100, Fabrice Triboix wrote:
On Mon, Jun 26, 2017 at 06:24:50PM +0100, Fabrice Triboix wrote:
Hi 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: 9
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
h
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 "ret
Hello,
I am trying to use nginx to reverse-proxy a wordpress website. The
wordpress website works fine when being accessed without nginx in the
middle.
The problem I am having is that when accessing the home page (which is
about 50k of html alone), nginx responds with "503 Service Temporaril
