listen ip:port;<br><br>I realized after I sent the email that I'd typoed that. It's the newest version, 1.0.11<br><br><div class="gmail_quote">On Thu, Feb 9, 2012 at 12:45 PM, Adrián Navarro <span dir="ltr"><<a href="mailto:adrian@navarro.at">adrian@navarro.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
listen ip:port; or listen ip port;?
</div><div><br></div><div>actually in that case it would be listening on default for the ip AND for the port as an address (weird scenario).</div><div><br></div><div>version?</div><div><br></div><div>-a.</div>
<div class="im">
<p style="color:#a0a0a8">On Thursday 9 de February de 2012 at 18:42, Bai Shen wrote:</p>
</div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span><div><div class="im"><div>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.<br>
<br>Any ideas what could be wrong? Everything I'm finding says that the listen command is all I needed to do.<br>
</div></div><div><div>_______________________________________________</div><div>nginx mailing list</div><div><a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a></div><div><a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a></div>
</div></div></span>
</blockquote>
<div>
<br>
</div>
<br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br></blockquote></div><br>