Recently, neponyatki occur with SSL and NGINX: there is a confusion of certificates among themselves. There are many domains on the server (500+). If earlier it showed that the certificate was not from that domain (for example, going to test.ru issued that the certificate belongs to test1.ru) and everything was solved by deleting the test1.ru certificate, now everything is completely deadlocked, it gives: "Error when establishing a secure connection. " without any additional information.
The syntax is normal (nginx -t), I also visually run over - everything is OK (although I can miss something with such a volume).
Config for domain:
server { server_name s1.com www.s1.com; listen 1.1.1.1; listen 1.1.1.1:443 ssl; disable_symlinks if_not_owner from=$root_path; set $root_path /var/www/red/data/www/s1.com; location ~* ^.+\.(jpg|jpeg|gif|png|svg|js|css|mp3|ogg|mpe?g|avi|zip|gz|bz2?|rar|swf)$ { root $root_path; access_log /var/www/nginx-logs/red isp; access_log /var/www/httpd-logs/s1.access.log ; error_page 404 = @fallback; } location / { proxy_pass http://1.1.1.1:81; proxy_redirect 1.1.1.1:81 /; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; } location ~* ^/(webstat|awstats|webmail|myadmin|pgadmin)/ { proxy_pass http://1.1.1.1:81; proxy_redirect 1.1.1.1:81 /; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; } location @fallback { proxy_pass http://1.1.1.1:81; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; } limit_conn red 200; ssl_certificate /var/www/httpd-cert/s1.crt; ssl_certificate_key /var/www/httpd-cert/s1.key; } Tell me, please, in which direction to dig.
listenis a bad sign. Do you exactly use them in allserverblocks? - Alexey Ten