On Tuesday 08 Nov 2016 13:06:32 Alan McKinnon wrote:
> On 08/11/2016 10:48, Peter Humphrey wrote:
> > On Monday 07 Nov 2016 12:17:05 Poison BL. wrote:
> >> From the configuration in the aforementioned guide:
> >>
> >> server {
> >>
> >> listen 127.0.0.1;
> >> server_name localhost;
> >>
> >> access_log /var/log/nginx/localhost.access_log main;
> >> error_log /var/log/nginx/localhost.error_log info;
> >>
> >> root /var/www/localhost/htdocs;
> >>
> >> }
> >>
> >> This specifically instructs nginx to listen only on 127.0.0.1, so even
> >> connections from the same machine to its hostname or external IP
> >> address will not hit nginx there. You'll need to change the 'listen'
> >> value to determine what connections it should be answering. See the
> >> nginx documetation on that here:
> >>
> >> http://nginx.org/en/docs/http/ngx_http_core_module.html#listen
> >>
> >> I would suspect for your internal network use-case, you'll want:
> >> listen *:80;
> >
> > Yes, but for two things:
> >
> > 1. With links on the same host I specified http://localhost, and
> > localhost
> > resolves to 127.0.0.1.
> >
> > 2. I made the change you recommended and it didn't help.
>
> you restarted nginx?
Yes, as I said just now. But I've just found I had an old alias for links in
place. That's what snookered me. It's working okay now, I think.
Sorry about the noise.
--
Regards
Peter
