May 01, 2009 03:18AM
On Fri, May 1, 2009 at 12:00 AM, Tristan Griffiths
<tristan.griffiths@stomp.com.au> wrote:

> http {
>    server {
- listen 192.168.1.1:80 default;
+        listen 80 default;
>    }
> }

try that

also you could try dropping default. maybe the behavior will change. i
guess it depends if nginx will listen on new ips that are inherited
through heartbeat or not. i haven't tried but i've never hit the
situation where i had to tell nginx to re-bind. but i may have never
-got- to that situation to begin with :P
Subject Author Posted

nginx + ip_nonlocal_bind

Tristan Griffiths May 01, 2009 02:26AM

Re: nginx + ip_nonlocal_bind

mike May 01, 2009 02:33AM

RE: nginx + ip_nonlocal_bind

Tristan Griffiths May 01, 2009 03:00AM

Re: nginx + ip_nonlocal_bind

mike May 01, 2009 03:18AM

Re: nginx + ip_nonlocal_bind

Igor Sysoev May 01, 2009 02:50AM

RE: nginx + ip_nonlocal_bind

Tristan Griffiths May 01, 2009 03:27AM

Re: nginx + ip_nonlocal_bind

Igor Sysoev May 01, 2009 03:38AM

RE: nginx + ip_nonlocal_bind

Tristan Griffiths May 01, 2009 06:00AM

RE: nginx + ip_nonlocal_bind

Tristan Griffiths May 01, 2009 07:01AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 243
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready