[GH-ISSUE #2151] Automate the DNS Challenge configuration process to generate SSL #1541

New issue

Closed

opened 2026-02-26 07:31:29 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @Tacioandrade on GitHub (Jul 8, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2151

Good afternoon everyone! I installed the nginx proxy manager to replace in my environment a shellscript that I use to generate my reverse proxies in environments that I don't have or pfSense (where I use the haproxy package).

I really liked the NPM interface, but I'm facing a small problem, I use the DNS challenge because in some of my clients, ports 80 and 443 are blocked by the internet providers, since they are broadband and non-dedicated links.

So far, so good, I was able to use the DNS Challenge option to generate the certificate, but every time I generate a different certificate, I have to:

Select the option: Request a new SSL Certificate
Select option: Use DNS Challenger
Select Cloudflare as Provider
Change Cloudflare Credentials File Content

In this case, I would like to request that in future versions, think about the option of creating a customized option in SSL Certificate such as: "Request a new SSL Certificate - Provider name", where when selecting this option, it automatically fills in the data DNS Provider, Token, etc.

That way, it would make the process of creating a new certificate much easier for environments like mine that have multiple https certificates for the same domain.

Originally created by @Tacioandrade on GitHub (Jul 8, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2151 Good afternoon everyone! I installed the nginx proxy manager to replace in my environment a shellscript that I use to generate my reverse proxies in environments that I don't have or pfSense (where I use the haproxy package). I really liked the NPM interface, but I'm facing a small problem, I use the DNS challenge because in some of my clients, ports 80 and 443 are blocked by the internet providers, since they are broadband and non-dedicated links. So far, so good, I was able to use the DNS Challenge option to generate the certificate, but every time I generate a different certificate, I have to: * Select the option: Request a new SSL Certificate * Select option: Use DNS Challenger * Select Cloudflare as Provider * Change Cloudflare Credentials File Content In this case, I would like to request that in future versions, think about the option of creating a customized option in SSL Certificate such as: "Request a new SSL Certificate - Provider name", where when selecting this option, it automatically fills in the data DNS Provider, Token, etc. That way, it would make the process of creating a new certificate much easier for environments like mine that have multiple https certificates for the same domain.

kerem

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

closed this issue
added the
enhancement

stale
labels

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Feb 13, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 13, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Mar 29, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 29, 2025): Issue was closed due to inactivity.

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#1541

No description provided.

Rows
Columns