Auto SSL Not Working
I setup AutoSSL back in January, but after April 14's checkup, I started getting these errors in the log and now our SSL went down disabling usage of our apps:
[QUOTE]WARN Local HTTP DCV error (sub1.domain.tld): The content ", did not match the expected value. The domain "sub1.domain.tld" resolved to an IP address "X.X.X.X" that does not exist on this server.
WARN Local HTTP DCV error (sub2.domain.tld): The system failed to fetch the DCV (Domain Control Validation) file at " because of an error: The system failed to send an HTTP (Hypertext Transfer Protocol) "GET" request to " because of an error: Cpanel::Exception/(XID trbq93) "sub2.domain.tld.well-known" does not resolve to any IP addresses on the internet.. The domain "sub2.domain.tld" resolved to an IP address "X.X.X.X" that does not exist on this server.
The subdomains are configured on the same server. The X.X.X.X IP is our domain host where a CNAME was setup for the sub1 and sub2 subdomains. Has anything changed recently that would break the configuration?
The subdomains are configured on the same server. The X.X.X.X IP is our domain host where a CNAME was setup for the sub1 and sub2 subdomains. Has anything changed recently that would break the configuration?
-
I setup AutoSSL back in January, but after April 14's checkup, I started getting these errors in the log and now our SSL went down disabling usage of our apps: The subdomains are configured on the same server. The X.X.X.X IP is our domain host where a CNAME was setup for the sub1 and sub2 subdomains. Has anything changed recently that would break the configuration?
It seems that AutoSSL is working correctly and You need to check the IP Address of Domain for which you are issuing a SSL. Go to0 -
-- deleted by author -- 0 -
I have a hunch now that it's because the subdomains are pointing to containers. Any idea on how to get AutoSSL working with subdomains that utilize Docker containers? 0 -
@Pol33li - we're happy to move threads to the correct area, so there's no need to make multiples - just let us know! As far as the AutoSSL system, it has no knowledge of operating systems or containers - it only sees the DNS records. If the DNS doesn't respond properly, it won't be able to issue the certificate for the domain. With your error, you'll want to make sure the domain does resolve to an IP address on the server where you are running the AutoSSL tool. 0 -
With your error, you'll want to make sure the domain does resolve to an IP address on the server where you are running the AutoSSL tool.
Thanks, I believe we resolved the IP address issue last night through the creation of a config file. Clarity of the situation: In January, the SSL certificates for two subdomains were successfully installed because the two subdomain directories were acting as normal directories, which allowed the AutoSSL script to write the keys into the default /.well-known/ directories (I didn"t have the containers linked until after the subdomains and SSL were both working). I then connected the containers. The configuration was "working" until the SSL renewal process began. The certifier then tried to update the keys in the /.well-known/ directory, but due to the container being configured it was now trying to look inside the container for a /.well-known/ directory. Is there a Docker command or Apache configuration to make the SSL certbot look to the /.well-known/ on the main server and not try and find it inside the container?0 -
We don't have any support for the container or docker system at this time. 0 -
We don't have any support for the container or docker system at this time.
Are there any communities or forums that support containers or docker systems for cpanel that you could recommend?0 -
Thank you for the resource. In the end I "removed" the containers from the subdomains, installed a cert, and then reconnected the containers. Will probably install a 1-2 year cert to nullify the need to repeat this every 90 days. 0
Please sign in to leave a comment.
Comments
10 comments