Skip to main content

How to Review an AutoSSL Failure for a Customer Domain

You can identify and investigate why an SSL certificate failed to renew or issue for a customer's domain using the AutoSSL tool in WHM. This process allows you to determine if the issue is caused by incorrect DNS records, a missing certificate...

You can identify and investigate why an SSL certificate failed to renew or issue for a customer's domain using the AutoSSL tool in WHM. This process allows you to determine if the issue is caused by incorrect DNS records, a missing certificate request, or other configuration errors.

Before you begin

You will need:

  • Reseller access to WHM

  • The specific domain name that failed to secure an SSL certificate

Reviewing AutoSSL failures

  1. Log in to WHM.

  2. Navigate to Home > Security Center > Manage AutoSSL.

  3. Select the specific cPanel account associated with the customer's domain.

  4. Locate the domain in the list and click the View button next to the domain.

  5. Review the AutoSSL Logs for that specific domain.

  6. Identify the specific error message provided by the AutoSSL tool.

Note: Common issues include "DNS_PROBE_INVALID," which indicates the domain is not pointing to the correct server, or "CA_BUNDLE_ERROR," which may indicate a configuration issue with the certificate authority.

Common failure causes

If the logs indicate a failure, check the following areas:

  • DNS Records: Ensure the domain's A record points to the correct server IP address.

  • Mail Exchange (MX) Records: Ensure the MX records are correct if the certificate requires mail verification.

  • Hostname Resolution: Verify that the server's hostname resolves correctly.

Confirm the result

  • The AutoSSL logs will display a clear status for the domain.

  • If the issue is resolved (e.g., by correcting a DNS record), the next scheduled AutoSSL run will successfully issue the certificate.

Limitations

  • This process does not automatically fix underlying DNS issues; it only provides the information needed to identify them.

  • AutoSSL runs on a schedule; changes to DNS records may take time to propagate before the next successful certificate issuance.

Did this answer your question?