Binding nginx to a single interface

Bai Shen baishen.lists at gmail.com
Thu Feb 9 17:50:13 UTC 2012


listen ip:port;

I realized after I sent the email that I'd typoed that.  It's the newest
version, 1.0.11

On Thu, Feb 9, 2012 at 12:45 PM, Adrián Navarro <adrian at navarro.at> wrote:

>  listen ip:port; or listen ip port;?
>
> actually in that case it would be listening on default for the ip AND for
> the port as an address (weird scenario).
>
> version?
>
> -a.
>
> On Thursday 9 de February de 2012 at 18:42, Bai Shen wrote:
>
> I have two nics on my server.  I have nginx set to listen on one of them
> using "listen 10.1.2.3 80"  However, it keeps listening on the other ip as
> well.  So i'm unable to start anything else on port 80 on that interface.
>
> Any ideas what could be wrong?  Everything I'm finding says that the
> listen command is all I needed to do.
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120209/2e4b9511/attachment.html>


More information about the nginx mailing list