# Requesting a certificate for \*\*\* from Let's Encrypt request failed **URL:** \ **Category:** Help! (Home for newbies)\ **Created:** [February 16, 2021, 12:52am UTC](https://forum.virtualmin.com/t/requesting-a-certificate-for-from-lets-encrypt-request-failed/109424 "2021-02-16T00:52:46Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![ramin](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/71e660/32.png) [@ramin](https://forum.virtualmin.com/u/ramin)\ **Post date:** [February 23, 2021, 4:00pm UTC](https://forum.virtualmin.com/t/requesting-a-certificate-for-from-lets-encrypt-request-failed/109424/3 "2021-02-23T16:00:52Z")
> [@petralian](#): > > I actually have no idea how to fix this… Neither do I but I’ll throw out some ideas… > [@petralian](#): > > Webmin = [jp.mysite.com](http://jp.mysite.com) Is this the server’s hostname and is there an A record for it? If you are hosting your own DNS Virtualmin takes care of essential A records when you create a virtualhost, but I don’t think Virtualmin takes a server hostname into account. If there’s a missing A record for this name add it manually to the same zone for the other names. > [@petralian](#): > > I do not use AAAA Do you mean there’s no IPv6 at all? or IPv6 is enabled for the server but you choose not to use it? If IPv6 is lurking somewhere in the network LE will find it and expect to find AAAA records. Or IPv6 doesn’t exist but there’s an entry for `::1` in _/etc/hosts_. If any of this rings a bell you’ll want to make certain IPv6 is thoroughly disabled before going without AAAA records. Here’s a suggestion that may help with that: > [@Error creating Certificate : address ::1 exists, but this virtual server does not have IPv6 enabled](https://forum.virtualmin.com/t/error-creating-certificate-address-1-exists-but-this-virtual-server-does-not-have-ipv6-enabled/109119/2): > > 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. It’s hard to say why http validation fails. Sometimes LE is unable to create _.well-known/acme-challenge_. Other times there’s redirection occuring in a virtualhost config or http header in an _.htaccess_ file that gets in LE’s way. When http validation fails LE moves on to DNS validation, so I find that it’s easier to correct DNS one time rather than modify a virtualhost every time LE needs to run. --- _[View the full topic](https://forum.virtualmin.com/t/requesting-a-certificate-for-from-lets-encrypt-request-failed/109424)._