mirror of
https://github.com/0xJacky/nginx-ui.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #1523] DNS-01 Let's Encrypt request issue #6619
Labels
No labels
Q/A
bug
casdoor
dependencies
docker
documentation
duplicate
enhancement
help wanted
invalid
lego
platform:openwrt
platform:windows
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-ui#6619
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @astrdev on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1523
Describe the bug
Here, I want to create a Let's Encrypt cert for "mydomain.ch" and "*.mydomain.ch" (while "mydomain.ch" being just a placeholder). I purchased "mydomain.ch" at Infomaniak. So for that DNS provider, I created the DNS credentials for the Infomaniak provider with a correct access token.
And then, when I want to issue a certificate from the Certificates List, putting the two domain above, nginx-ui cannot create the cert.
But, for example, while I'm using Nginx Proxy Manager (because I used that before testing nginx-ui), it can create that cert while providing the same domains above.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Successfully create the Let's Encrypt cert for the above domains.
Screenshots
The "Issue Certificate" creation box:

Full trace logs while doing it (redacted some info):
While "proxy.on.local" being the actual nginx-ui host and "on.local" being my LAN DNS zone.
Info (please complete the following information):
Additional context
Running via docker-compose, the full compose file:
@0xJacky commented on GitHub (Feb 8, 2026):
A public domain name is required to apply for the certificate.
@astrdev commented on GitHub (Feb 12, 2026):
What does this has to do with this issue? My domain was always private (with THE WHOIS info redacted, if it's what you mean), but it didn't stop me to create the same cert (for the both domains above) in NPM before.
Do you have an idea?