[GH-ISSUE #1193] Certificate renewal through Cloudflare stopped working. #3751

Closed
opened 2026-02-28 11:57:33 +03:00 by kerem · 12 comments
Owner

Originally created by @mosaati on GitHub (Jun 30, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1193

Describe the bug
I don't know when this has started. But certificate renewal stopped working. I had it previously running using Cloudflare DNS verification. and it was working fine. Now it just spams "Waiting for DNS record propagation".

and then the error: obtain cert error: error: one or more domains had a problem: [*.xx.xx] propagation: time limit exceeded: last error: authoritative nameservers: NS lou.ns.cloudflare.com.:53 did not return the expected TXT record.

Interestingly:
2 TXT records are created on Cloudflare, however there is a note on the records "The content field of TXT records must be in quotation marks. Cloudflare may add quotation marks on your behalf, which will not affect how the record works."

The error also reads other TXT spf records which are named the same as my domain as found instead of the named _acme-challenge TXT that were created.

To Reproduce
Steps to reproduce the behavior:

  1. add 1.1.1.1:53 DNS propagation
  2. create ACME user
  3. add Cloudflare DNS API credentials
  4. Try to create wildcard certificate.

Expected behavior
Issue or renew as expected.

Info (please complete the following information):

  • Server OS: [Ubuntu 24.10]
  • Server Arch: [x86,]
  • Nginx UI Version: [v2.1.9]
  • Your Browser: [Brave]

Additional context
No other changes were observed except of I upgraded the version.

Please let me know if there is a way to revert to an older version to test.

Originally created by @mosaati on GitHub (Jun 30, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1193 **Describe the bug** I don't know when this has started. But certificate renewal stopped working. I had it previously running using Cloudflare DNS verification. and it was working fine. Now it just spams "Waiting for DNS record propagation". and then the error: obtain cert error: error: one or more domains had a problem: [*.xx.xx] propagation: time limit exceeded: last error: authoritative nameservers: NS lou.ns.cloudflare.com.:53 did not return the expected TXT record. Interestingly: 2 TXT records are created on Cloudflare, however there is a note on the records "The content field of TXT records must be in quotation marks. Cloudflare may add quotation marks on your behalf, which will not affect how the record works." The error also reads other TXT spf records which are named the same as my domain as found instead of the named _acme-challenge TXT that were created. **To Reproduce** Steps to reproduce the behavior: 1. add 1.1.1.1:53 DNS propagation 2. create ACME user 3. add Cloudflare DNS API credentials 4. Try to create wildcard certificate. **Expected behavior** Issue or renew as expected. **Info (please complete the following information):** - Server OS: [Ubuntu 24.10] - Server Arch: [x86,] - Nginx UI Version: [v2.1.9] - Your Browser: [Brave] **Additional context** No other changes were observed except of I upgraded the version. Please let me know if there is a way to revert to an older version to test.
kerem 2026-02-28 11:57:33 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@0xJacky commented on GitHub (Jun 30, 2025):

It seems to be caused by the DNS cache. You can try again at a different time to see if the renewal can be successful. Currently, it is functioning properly here with me.

<!-- gh-comment-id:3019136275 --> @0xJacky commented on GitHub (Jun 30, 2025): It seems to be caused by the DNS cache. You can try again at a different time to see if the renewal can be successful. Currently, it is functioning properly here with me.
Author
Owner

@mosaati commented on GitHub (Jun 30, 2025):

The error is persisting for almost a week now. I'm not sure why.

I will do some debugging and report back.

Thank you for your time.

<!-- gh-comment-id:3019193455 --> @mosaati commented on GitHub (Jun 30, 2025): The error is persisting for almost a week now. I'm not sure why. I will do some debugging and report back. Thank you for your time.
Author
Owner

@0xJacky commented on GitHub (Jun 30, 2025):

You can try to use another DNS server like 8.8.8.8:53

<!-- gh-comment-id:3019198035 --> @0xJacky commented on GitHub (Jun 30, 2025): You can try to use another DNS server like 8.8.8.8:53
Author
Owner

@mosaati commented on GitHub (Jun 30, 2025):

Sure. Will try. Thanks.

<!-- gh-comment-id:3019203070 --> @mosaati commented on GitHub (Jun 30, 2025): Sure. Will try. Thanks.
Author
Owner

@mosaati commented on GitHub (Jul 10, 2025):

I just wanted to add that I had tried everything and nothing worked. I tried using DNS challenge in other tools and they worked as expected. Not sure where the problem is.

<!-- gh-comment-id:3056704107 --> @mosaati commented on GitHub (Jul 10, 2025): I just wanted to add that I had tried everything and nothing worked. I tried using DNS challenge in other tools and they worked as expected. Not sure where the problem is.
Author
Owner

@mosaati commented on GitHub (Jul 10, 2025):

I was able to issue a certificate by editing the text records as soon as they were created and adding quotes at the beginning and end of each record.

<!-- gh-comment-id:3056772495 --> @mosaati commented on GitHub (Jul 10, 2025): I was able to issue a certificate by editing the text records as soon as they were created and adding quotes at the beginning and end of each record.
Author
Owner

@0xJacky commented on GitHub (Jul 10, 2025):

OK, I know the problem. Thanks for your debug!

<!-- gh-comment-id:3056786679 --> @0xJacky commented on GitHub (Jul 10, 2025): OK, I know the problem. Thanks for your debug!
Author
Owner

@mosaati commented on GitHub (Jul 10, 2025):

Just to add, bug #1219 happened to me as well and had to delete them all. The text records keep creating to renew but never confirmed. I guess adding the quotes while testing fixed the issue for now but will happen again when it is time o renew.

<!-- gh-comment-id:3057045299 --> @mosaati commented on GitHub (Jul 10, 2025): Just to add, bug #1219 happened to me as well and had to delete them all. The text records keep creating to renew but never confirmed. I guess adding the quotes while testing fixed the issue for now but will happen again when it is time o renew.
Author
Owner

@0xJacky commented on GitHub (Jul 10, 2025):

Yes, I have noticed that.

<!-- gh-comment-id:3057183018 --> @0xJacky commented on GitHub (Jul 10, 2025): Yes, I have noticed that.
Author
Owner

@0xJacky commented on GitHub (Jul 19, 2025):

You can update to the dev version. This issue should have been fixed.

<!-- gh-comment-id:3092385763 --> @0xJacky commented on GitHub (Jul 19, 2025): You can update to the dev version. This issue should have been fixed.
Author
Owner

@mosaati commented on GitHub (Jul 20, 2025):

Tried the dev release and renewed right away. Thank you.

Just a minor note. Dev version is v2.1.13 (ddd538b5). When I switch the channel to stable the version is v2.1.12 but the page still says New version released and to upgrade to it. Not sure if I should create a bug.

<!-- gh-comment-id:3094478039 --> @mosaati commented on GitHub (Jul 20, 2025): Tried the dev release and renewed right away. Thank you. Just a minor note. Dev version is v2.1.13 (ddd538b5). When I switch the channel to stable the version is v2.1.12 but the page still says New version released and to upgrade to it. Not sure if I should create a bug.
Author
Owner

@0xJacky commented on GitHub (Jul 20, 2025):

Tried the dev release and renewed right away. Thank you.

Just a minor note. Dev version is v2.1.13 (ddd538b5). When I switch the channel to stable the version is v2.1.12 but the page still says New version released and to upgrade to it. Not sure if I should create a bug.

This is normal and there's no need to pay attention to it.

<!-- gh-comment-id:3094480644 --> @0xJacky commented on GitHub (Jul 20, 2025): > Tried the dev release and renewed right away. Thank you. > > Just a minor note. Dev version is v2.1.13 (ddd538b5). When I switch the channel to stable the version is v2.1.12 but the page still says New version released and to upgrade to it. Not sure if I should create a bug. This is normal and there's no need to pay attention to it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-ui#3751
No description provided.