On Wed, Oct 20, 2010 at 07:15:05AM -0400, danjac wrote:

> This solution works (i.e. I can restart nginx) but it doesn't recognize
> the correct domain - certificate for firstdomain.com is correct, but
> when I go to the seconddomain.com I get the SSL error "this site was
> configured for firstdomain.com" in my browser.

You see certificate for firstdomain.com for all addresse - IP2 and IP3 ?
It seems that these IP-addresses are not really configured on the host.
And the previous error "Cannot assign requested address" is related to this.

> Igor Sysoev Wrote:
> -------------------------------------------------------
> > On Wed, Oct 20, 2010 at 06:22:59AM -0400, danjac
> > wrote:
> >
> > > The IP is configured for this address, yes.
> >
> > Then something wrong in this configuration.
> > This is not nginx issue.
> > You can workaround it by binding only to *:443 and
> > letting nginx to learn
> > address at run-time:
> >
> > server {
> > listen *:443;
> > listen IP1:443;
> > }
> >
> > server {
> > listen IP2:443;
> > }
> >
> > server {
> > listen IP3:443;
> > }


--
Igor Sysoev
http://sysoev.ru/en/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx