[GH-ISSUE #1381] Creating of new certificates via HTTP method, rather than DNS only. #3872

New issue

Closed

opened 2026-02-28 11:58:06 +03:00 by kerem · 1 comment

kerem commented

2026-02-28 11:58:06 +03:00

Owner

Originally created by @firengate on GitHub (Oct 6, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1381

Hello!

When you click on 'Issue Certificate', you are only offered the option to create new certificates via a DNS provider. However, HTTP-based methods do exist.
Yes, you can change the method to HTTP for a certificate that has already been created by nginx-ui, for example, via the DNS method. Nevertheless, you cannot create a certificate without DNS.

Not in all cases do you have access to the DNS zone, sometimes a domain simply points to your proxy, but you require a certificate.

Originally created by @firengate on GitHub (Oct 6, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1381 Hello! When you click on 'Issue Certificate', you are only offered the option to create new certificates via a DNS provider. However, HTTP-based methods do exist. Yes, you can change the method to HTTP for a certificate that has already been created by nginx-ui, for example, via the DNS method. Nevertheless, you cannot create a certificate without DNS. Not in all cases do you have access to the DNS zone, sometimes a domain simply points to your proxy, but you require a certificate.

kerem

2026-02-28 11:58:06 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-28 11:58:07 +03:00

Author

Owner

@0xJacky commented on GitHub (Oct 6, 2025):

If you want to use HTTP Challenge, please find "Encrypt website with Let's Encrypt" in the site editing page.

@0xJacky commented on GitHub (Oct 6, 2025): If you want to use HTTP Challenge, please find "Encrypt website with Let's Encrypt" in the site editing page.