Answer the question
In order to leave comments, you need to log in
Nginx is loading the wrong certificate. What to do?
There are configs for each domain of this kind
....
server_name host.[net,ru,com,by];
ssl_certificate /path/to/cert/host.[net,ru,com,by].crt;
ssl_certificate_key /path/to/cert/host.[net,ru,com,by].key;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers kEECDH+AES128:kEECDH:kEDH:-3DES:kRSA+AES128:kEDH+3DES:DES-CBC3-SHA:!RC4:!aNULL:!eNULL:!MD5:!EXPORT:!LOW:!SEED:!CAMELLIA:!IDEA:!PSK:!SRP:!SSLv2;
ssl_prefer_server_ciphers on;
add_header Strict-Transport-Security max-age=63072000;
add_header X-Content-Type-Options nosniff;
.....
Answer the question
In order to leave comments, you need to log in
Check that nginx is built with SNI support. This can be done with the nginx -V command.
And also check that the browsers in which the problem is observed are also able to SNI:
nginx.org/en/docs/http/configuring_https_servers.html
If this is indeed the problem, then certificates and different virtual hosts can be placed at different ip-addresses.
To improve browser support, a root certificate for the chain was added to the certificate itself.
Many have solved the problem, but this is not a panacea.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question