NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Add label/comment field for each entry in Access Lists
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
Access List rules only show the raw IP/CIDR value. When a list has more than a few entries, it's hard to remember what each one represents (e.g., "office VPN," "client A's static IP," "monitoring server") without cross-referencing external notes.
Describe the solution you'd like
Add an optional label/description/comment field next to each IP/CIDR entry in the Access List "Access" tab. This would just be a UI-level annotation (not passed to nginx config, or optionally added as a # comment above the corresponding allow/deny line) so admins can identify at a glance what each rule is for.
Describe alternatives you've considered
Keeping a separate spreadsheet/doc mapping IPs to their purpose — error-prone and easy to let go stale.
Naming separate Access Lists per purpose — doesn't scale well when one list legitimately needs multiple distinct IPs/CIDRs.
Additional context
This would be purely additive (an optional text field per row) and wouldn't change existing behavior for lists that don't use it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Access Lists "Access" tab and the existing IP/CIDR entry model and rendering path. Trace how entries are persisted and whether they reach nginx configuration generation; done means an optional annotation is shown per row, existing lists keep working, and any chosen comment behavior is covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100