Hi, i’m trying to configure Letsencrypt for a virtual domain, the same way i did for some other domains but for this one, i’m getting error saying there is an IPV6 record existing in apache for this domain, etc…
I searched on the forums and i seen other users having the same problems. The only solution i seen was about the option to change IP and set the IPV6 at none but it’s already at none…
I tried to find anything related to ipv6 in apache or in everything related to ip’s and so on and i found nothing.
My certificate expire in 6 days and i’m tired to update certificate manually so please can you help me with that?
First, I think you have the DNS feature enabled in Virtualmin, but you don’t appear to be hosting that zone locally in BIND. (Your DNS servers when I do a whois are GoDaddy servers). If you are not using Virtualmin to manage your DNS, you should disable the DNS feature in Features and Plugins (you’ll have to disable it in every domain you’ve created first, as you can’t disable a Feature if any domains are using it).
Second, Virtualmin, at some point, believed you wanted to use IPv6, so it created AAAA records and presumably Apache config for IPv6. Iguess you removed the Apache config, but didn’t remove the local DNS records…this one probably gets solved automatically by fixing the previous one.
I don’t know. Seems like a question for your DNS provider, if you can’t find how to disable it.
You can also choose to skip the tests that Virtualmin does, but I think you’ll probably end up failing to validate anyway…Let’s Encrypt is going to try to resolve AAAA records, too. I don’t know what it would do in this circumstance, as it doesn’t really make sense. It might resolve automatically to the right thing though. I may give up on AAAA since there is no AAAA for the bare domain (without www).
check here (found this in the forum)
In Virtualmin → Manage Virtual Server → Change IP address, set IPv6 address to none and then apply again for a SSL certificate. Should work this time.
The problem OP has (at least the one that caused the specific error we’ve seen) is not that. OP has an AAAA record for one of the names they’re trying to request a certificate for (www). Virtualmin sees that, and knows that Apache is not configured to respond to IPv6 requests, and helpfully is telling OP about that misconfiguration.
There are several ways to deal with it.
One (the right way) is to get rid of the AAAA record, if the site won’t be available on an IPv6 address.
Another is to tell Virtualmin to skip the tests that it is doing. That will get past the Virtualmin error, but may fail when Let’s Encrypt tries to validate (or may not, depends on how they resolve the name and whether they’re strict about an AAAA record eventually resolving to an IPv4 address…which, I’m pretty sure, is invalid, but maybe it’s OK for Let’s Encrypt).
Another is to stop trying to get a cert for www, since that may be the only one that has this problem, though I didn’t . If you request certs for names that do not have AAAA records, it should validate fine (assuming everything else is OK).
They all come down to getting DNS right for the names you’re requesting a cert for, one way or another. I run out of ways to say, “fix your DNS”, but that’s pretty often the answer.
