starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #3773] [ FEATURE REQUEST ] : categories #2485

New issue

Closed

opened 2026-02-26 07:35:44 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:35:44 +03:00

Owner

Originally created by @Tygo-van-den-Hurk on GitHub (May 24, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3773

Is your feature request related to a problem? Please describe.
I personally run a lot of services on the on machine using docker. Having this many services of even multiple domains running can cause things to look a little more chaotic then I'd like.

Describe the solution you'd like
I wish there was a sort of folder structure to put your proxy/redirection hosts into. So for example, when you click on proxy hosts, instead of getting a long list of your 50 redirection hosts, you can add categories which you can expand.

begin example

example.com (or any name of your chosing)

service-a.host1.example.com
service-b.host2.example.com
service-c.host3.example.com

example.net (or any name of your chosing)

service-d.host4.example.net
service-e.host5.example.net
service-f.host6.example.net

example.org (or any name of your chosing)

service-g.host7.example.org
service-h.host8.example.org
service-k.host9.example.org

end example

Describe alternatives you've considered
I considered running multiple NPM containers one for each domain, so that the primary proxies to the secondary, which proxies to the resource, but this is clunky, consumes more resources. Makes me have to open more windows, log in at different things etc etc

Just not ideal when a feature request would do the trick.

I saw this issue with a similar request, which was completed, but I couldn't find a resourse online on how I could create the effect I'm looking for.

Additional context
This is an example I spun up to give a rough idea of what it'd look like:

Originally created by @Tygo-van-den-Hurk on GitHub (May 24, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3773 **Is your feature request related to a problem? Please describe.** I personally run a lot of services on the on machine using docker. Having this many services of even multiple domains running can cause things to look a little more chaotic then I'd like. **Describe the solution you'd like** I wish there was a sort of folder structure to put your proxy/redirection hosts into. So for example, when you click on proxy hosts, instead of getting a long list of your 50 redirection hosts, you can add categories which you can expand. <hr><center>begin example</center><hr> <details> <summary> example.com (or any name of your chosing) </summary> <ul> <li> service-a.host1.example.com </li> <li> service-b.host2.example.com </li> <li> service-c.host3.example.com </li> </ul> </details> <details> <summary> example.net (or any name of your chosing) </summary> <ul> <li> service-d.host4.example.net </li> <li> service-e.host5.example.net </li> <li> service-f.host6.example.net </li> </ul> </details> <details> <summary> example.org (or any name of your chosing) </summary> <ul> <li> service-g.host7.example.org </li> <li> service-h.host8.example.org </li> <li> service-k.host9.example.org </li> </ul> </details> <hr><center>end example</center><hr> **Describe alternatives you've considered** I considered running multiple NPM containers one for each domain, so that the primary proxies to the secondary, which proxies to the resource, but this is clunky, consumes more resources. Makes me have to open more windows, log in at different things etc etc Just not ideal when a feature request would do the trick. I saw [this issue](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1313) with a similar request, which was completed, but I couldn't find a resourse online on how I could create the effect I'm looking for. **Additional context** This is an example I spun up to give a rough idea of what it'd look like: ![Screenshot 2024-05-24 at 10-41-52 Nginx Proxy Manager](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/91738110/545005d9-3cc0-45ed-886b-a6492753ac05)

kerem

2026-02-26 07:35:44 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 07:35:45 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 26, 2024):

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

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

kerem commented

2026-02-26 07:35:45 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 17, 2026):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jan 17, 2026): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 08:31:10 +03:00

[PR #2507] [MERGED] Update certbot desec plugin fixes #2485 #3579

kerem referenced this issue

2026-02-26 08:31:17 +03:00

[PR #2686] [MERGED] v2.9.20 #3610

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

No description provided.

Rows
Columns