AutoSSL Log Warnings On Addon Domain That Used To Be a Main Domain
I have a domain, let's call it "problemdomain.com" that was originally the main domain for a cPanel account, but now is an addon domain for another domain I will call "maindomain.com."
I recently enabled AutoSSL for maindomain.com, and AutoSSL successfully installed the SSL certificate for maindomain.com and problemdomain.com; however, in the AutoSSL log each night I get this:
10:58:04 PM Checking websites for "maindoma" "
10:58:04 PM The website "problemdomain.maindomain.com", owned by "maindoma", has a valid SSL certificate, but additional SSL coverage may be possible for the domains "cpanel.problemdomain.com" and "webmail.problemdomain.com". The system will attempt to replace this certificate with one that includes these additional domains.
10:58:04 PM WARN The domain "cpanel.problemdomain.com" failed domain control validation: "cpanel.problemdomain.com" does not resolve to any IPv4 addresses on the internet.
10:58:04 PM WARN The domain "webmail.problemdomain.com" failed domain control validation: "webmail.problemdomain.com" does not resolve to any IPv4 addresses on the internet.
10:58:04 PM AutoSSL cannot add any new domains to SSL coverage for the website "problemdomain.maindomain.com".
10:58:04 PM The system has completed the AutoSSL check for "maindoma".
Obviously, the subdomains cpanel.problemdomain.com and webmail.problemdomain.com don't exist since problemdomain.com is an addon domain and not a cPanel account main domain, so they don't resolve. My question is whether the warnings for the missing cpanel and webmail subdomains are normal behavior for AutoSSL with addon domains, and I should just ignore the warnings, or is AutoSSL attempting to add SSL coverage for the cpanel and webmail subdomains because something is left over from when problemdomain.com was a cPanel account main domain? If it's the latter, how can I fix it?
Obviously, the subdomains cpanel.problemdomain.com and webmail.problemdomain.com don't exist since problemdomain.com is an addon domain and not a cPanel account main domain, so they don't resolve. My question is whether the warnings for the missing cpanel and webmail subdomains are normal behavior for AutoSSL with addon domains, and I should just ignore the warnings, or is AutoSSL attempting to add SSL coverage for the cpanel and webmail subdomains because something is left over from when problemdomain.com was a cPanel account main domain? If it's the latter, how can I fix it?
-
Hello, Actually, you can use proxy subdomains (e.g. cpanel.domain.tld) with addon domain names. If the entries do not exist, you can add them with the following command: /scripts/proxydomains add --domain=addon-domain.tld
Thank you.0 -
I may not have been clear in my question. I'm not trying to access cPanel or Webmail with, for example, "cpanel.problemdomain.com." I'm asking if the fact that problemdomain.com used to be a main domain accounts for the warnings in the AutoSSL log, and, if so, how to fix it so they don't appear in the log. If the warnings are normal for addon domains with AutoSSL, I can just ignore them, but I wanted to fix them if they are due to a leftover configuration. 0 -
Hello, Those warning messages are normal, even with Addon domain names, as the feature will attempt to setup SSL certificates for proxy subdomains. There's a feature request for the ability to exclude certain domain names from the AutoSSL feature at: AutoSSL: Prevent specific domains from being issued free SSL certificates Thank you. 0 -
That's what I needed to know. Now I can comfortably ignore them; I was just wondering if something was left behind from when the domain was a main domain. I voted for the feature request. Thanks! You can mark this one solved. 0
Please sign in to leave a comment.
Comments
4 comments