mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1974] "Proxy Host Group" feature #1427
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1427
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 @HomelabHaven on GitHub (Apr 4, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1974
Hello there,
first of all I'd like to commend you on how much of a pleasure it is to setup and use nginx-proxy-manager. I switched from haproxy on my pfsense router about a week back and have had no regrets except for one.
I couldn't find this topic as a request and hope that I am not duplicating one.
Despite not being a reverse proxy expert by any stretch of the imagination it seems like one big downside to nginx-proxy-manager after the switch from haproxy that one cannot group proxy hosts together to have certain settings apply to all of them. In addition it would be useful if all proxy hosts could be triggered to reload if a shared setting from a "proxy host group" were to be changed.
My thoughts are that (for example) the "SSL" and "Access List" portions of the setting would fall into the shared "proxy host group" settings category.
@github-actions[bot] commented on GitHub (Feb 20, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 5, 2025):
Issue was closed due to inactivity.