starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2150] Firewall for the Nginx Proxy Manager #1540

New issue

Closed

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

kerem commented

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

Owner

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

Is your feature request related to a problem? Please describe.

No, but it can be usefull to prevent Problems

Describe the solution you'd like

Can you add a Firewall/IPTables to the UI so you can block IPs over the UI

Describe alternatives you've considered

You can make Lists and add IPs that are blocked and to every Host you can add one of the Lists like the Access Lists.

Additional context

Thank you

Originally created by @NixNux123 on GitHub (Jul 8, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2150  **Is your feature request related to a problem? Please describe.**  No, but it can be usefull to prevent Problems **Describe the solution you'd like**  Can you add a Firewall/IPTables to the UI so you can block IPs over the UI **Describe alternatives you've considered**  You can make Lists and add IPs that are blocked and to every Host you can add one of the Lists like the Access Lists. **Additional context**  Thank you

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

@the1ts commented on GitHub (Jul 9, 2022):

I'm not sure that the correct place for IP blocking is on the container for NPM. To run iptables inside a container, I believe you need to run the container with NET_ADMIN capabilities, this means all traffic for all containers will be available on that container. This sounds like an increase for insecurity. The place for IPs to be stopped is as early as possible rather than at the container level which is almost the last layer.

@the1ts commented on GitHub (Jul 9, 2022): I'm not sure that the correct place for IP blocking is on the container for NPM. To run iptables inside a container, I believe you need to run the container with NET_ADMIN capabilities, this means all traffic for all containers will be available on that container. This sounds like an increase for insecurity. The place for IPs to be stopped is as early as possible rather than at the container level which is almost the last layer.

kerem commented

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

Author

Owner

@Issykul commented on GitHub (Jul 12, 2022):

Use ufw instead on your docker host. Way better security and ease of use.

@Issykul commented on GitHub (Jul 12, 2022): Use `ufw` instead on your docker host. Way better security and ease of use.

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:30 +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#1540

No description provided.

Rows
Columns