Skip to main content

AutoSSL not creating certificates

coursevector
I looked and looked and couldn't find a solution to my problem. I have about 20~ accounts all with valid domains. But AutoSSL says it can't get certificates for them. See below:
Log for the AutoSSL run for "USERNAME": Friday, December 9, 2016 9:34:45 AM GMT-0500 (cPanel (powered by Comodo)) 2:34:45 PM This system has AutoSSL set to use "cPanel (powered by Comodo)". 2:34:45 PM Checking websites for "USERNAME" " 2:34:45 PM The website "example.com", owned by "USERNAME", has no SSL certificate. AutoSSL will attempt to obtain a new certificate and install it. 2:34:45 PM WARN The domain "example.com" failed domain control validation: "example.com" does not resolve to any IPv4 addresses on the internet. at bin/autossl_check.pl line 512. 2:34:45 PM WARN The domain "www.example.com" failed domain control validation: "www.example.com" does not resolve to any IPv4 addresses on the internet. at bin/autossl_check.pl line 512. 2:34:45 PM WARN The domain "mail.example.com" failed domain control validation: "mail.example.com" does not resolve to any IPv4 addresses on the internet. at bin/autossl_check.pl line 512. 2:34:45 PM The system has completed the AutoSSL check for "USERNAME". 2:34:45 PM The system has finished checking 1 user.
Except that example.com, www.example.com, etc all work and are valid. I have this error for all the accounts on the server.

Comments

4 comments

Date Votes
  • coursevector
    Ticket #8048341
    0
  • coursevector
    I managed to get the certificates to go through by disabling CSF/LFD. But this is not a great solution in the 90days when the certificates need to renew. I checked the IPs used to validate the text files and they were not blocked by CSF. So something else is causing the issue.
    0
  • coursevector
    This was resolved, there was a block in CSF for:
    192.0.0.0/8 # lfd: (NETBLOCK) 192.0.0.0/8
    Some of the root DNS servers are in the 192 block and that was causing the issue. Removing the block fixed the issue.
    0
  • cPanelMichael
    This was resolved, there was a block in CSF for:
    192.0.0.0/8 # lfd: (NETBLOCK) 192.0.0.0/8
    Some of the root DNS servers are in the 192 block and that was causing the issue. Removing the block fixed the issue.

    Hello, I'm happy to see the issue is now resolved. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post