AutoSSL Not Generating Signing Request
We have been using AutoSSL since obtaining our server at the beginning of the year, and so far the AutoSSL has been working great for some of our domains.
The domains it has been working great for all share the same registrar and nameservers - conveniently, the same registrar as we rent the dedicated server from.
Now, we have another domain which is with a different registrar, as the .[tld] for the domain is not supported by the registrar our server and other domains are with.
I have configured the A records to point towards our server, although the AutoSSL signing request doesn't seem to get initiated.
Could this be an issue with the nameservers pointing somewhere else, or is there something more obvious that I have missed?
Appreciate any guidance.
-
Hello, Can you browse to "WHM >> Manage AutoSSL" and review one of the affected usernames under the "Logs" tab to see what's happening when AutoSSL attempts to install a certificate on one of those domain names? Thank you. 0 -
My log is as follows: 3:53:18 PM This system has AutoSSL set to use "cPanel (powered by Comodo)". 3:53:18 PM Checking websites for "enablebusiness" " 3:53:18 PM The website "example.com", owned by "enablebusiness", has a valid SSL certificate, but additional SSL coverage may be possible for the domains "mail.example.com", "webdisk.example.com", "webmail.example.com", "cpanel.example.com", "webmail.example.com", "webdisk.example.com", and "cpanel.example.com". The system will attempt to replace this certificate with one that includes these additional domains. 3:53:18 PM The website "tools.example.com", owned by "enablebusiness", has a faulty SSL certificate (OPENSSL_VERIFY:0:18:DEPTH_ZERO_SELF_SIGNED_CERT). AutoSSL will attempt to replace this certificate. 3:53:18 PM WARN The domain "tools.example.com" failed domain control validation: "tools.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "www.tools.example.com" failed domain control validation: "www.tools.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "mail.example.com" failed domain control validation: "mail.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "webdisk.example.com" failed domain control validation: "webdisk.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "webmail.example.com" failed domain control validation: "webmail.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "cpanel.example.com" failed domain control validation: "cpanel.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "webmail.example.com" failed domain control validation: "webmail.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "webdisk.example.com" failed domain control validation: "webdisk.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM WARN The domain "cpanel.example.com" failed domain control validation: "cpanel.example.com" does not resolve to any IPv4 addresses on the internet. 3:53:19 PM AutoSSL cannot add any new domains to SSL coverage for the website "example.com". 3:53:19 PM The system has completed the AutoSSL check for "enablebusiness".
It would appear as though the DNS isn't resolving for all subdomains - I will get this added with the registrar and then update this thread once I have tested again.0 -
Yeah, adding the A records for the subdomains seems to have done the trick. I feel so silly now not realising that was the issue - I guess it's because I normally put a wildcard DNS record on the domains but I didn't on this particular one. 0 -
Hello, I'm glad to see you were able to solve the issue. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
4 comments