[GH-ISSUE #630] Add Domain-Zones and API-Key Management #533

Closed
opened 2026-02-26 06:33:17 +03:00 by kerem · 4 comments
Owner

Originally created by @typoworx-de on GitHub (Oct 5, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/630

Is your feature request related to a problem? Please describe.
Not at all. It would be a benefit for feature improvement.

Currently it is not possible to store the Cloudflare API Key for SSL-Management and given Domains. Also it is not possible to restrict access for Domains (also their SSL Certs) to users.

This could be a great benefit for new features:

  1. Add a new Menu "Zones" where Domain-Zones and optional User-Restrictions (who can access which Zone/Domain/SSL Certs for the given Domain).

  2. Also we could assign Cloudflare API-Key to a Domain Zone (see 1.). For this I think it would be most flexible having a API Management Menu being able to Choose Cloudflare and enter the API-Key and optionally to which Zones it applies (I like to use Cloudflare restrictions to selective domains).

Originally created by @typoworx-de on GitHub (Oct 5, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/630 **Is your feature request related to a problem? Please describe.** Not at all. It would be a benefit for feature improvement. Currently it is not possible to store the Cloudflare API Key for SSL-Management and given Domains. Also it is not possible to restrict access for Domains (also their SSL Certs) to users. This could be a great benefit for new features: 1. Add a new Menu "Zones" where Domain-Zones and optional User-Restrictions (who can access which Zone/Domain/SSL Certs for the given Domain). 2. Also we could assign Cloudflare API-Key to a Domain Zone (see 1.). For this I think it would be most flexible having a API Management Menu being able to Choose Cloudflare and enter the API-Key and optionally to which Zones it applies (I like to use Cloudflare restrictions to selective domains).
kerem 2026-02-26 06:33:17 +03:00
Author
Owner

@MDHMatt commented on GitHub (Jun 16, 2021):

this would be great addition. Swag guys implemented the api access but if you could do it so that if it was connected then when you add a proxy it can also add a dns record if it doesn't exist

<!-- gh-comment-id:862562826 --> @MDHMatt commented on GitHub (Jun 16, 2021): this would be great addition. Swag guys implemented the api access but if you could do it so that if it was connected then when you add a proxy it can also add a dns record if it doesn't exist
Author
Owner

@zeus86 commented on GitHub (Aug 1, 2022):

...especially because nginx-pm stores the dns-key anyways. for one to renew the certs, but also they are visible in the audit-log-details.

<!-- gh-comment-id:1201470192 --> @zeus86 commented on GitHub (Aug 1, 2022): ...especially because nginx-pm stores the dns-key anyways. for one to renew the certs, but also they are visible in the audit-log-details.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 25, 2024):

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

<!-- gh-comment-id:2017068688 --> @github-actions[bot] commented on GitHub (Mar 25, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (May 5, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2849747576 --> @github-actions[bot] commented on GitHub (May 5, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
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#533
No description provided.