[GH-ISSUE #1283] Cloudflare DNS not finding zone #2652

New issue

Closed

opened 2026-02-27 12:25:14 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 12:25:14 +03:00

Owner

Originally created by @Glujaz on GitHub (Aug 2, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1283

Describe the bug
I am trying to generate an SSL certificate within nginx ui.
I created the dns credentials and ACME user. When issuing a certificate, I get an error that it can not find the correct zone :

obtain cert error: error: one or more domains had a problem: [.glujaz.fr] [.glujaz.fr] acme: error presenting token: cloudflare: failed to find zone fr.: zone could not be found [glujaz.fr] [glujaz.fr] acme: error presenting token: cloudflare: failed to find zone fr.: zone could not be found

(real domain name replaced)
The token is valid, otherwise I would have gotten an error (already tested with a bad token), and the zone exist under glujaz.fr and is readable and modifiable as per cloudflare API token settings.

I even made a fresh reinstall on a dedicated LXC container to be sure that it was not my configuration

I have the feeling it is not sending the correct domain chain to the command which executes the certificates (which I understood, is not Certbot)

To Reproduce

This is what I did on the temporally newly created install

Create a new LXC container with debian 12.
Execute:
apt update
apt upgrade
apt install nano curl nginx
bash -c "$(curl -L https://cloud.nginxui.com/install.sh)" @ install

finish the configuration of nginx (user = admin, password=adminadmin)

On cloudflare, login in, go to account, and API Token.
Create a new one, rename it "Nginx UI"
Set rules:
Autorisation : Zone, DNS, Modify
Ressources of the zone : include, all zones

Then, get the token key
(cloud flare is not in English, maybe my translation are wrong)

in nginx ui freshly installed:

Acme User, create a new one : type a describing name, and an email, leave the rest as default

DNS credentials: add
Type is describing name
Set cloudflare
put the token key in "CF_DNS_API_TOKEN" (though CLOUDFLARE_DNS_API_TOKEN seems to also work)

save and go to certificates list, and issue certificate

Set wildcard (the problem is the same also for a specific domaine)
Set domain name : glujaz.fr (*. is added by nginx UI)
key type as default (EC256)
Acme user : select the unique one, just created
DNS provider : Cloudflare
Credentials : select the unique one, just created

Don't change anything else, and hit next

Expected behavior
Nginx UI finds glujaz.fr zone, and do the TXT change, and Obtaining the certificate

Info (please complete the following information):

Server OS:Debian 12 (LXC)
Server Arch: x86
Nginx UI Version: 2.1.14
Your Browser: Safari

Additional context
I made a mistake and hade to reinstall NGINX fully, while keeping nginx UI. the reinstall removed my previously configured certificates, so I wanted to reconfigure it. However, even with a fresh install, the problem of connecting to cloudflare is still existant.

Originally created by @Glujaz on GitHub (Aug 2, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1283 **Describe the bug** I am trying to generate an SSL certificate within nginx ui. I created the dns credentials and ACME user. When issuing a certificate, I get an error that it can not find the correct zone : obtain cert error: error: one or more domains had a problem: [*.glujaz.fr] [*.glujaz.fr] acme: error presenting token: cloudflare: failed to find zone fr.: zone could not be found [glujaz.fr] [glujaz.fr] acme: error presenting token: cloudflare: failed to find zone fr.: zone could not be found (real domain name replaced) The token is valid, otherwise I would have gotten an error (already tested with a bad token), and the zone exist under glujaz.fr and is readable and modifiable as per cloudflare API token settings. I even made a fresh reinstall on a dedicated LXC container to be sure that it was not my configuration I have the feeling it is not sending the correct domain chain to the command which executes the certificates (which I understood, is not Certbot) **To Reproduce** This is what I did on the temporally newly created install Create a new LXC container with debian 12. Execute: apt update apt upgrade apt install nano curl nginx bash -c "$(curl -L https://cloud.nginxui.com/install.sh)" @ install finish the configuration of nginx (user = admin, password=adminadmin) On cloudflare, login in, go to account, and API Token. Create a new one, rename it "Nginx UI" Set rules: Autorisation : Zone, DNS, Modify Ressources of the zone : include, all zones Then, get the token key (cloud flare is not in English, maybe my translation are wrong) in nginx ui freshly installed: Acme User, create a new one : type a describing name, and an email, leave the rest as default DNS credentials: add Type is describing name Set cloudflare put the token key in "CF_DNS_API_TOKEN" (though CLOUDFLARE_DNS_API_TOKEN seems to also work) save and go to certificates list, and issue certificate Set wildcard (the problem is the same also for a specific domaine) Set domain name : glujaz.fr (*. is added by nginx UI) key type as default (EC256) Acme user : select the unique one, just created DNS provider : Cloudflare Credentials : select the unique one, just created Don't change anything else, and hit next **Expected behavior** Nginx UI finds glujaz.fr zone, and do the TXT change, and Obtaining the certificate **Info (please complete the following information):** - Server OS:Debian 12 (LXC) - Server Arch: x86 - Nginx UI Version: 2.1.14 - Your Browser: Safari **Additional context** I made a mistake and hade to reinstall NGINX fully, while keeping nginx UI. the reinstall removed my previously configured certificates, so I wanted to reconfigure it. However, even with a fresh install, the problem of connecting to cloudflare is still existant.