Author Topic: AutoSSL Does not Install Correct Domain  (Read 254 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
AutoSSL Does not Install Correct Domain
« on: April 20, 2019, 06:40:34 AM »
Common Name missmatch when using AutoSSL.
It's install as hostname, not a real domain name.

Here's the info from sslshopper.com :
None of the common names in the certificate match the name that was entered (billing.domain.com). You may receive an error when accessing this site in a web browser.

And Common Name missmatch info :
Common name: srv.domain.com
SANs: srv.domain.com


billing.domain.com is my real domain and srv.domain.com is my hostname.
See?  it's a different domain name when I'm using AutoSSL to generate SSL.

~ (note) domain.com for example domain only ~

Offline
*****
Re: AutoSSL Does not Install Correct Domain
« Reply #1 on: April 29, 2019, 06:04:30 AM »
Hi, are you sure you have installed SSL to the domain? Try to restart WEB server(s) if you are.

Offline
***
Re: AutoSSL Does not Install Correct Domain
« Reply #2 on: May 04, 2019, 01:37:06 PM »
Something strange happened, which caused chaos with my certs.

When I installed CWP I was asked for primary domain.

In the past, it made no difference which domain I used.  In fact, I even used bogus.com in the past with no problem.

But now, it makes a very big difference.

During install, I used my domain from my other server, (which I am being forced to abandon because CWP has expired files and will no longer update).  The NEW install, then created a hostname-ssl file.....BUT..BUT.....BUT...the NEW install created a hostname-ssl file and populated the IP address by a DNS LOOKUP.

Guess what.....the NEW INSTALL created a hostname-ssl file with my OLD SERVER IP ADDRESS because DNS resolved to the old server IP address.   Bad Bad boy!  This  created big problems and big headaches.

If I look at primary domain name in NEW CWP it showed the old server IP address.  I was able to edit the IP address, but I dont know how to edit primary domain associated with account.
« Last Edit: May 04, 2019, 01:39:44 PM by pixelpadre »

Offline
*****
Re: AutoSSL Does not Install Correct Domain
« Reply #3 on: May 08, 2019, 07:50:28 AM »
Hi, you must check your DNS. CWP works fine with SSL.

Offline
*
Re: AutoSSL Does not Install Correct Domain
« Reply #4 on: May 09, 2019, 04:21:05 PM »
I have the same issue. "The hostname (cwp.example.com) does NOT match the Common Name in the certificate (www.example.com). This certificate is currently invalid for this host." The certificates for my domains are valid but not the one for the host.

As I understand, I have to change the Common Name. But how can I do it? I found this solution:
https://community.letsencrypt.org/t/how-can-i-easily-make-the-base-name-and-common-name-the-same/36998 (see Post 2). Does this really work? I don't want to mess it up.

Offline
***
Re: AutoSSL Does not Install Correct Domain
« Reply #5 on: May 10, 2019, 03:55:46 AM »
(...)
https://community.letsencrypt.org/t/how-can-i-easily-make-the-base-name-and-common-name-the-same/36998 (see Post 2). Does this really work? I don't want to mess it up.

Use /root/.acme.sh/acme.sh tool instead.
Is the installed tool.
To run help:
Code: [Select]
# /root/.acme.sh/acme.sh -h

To use certbot, you should to sure certbot tool will install the certs in same location.
I cannot assure that, perhaps someone else.

Regards,
Netino

Offline
*
Re: AutoSSL Does not Install Correct Domain
« Reply #6 on: May 15, 2019, 11:31:13 AM »
Now all certificates are valid. I guess rebuilding all vHosts worked but I can't reproduce it. Thanks anyway.