Hi Almir,<br><br>You're correct that nginx should listen on 80 for http and 443 for https, and that's what I show in my example for the front-end servers. It's the back-end nginx that is listening on arbitrary ports. The back-end nginx will not be accessed directly from any client computers -- all requests will be proxied through the front-end servers first. (Please see my original post for an explanation of why this is necessary.)<br>
<br>Nick<br><br><br><div class="gmail_quote">On Thu, Oct 30, 2008 at 4:20 PM, Almir Karic <span dir="ltr"><<a href="mailto:almir@kiberpipa.org">almir@kiberpipa.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thu, Oct 30, 2008 at 03:29:47PM -0500, Nick Pearson wrote:<br>
> I'm going to try tonight to get this working as you have suggested. I'm<br>
> hoping that I'll be able to do it without using too many IPs, because then<br>
> I'll run into my original problem (the IP limit imposed by my hosting<br>
> provider). I believe your solution of listening on the same IP on multiple<br>
> ports should work, though. I'll just assign two listen ports on the<br>
> back-end nginx for each site -- one for http and one for https.<br>
<br>
</div>no. for each ssl https you want visible to world you have to have one ip,<br>
unless off course you want to tell your visitors/costumers that they enter<br>
<a href="https://your-site.com:444" target="_blank">https://your-site.com:444</a> to enter the site.<br>
<br>
</blockquote></div><br>