starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-28 10:55:54 +03:00

[GH-ISSUE #364] Add Letsencrypt cert authentication method choice #312

New issue

Closed

opened 2026-02-26 06:32:13 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:32:13 +03:00

Owner

Originally created by @lobradov on GitHub (Apr 12, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/364

Problem statement

Nginx-proxy-manager only supports "webhook" authentication method, implying that tcp/80 and/or tcp/443 have to be accessible from the internet.
That is very rarely the case on residential broadband connections.
Letsencrypt also supports various DNS methods that do not require said ports to be accessible.

Proposed solution

Add options on "Add SSL certificate" that would allow to choose:

LetsEncrypt Auth method (Webhook or DNS)
DNS parameters, if DNS option is chosen

Additional info

Two side projects exist that make auth/cert management with Letsencrypt easier:

dehydrated - https://github.com/dehydrated-io/dehydrated. - bash for Letsencrypt
lexicon - https://github.com/AnalogJ/lexicon - DNS record manipulation

Combination of both allows necessary tokens/challenges to be updated for Letsencrypt over DNS to work.

Home Assistant "DuckDNS add-on" essentially uses both to renew both DuckDNS registration (less important) and LetsEncrypt certificate.

Originally created by @lobradov on GitHub (Apr 12, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/364 ## Problem statement Nginx-proxy-manager only supports "webhook" authentication method, implying that tcp/80 and/or tcp/443 have to be accessible from the internet. That is very rarely the case on residential broadband connections. Letsencrypt also supports various DNS methods that do not require said ports to be accessible. ## Proposed solution Add options on "Add SSL certificate" that would allow to choose: - LetsEncrypt Auth method (Webhook or DNS) - DNS parameters, if DNS option is chosen ## Additional info Two side projects exist that make auth/cert management with Letsencrypt easier: - dehydrated - https://github.com/dehydrated-io/dehydrated. - bash for Letsencrypt - lexicon - https://github.com/AnalogJ/lexicon - DNS record manipulation Combination of both allows necessary tokens/challenges to be updated for Letsencrypt over DNS to work. Home Assistant "DuckDNS add-on" essentially uses both to renew both DuckDNS registration (less important) and LetsEncrypt certificate.

kerem

2026-02-26 06:32:13 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 06:32:13 +03:00

Author

Owner

@jodab commented on GitHub (Apr 16, 2020):

Support for dnsapi such as what acme.sh does would indeed be a nice addition.

@jodab commented on GitHub (Apr 16, 2020): Support for dnsapi such as what acme.sh does would indeed be a nice addition.

kerem commented

2026-02-26 06:32:13 +03:00

Author

Owner

@vic4hub commented on GitHub (Dec 23, 2020):

hey guys, I see that this now seems to be in, however, I am using duckdns and that is unfortunately not an option. As for the aforementioned "webhook" option, as far as I understand it all that is needed is to open up ports 80 and 443 - however it seems to be broken. Seems proxy manager does not expose /.well-known/acme-challenge/ out the gate, please advise.

@vic4hub commented on GitHub (Dec 23, 2020): hey guys, I see that this now seems to be in, however, I am using duckdns and that is unfortunately not an option. As for the aforementioned "webhook" option, as far as I understand it all that is needed is to open up ports 80 and 443 - however it seems to be broken. Seems proxy manager does not expose /.well-known/acme-challenge/ out the gate, please advise.

kerem commented

2026-02-26 06:32:13 +03:00

Author

Owner

@chaptergy commented on GitHub (May 9, 2021):

@vic4hub please open a separate issue for this.

DNS challenges are now supported (through certbot and its dns plugins).

@chaptergy commented on GitHub (May 9, 2021): @vic4hub please open a separate issue for this. DNS challenges are now supported (through certbot and its dns plugins).

kerem commented

2026-02-26 06:32:13 +03:00

Author

Owner

@chaptergy commented on GitHub (May 10, 2021):

@vic4hub BTW, duckDNS is in our supported providers list, however I think it won't work, but I already created a pull request in the duckDNS plugin repo to fix this.

@chaptergy commented on GitHub (May 10, 2021): @vic4hub BTW, duckDNS is in our supported providers list, however I think it won't work, but I already created a pull request in the duckDNS plugin repo to fix this.

kerem referenced this issue

2026-02-26 07:38:31 +03:00

[PR #351] [MERGED] v2.2.2 Release #3225

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-proxy-manager-NginxProxyManager#312

No description provided.

Rows
Columns