Skip to main content

The certificate chain failed OpenSSL’s verification

Comments

5 comments

  • cPanelLauren
    Hello, Does the domain have an AAAA record or is it by chance using IPv6? If so can you confirm that the IPv6 address resolves to the server? Furthermore, if you switch to the Comodo provider rather than the Let's Encrypt provider do you continue to receive the same error? Thanks!
    0
  • meeven
    Does the domain have an AAAA record or is it by chance using IPv6? If so can you confirm that the IPv6 address resolves to the server? Furthermore, if you switch to the Comodo provider rather than the Let's Encrypt provider do you continue to receive the same error?

    @cPanelLauren, thanks for editing the title of my post! I couldn't find a way to do it myself.:) To answer your question, yes, the domain has an AAAA record at the external DNS provider for both the root domain and the www domain. And, the IPV6 address does resolve to the server FQDN. I also checked the Basic Config section WHM setup and both the IPv4 and IPv6 addresses are bound to the server. The only non-standard thing about the domain's config (in fact, all domains on the server) is that it uses external DNS, via Linode DNS manager. About using Comodo as the provider, I am not sure what impact this might have. Is this safe to change?
    0
  • cPanelLauren
    Hi @meeven It is safe to change though it will update the certificate on any domains to Comodo SSL's if they don't currently have certificates.
    0
  • meeven
    @cPanelLauren, I was able to get this sorted out, thanks to cPanel tech support. The solution is to assign the IPv6 address to the domain using the WHM " "Assign IPv6 Address" interface and then run LetsEncrypt for the domain again.
    0
  • cPanelLauren
    Hi @meeven Glad to hear you were able to get the issue sorted out! Thanks for letting us know what the resolution was. Thanks!
    0

Please sign in to leave a comment.