Working now, and you were correct, the issue was with IP addresses. The IP addresses used needed to be the internal IP addresses, not the public external IPs. So for example one of our addresses was 99.999.9.102:443, it should have been instead 192.168.100.102:443. Stupid mistake on my part.by danjac - Nginx Mailing List - English
The IP addresses are fine, they are configured correctly on the host as far as I (and our hosting company) can verify. > Have you read this > http://nginx.org/en/docs/http/configuring_https_servers.html > ? I take it you mean this section: The oldest and most robust method to resolve the issue is to assign a separate IP address for every HTTPS server: server { listenby danjac - Nginx Mailing List - English
OK, the error I now get is this (nginx error log file): 27054#0: *233 no "ssl_certificate" is defined in server listening on SSL port while SSL handshaking, client: 77.97.200.235, server: 0.0.0.0:443 In the Firefox this appears as "The connection to the server was reset while the page was loading.". This is when I set the default for port 443 to "*:443 defaulby danjac - Nginx Mailing List - English
Yes, telnet works too.by danjac - Nginx Mailing List - English
I've double-checked the IP addresses, they are all resolving correctly to this host.by danjac - Nginx Mailing List - English
> > You see certificate for firstdomain.com for all > > addresse - IP2 and IP3 ? > > I'm not sure I quite understand. Each IP address is set for each domain > and has its own certificate. > Yes, but currently do you see only certificate of firstdomain.com for > all requests ? Yes. I'll check with our hosting provider to ensure these IPs are set correctly.by danjac - Nginx Mailing List - English
> You see certificate for firstdomain.com for all > addresse - IP2 and IP3 ? I'm not sure I quite understand. Each IP address is set for each domain and has its own certificate. > And the previous error "Cannot assign requested > address" is related to this. > > > Igor Sysoev Wrote: > > > -------------------------------------------------- >by danjac - Nginx Mailing List - English
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. Igor Sysoev Wrote: ------------------------------------------------------- > On Wed, Oct 20, 2010 at 06:22:59AM -0400, danjacby danjac - Nginx Mailing List - English
As you can see, they are all using different IPs.by danjac - Nginx Mailing List - English
The IP is configured for this address, yes.by danjac - Nginx Mailing List - English
I have an nginx (v0.7.64) configuration that requires a number of virtual hosts each with their own SSL. I have assigned different IP addresses to each vhost. All IP addresses are available on port 443 (i.e. they are not blocked by firewall). All certificates are from Thawte. When I test nginx configuration (nginx -t), I get the following error: the configuration file /usr/local/nginx/coby danjac - Nginx Mailing List - English