1 |
On 08/11/2016 10:48, Peter Humphrey wrote: |
2 |
> On Monday 07 Nov 2016 12:17:05 Poison BL. wrote: |
3 |
> |
4 |
>> From the configuration in the aforementioned guide: |
5 |
>> |
6 |
>> server { |
7 |
>> listen 127.0.0.1; |
8 |
>> server_name localhost; |
9 |
>> |
10 |
>> access_log /var/log/nginx/localhost.access_log main; |
11 |
>> error_log /var/log/nginx/localhost.error_log info; |
12 |
>> |
13 |
>> root /var/www/localhost/htdocs; |
14 |
>> } |
15 |
>> |
16 |
>> This specifically instructs nginx to listen only on 127.0.0.1, so even |
17 |
>> connections from the same machine to its hostname or external IP |
18 |
>> address will not hit nginx there. You'll need to change the 'listen' |
19 |
>> value to determine what connections it should be answering. See the |
20 |
>> nginx documetation on that here: |
21 |
>> |
22 |
>> http://nginx.org/en/docs/http/ngx_http_core_module.html#listen |
23 |
>> |
24 |
>> I would suspect for your internal network use-case, you'll want: |
25 |
>> |
26 |
>> listen *:80; |
27 |
> |
28 |
> Yes, but for two things: |
29 |
> |
30 |
> 1. With links on the same host I specified http://localhost, and localhost |
31 |
> resolves to 127.0.0.1. |
32 |
> |
33 |
> 2. I made the change you recommended and it didn't help. |
34 |
> |
35 |
|
36 |
you restarted nginx? |
37 |
|
38 |
|
39 |
-- |
40 |
Alan McKinnon |
41 |
alan.mckinnon@×××××.com |