DCV error AutoSSL

jimlongo

• April 07, 2019 08:39

Receiving the following error when Auto SSL is run on this subdomain. WARN Local HTTP DCV error (whmcs.example.cloud): The system queried for a temporary file at "http://whmcs.example.cloud/.well-known/pki-validation/C80C71C7CE884124B1D7CF3C58CABCA4.txt", but the web server responded with the following error: 404 (Not Found). A DNS (Domain Name System) or web server misconfiguration may exist.
I have read through the common errors, etc., Thing is I can reach the address properly. For instance if I put a test.txt file in this location it can be reached at

• 

  jimlongo

  • April 09, 2019 16:00

  Should I open a ticket?

  0
• 

  cPanelMichael

  • April 09, 2019 16:21

  Hello @jimlongo, Can you verify which cPanel & WHM version is installed on this system? Version 78.0.20 includes a couple of cases designed to address DNS resolution issues: [QUOTE]

  • Fixed case CPANEL-26228: Reuse DNS query ID for parallel queries in DNS resolver.
  • Fixed case CPANEL-26238: Disable persistent UDP in DnsRoots::Resolver.

  
  Thank you.

  0
• 

  jimlongo

  • April 09, 2019 20:55

  Thanks, It is 78.0.20, and I just ran it again with the same error.

  0
• 

  cPanelMichael

  • April 09, 2019 21:12

  Hi @jimlongo, Can you open a

  0
• 

  jimlongo

  • April 09, 2019 21:43

  ticket #11915331 Thank you.

  0
• 

  jimlongo

  • April 10, 2019 16:36

  from support (note I'm still waiting for DNS to propagate . . . ) This is occurring due to the domain resolving to an IPv6. ================================= ??# dig AAAA whmcs.mydomain.cloud +short 2600:3c03::xxxxxx ======================== However, Apache does not have an IPv6 VirtualHost present which is why the 404 error is occurring. You'll need to add the IPv6 to the cPanel / WHM configuration following the documentation below: ================================================ https://docs.cpanel.net/search/?product=all&q=80Docs/IPv6+Ranges https://documentation.cpanel.net/display/80Docs/Assign+IPv6+Address ======================================================= Alternately, removing the AAAA records where the remote DNS is hosted will also resolve the issue.
  I'm trying to remove the AAAA records from the DNS management for this domain, mostly because the documentation noted in this response is very difficult to follow.

  0
• 

  jimlongo

  • April 10, 2019 20:15

  Unfortunately that fixed the DNS, but was followed by a permissions problem. At any rate it is fixed, all is well. Thanks for your help.

  0

Please sign in to leave a comment.