# Directadmin Error with LetsEncrypt request **URL:** \ **Category:** Help\ **Created:** [June 30, 2023, 2:44pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025 "2023-06-30T14:44:36Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 2:44pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/1 "2023-06-30T14:44:36Z")
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help. My domain is: omedita.lt My hosting provider, if applicable, is: hostinger I am trying to issue a Lets's Encrypt wildcard ssl certificate but everytime i get an error saying that something is wrong and i can't get it I already have enabled a PositiveSSL. Maybe that's the problem, that it can't be 2 certificates at the same time Erorr window: Found wildcard domain name and http challenge type, switching to dns-01 validation. 2023/06/30 14:12:23 [INFO] [omedita.lt, _.omedita.lt] acme: Obtaining SAN certificate 2023/06/30 14:12:24 [INFO] [_.omedita.lt] AuthURL: [https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514967](https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514967) 2023/06/30 14:12:24 [INFO] [omedita.lt] AuthURL: [https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514977](https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514977) 2023/06/30 14:12:24 [INFO] [_.omedita.lt] acme: use dns-01 solver 2023/06/30 14:12:24 [INFO] [omedita.lt] acme: Could not find solver for: tls-alpn-01 2023/06/30 14:12:24 [INFO] [omedita.lt] acme: Could not find solver for: http-01 2023/06/30 14:12:24 [INFO] [omedita.lt] acme: use dns-01 solver 2023/06/30 14:12:24 [INFO] [_.omedita.lt] acme: Preparing to solve DNS-01 2023/06/30 14:12:26 2023/06/30 14:12:24 info executing task task=action=dns&do=delete&domain=omedita.lt&name=\_acme-challenge&type=TXT 2023/06/30 14:12:25 info executing task task=action=dns&do=add&domain=omedita.lt&name=\_acme-challenge&named\_reload=yes&ttl=5&type=TXT&value=%22Ivlglik2Rez6jQL8YV3eGKg-ljLB0WkONkRN\_nytNgA%22 2023/06/30 14:12:26 [INFO] [_.omedita.lt] acme: Trying to solve DNS-01 2023/06/30 14:12:26 [INFO] [_.omedita.lt] acme: Checking DNS record propagation using [[2001:4860:4860::8888]:53] 2023/06/30 14:12:56 [INFO] Wait for propagation [timeout: 5m0s, interval: 30s] 2023/06/30 14:12:57 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:13:27 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:13:57 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:14:27 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:14:58 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:15:28 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:15:58 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:16:28 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:16:58 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:17:28 [INFO] [_.omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:17:58 [INFO] [\*.omedita.lt] acme: Cleaning DNS-01 challenge 2023/06/30 14:17:59 2023/06/30 14:17:58 info executing task task=action=dns&do=delete&domain=omedita.lt&name=\_acme-challenge&type=TXT 2023/06/30 14:17:59 [INFO] [omedita.lt] acme: Preparing to solve DNS-01 2023/06/30 14:18:02 2023/06/30 14:17:59 info executing task task=action=dns&do=delete&domain=omedita.lt&name=\_acme-challenge&type=TXT 2023/06/30 14:18:01 info executing task task=action=dns&do=add&domain=omedita.lt&name=\_acme-challenge&named\_reload=yes&ttl=5&type=TXT&value=%22s7UeBhIxmSMMxIzhikureF0LGOvdukkNgAhSfSJ2\_yg%22 2023/06/30 14:18:02 [INFO] [omedita.lt] acme: Trying to solve DNS-01 2023/06/30 14:18:02 [INFO] [omedita.lt] acme: Checking DNS record propagation using [[2001:4860:4860::8888]:53] 2023/06/30 14:18:32 [INFO] Wait for propagation [timeout: 5m0s, interval: 30s] 2023/06/30 14:18:32 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:19:02 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:19:32 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:20:02 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:20:33 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:21:03 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:21:33 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:22:03 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:22:33 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:23:03 [INFO] [omedita.lt] acme: Waiting for DNS record propagation. 2023/06/30 14:23:33 [INFO] [omedita.lt] acme: Cleaning DNS-01 challenge 2023/06/30 14:23:34 2023/06/30 14:23:33 info executing task task=action=dns&do=delete&domain=omedita.lt&name=\_acme-challenge&type=TXT 2023/06/30 14:23:35 [INFO] Deactivating auth: [https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514967](https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514967) 2023/06/30 14:23:35 [INFO] Deactivating auth: [https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514977](https://acme-v02.api.letsencrypt.org/acme/authz-v3/241406514977) 2023/06/30 14:23:35 Could not obtain certificates: error: one or more domains had a problem: [\*.omedita.lt] time limit exceeded: last error: NS [ns1.dns-parking.com](http://ns1.dns-parking.com). returned NXDOMAIN for \_acme-challenge.omedita.lt. [omedita.lt] time limit exceeded: last error: NS [ns2.dns-parking.com](http://ns2.dns-parking.com). returned NXDOMAIN for \_acme-challenge.omedita.lt. Certificate generation failed. Those 2 lines changes everytime sometimes there is: NS [ns2.dns-parking.com](http://ns2.dns-parking.com) and NS [ns2.dns-parking.com](http://ns2.dns-parking.com) NS [ns1.dns-parking.com](http://ns1.dns-parking.com) and NS [ns1.dns-parking.com](http://ns1.dns-parking.com) NS [ns2.dns-parking.com](http://ns2.dns-parking.com) and NS [ns1.dns-parking.com](http://ns1.dns-parking.com) ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 2:56pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/2 "2023-06-30T14:56:10Z")
Hello @, welcome to the Let's Encrypt community. šŸ™‚ There are both IPv4 and IPv6 Address for the domain, IPv4 seem fine however IPv6 is not connecting see [https://www.ssllabs.com/ssltest/analyze.html?d=omedita.lt](https://www.ssllabs.com/ssltest/analyze.html?d=omedita.lt) Let's Encrypt will try IPv6 first. All IP Address need to produce the same replies and responses. ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/3/c/3c5ade6511bae4e69c76dc141a8cb41a61e43295.png) ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 2:57pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/3 "2023-06-30T14:57:19Z")
How do i fix this? ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 2:58pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/4 "2023-06-30T14:58:39Z")
A quick fix would be to disable IPv6 by removing the DNS AAAA Records from the domain. ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 2:59pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/5 "2023-06-30T14:59:19Z")
What will that do? Won't this crash my website? ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 3:00pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/6 "2023-06-30T15:00:01Z")
How would the crash your website? ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 3:00pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/7 "2023-06-30T15:00:34Z")
I don't know, maybe removing that, the current working SSL will stop working? ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 3:02pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/8 "2023-06-30T15:02:38Z")
What about the not quick fix? ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 3:06pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/9 "2023-06-30T15:06:00Z")
Get your server responding identical for both IPv4 and IPv6 addresses. ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 3:11pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/10 "2023-06-30T15:11:01Z")
If i delete that line in DNS settings, the Let's Encrypt should start working. Yes? ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 3:13pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/11 "2023-06-30T15:13:54Z")
I thinks so, or at least show us the next issue (if there are any). ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 3:25pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/12 "2023-06-30T15:25:18Z")
Gona post if something is wrong later, don't want to delete that setting when 100+ people are browsing the website ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 3:27pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/13 "2023-06-30T15:27:21Z")
Sensible. šŸ™‚ ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [June 30, 2023, 4:07pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/14 "2023-06-30T16:07:57Z")
Bruce: OP is having issues with their `dns-01` challenge. While I agree a non-functional IPv6 is a bad thing and needs to be addressed, it's _not_ the cause of the failing certificate issuance (as that would require the usage of the `http-01` challenge, not the currently used `dns-01`). @Tautuxs Is the DNS zone for `omedita.lt` also managed in DirectAdmin? Or separately? Edit: Hm, it seems `dns-parking.com` (the domain of the nameservers for `omedita.lt`) actually belong to Hostinger.. So that should be good, right? Can you confirm you can modify the DNS zone for `omedita.lt` using DirectAdmin? The output of your log looks from `acme.sh` but when I tried to identify the DNS plugin used by searching for the text `named_reload`, it does not give any result? Maybe Hostinger is using a custom DNS plugin for their acme.sh integration? -\> Hm, it seems that `named_reload` variable is a DirectAdmin thing looking at [named\_reload=yes to respect named\_service\_override](https://www.directadmin.com/features.php?id=2543).. Probably isn't acme.sh at all šŸ˜› @Tautuxs You might want to ask Hostinger about this issue. ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 4:13pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/15 "2023-06-30T16:13:19Z")
> [@Osiris](#): > > OP is having issues with their `dns-01` challenge. Good point Osiris, thank you. šŸ™‚ ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 4:40pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/16 "2023-06-30T16:40:03Z")
What should i ask them? Like: Why Let's Encrypt wildcard won't work for my VPS website? Or should i just copy pasta the same error window i posted in here? ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 4:41pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/17 "2023-06-30T16:41:59Z")
Since the [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) is being used this maybe of some use. > [@DNS providers who easily integrate with Let's Encrypt DNS validation](https://community.letsencrypt.org/t/dns-providers-who-easily-integrate-with-lets-encrypt-dns-validation/86438): > > Iā€¦ ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 4:42pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/18 "2023-06-30T16:42:28Z")
I think it's from hostinger, the DNS name servers, because the domain is bought from hostinger ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [June 30, 2023, 4:44pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/19 "2023-06-30T16:44:46Z")
> [@Tautuxs](#): > > the DNS name servers Here [https://dnsspy.io/scan/omedita.lt](https://dnsspy.io/scan/omedita.lt) shows name servers `ns1.dns-parking.com.` and `ns2.dns-parking.com.` ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/a/a/aa8b69ca31c49bf453dc4876e146c62ef64dee50.png) n ---
**Author:** ![Tautuxs](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tautuxs/32/71651_2.png) [@Tautuxs](https://community.letsencrypt.org/u/Tautuxs)\ **Post date:** [June 30, 2023, 4:46pm UTC](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025/20 "2023-06-30T16:46:44Z")
Yes. Those 2 name servers: ns1 and ns2 are hostingers name servers [Next page](https://community.letsencrypt.org/t/directadmin-error-with-letsencrypt-request/201025.md?page=2)