NB: I have replaced the dot (.) in domain names below with a comma (,) so it would allow me to post this. Apparently, new users can only post two links in a post! Actually, they are not links, just examples, sort of makes asking a question about SSL on a domain difficult but never mind. So the comma’s are not typos and are not in my actual setup.
I am getting the above message when attempting to access my site via SSL. I am at a loss trying to figure out a fix.
Basically I set of domains, say:
I am using letsencrypt-auto to create certificates to use in nginx server. I have used the following:
sudo ./letsencrypt-auto certonly --webroot -w /var/www/example/ -d www,example,com -d example,com -d mail,example,com
Certificates are created and I link these into nginx:
server_name www,example,com example,com mail,example,com;
All would appear to be well … but, when I try it in the browser, I get: “requested domain name does not match the server’s certificate”. On closer inspection the certificate issued to the browser is for another domain set on my server (say example,org, www,example,org, …etc). I am at a loss to where this info is coming from and how it is getting into the certificate for other domain.
I originally tried to use the nginx plugin but it didn’t work for me. Perhaps something got set when I did this that is now stopping me issuing certificates correctly? The irony is that the domain, which is cross-contaminating is now on another server.
I need to issue a series of separate certificates on this server; I assume this is possible?
Does anyone know what may be causing this and how I can work round it?