Re: SSL_ERROR_BAD_CERT_DOMAIN

2020-05-15 Thread Francis Daly
On Thu, May 14, 2020 at 03:37:38PM -0400, Amakesh wrote: Hi there, > Earlier Let’s encrypt certificates worked fine for for all of them, but > recently installed Nginx as web proxy. > https://www.ssllabs.com shows all of the certificates have Server > hostname(rsvix170.gerwanserver.de) as domain

SSL_ERROR_BAD_CERT_DOMAIN

2020-05-14 Thread Amakesh
now a problem with the certificates - SSL_ERROR_BAD_CERT_DOMAIN. https://www.ssllabs.com shows all of the certificates have Server hostname(rsvix170.gerwanserver.de) as domain name and not their own addresses. https://www.ssllabs.com/ssltest/analyze.html?d=solaris-ustronie.eu https://check-your

Re: SSL_ERROR_BAD_CERT_DOMAIN with multiple domains

2019-07-10 Thread Francis Daly
On Sat, Jul 06, 2019 at 07:59:10AM -0400, BeyondEvil wrote: Hi there, > Server A (macmini) has an nginx server under my direct control. > Server B (the synology NAS) has an nginx server NOT under my direct > control. ...and you have exactly 1 public IP address, and you would like to be able to a

Re: SSL_ERROR_BAD_CERT_DOMAIN with multiple domains

2019-07-06 Thread BeyondEvil
Hi Francis! Thank you so much for your answer! I really appreciate it! And I apologize for taking this long to reply. > As I understand things: > > * you need one nginx listening on port 80 for http and 443 for https > * you want to handle two server names (differently) Well, sort of. I have t

Re: SSL_ERROR_BAD_CERT_DOMAIN with multiple domains

2019-06-26 Thread Francis Daly
On Sat, Jun 22, 2019 at 04:01:40PM -0400, BeyondEvil wrote: Hi there, I don't have an answer for you, but I do have some comments that may make it easier for someone else to have an answer. > So I need to add two new server blocks in my config so that: > If I visit "http://domain.synology.me"; (

SSL_ERROR_BAD_CERT_DOMAIN with multiple domains

2019-06-22 Thread BeyondEvil
I have two domains: (1) myvery.owndomain.com (2) domain.synology.me (1) is under my control (I own the domain) and I manage the certs (Let's Encrypt). If I visit "https://myvery.owndomain.com"; I'm greeted by the "Welcome to Nginx!" landing page. (I use nginx as a reverse proxy only.) (2) is a D

SNI: ssl_error_bad_cert_domain on https://

2015-02-28 Thread 173279834462
t; The certificate is only valid for the following names: < < www.example.com example.com < < (Error code: ssl_error_bad_cert_domain) where "example.com" is a random? host from our pool of vhosts, and its registered certificate is served for the IP-ADDRESS by nginx's SNI