# Challenges have failed

**URL:** <https://community.letsencrypt.org/t/challenges-have-failed/219066>\
**Category:** Help\
**Created:** [May 27, 2024, 4:21am UTC](https://community.letsencrypt.org/t/challenges-have-failed/219066 "2024-05-27T04:21:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cirosanchez](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cirosanchez/32/80296_2.png) [@cirosanchez](https://community.letsencrypt.org/u/cirosanchez)\
**Post date:** [May 27, 2024, 4:21am UTC](https://community.letsencrypt.org/t/challenges-have-failed/219066/1 "2024-05-27T04:21:25Z")

</div>

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. [crt.sh | 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: [cirosanchez.me](http://cirosanchez.me)

I ran this command: idk, im using nginx proxy manager?

It produced this output: [LearnSpigot: Paste](https://paste.learnspigot.com/uxujayeluq.yaml)

My web server is (include version): nginx v2.11.2

The operating system my web server runs on is (include version): ubuntu 22.04

My hosting provider, if applicable, is: holynodes

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Portainer 2.19.5, Nginx 2.11.2

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): 2.10.0

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [May 27, 2024, 6:07am UTC](https://community.letsencrypt.org/t/challenges-have-failed/219066/2 "2024-05-27T06:07:48Z")

</div>

Looks like everything goes according to plan with adding and removing the TXT challenge using Cloudflare, but for some reason the Let's Encrypt resolver can't find it. Maybe the 10 seconds propogation time is just too short? Any way to increase that in NPM?

Also, nginx seems to be working just fine, is there any reason why NPM would opt for the `dns-01` challenge instead of the much simpeler `http-01` challenge? You're not requesting a wildcard certificate which would mandate the `dns-01` challenge..

Maybe 2 questions for the NPM support channel(s) 🙂

---

<div class="post-metadata">

**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\
**Post date:** [May 27, 2024, 6:18am UTC](https://community.letsencrypt.org/t/challenges-have-failed/219066/3 "2024-05-27T06:18:53Z")

</div>

> [@Osiris](#):
>
> Maybe the 10 seconds propogation time is just too short?

Yes as @Osiris suggests, you need to wait at least 30 seconds for cloudflare DNS updates to reach all the nameservers. I believe this is called "Propagation Seconds" in the nginx proxy manager UI: [HomeLab: Nginx-Proxy-Manager: Setup SSL Certificate with Domain Name in Cloudflare DNS | by Life-is-short--so--enjoy-it | Medium](https://medium.com/@life-is-short-so-enjoy-it/homelab-nginx-proxy-manager-setup-ssl-certificate-with-domain-name-in-cloudflare-dns-732af64ddc0b)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [June 26, 2024, 6:19am UTC](https://community.letsencrypt.org/t/challenges-have-failed/219066/4 "2024-06-26T06:19:31Z")

</div>

Closed on June 26, 2024, 6:19am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
