starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #722] Restrict access to Admin Panel from outside the lan #612

New issue

Closed

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

kerem commented

2026-02-26 06:33:39 +03:00

Owner

Originally created by @rParslow on GitHub (Nov 15, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/722

I've redirected ports 80/443 to the IP where nginx-proxy-manager is hosted
From the internet if I try to connect to my.public.ip:81 the admin panel is prompted
Same with a domain I've wildcardly redirected a domain to my IP and dummy.mydomaine.tld:81 prompt admin panel

Could it be an settings to allow only connecting to the admin panel from the lan ?

Originally created by @rParslow on GitHub (Nov 15, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/722 Hi I've redirected ports 80/443 to the IP where nginx-proxy-manager is hosted From the internet if I try to connect to my.public.ip:81 the admin panel is prompted Same with a domain I've wildcardly redirected a domain to my IP and dummy.mydomaine.tld:81 prompt admin panel Could it be an settings to allow only connecting to the admin panel from the lan ?

kerem

2026-02-26 06:33:39 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@Wadera commented on GitHub (Nov 16, 2020):

Disable port forwarding for port 81 ;)
Set new proxy, example:
Restrict IP for your proxy server for your own and local, for example:

satisfy any;
allow 192.168.0.1/15;
allow 172.0.0.1/8;
allow 123.123.123.123;
deny all;

Where 192.168.0.1 is your local network and 1233.123.123.123 is your own IP ;)

@Wadera commented on GitHub (Nov 16, 2020): 1. Disable port forwarding for port 81 ;) 2. Set new proxy, example: ![image](https://user-images.githubusercontent.com/407236/99252283-a3536b00-2806-11eb-8c5a-1cf6fdd772b2.png) 3. Restrict IP for your proxy server for your own and local, for example: ``` satisfy any; allow 192.168.0.1/15; allow 172.0.0.1/8; allow 123.123.123.123; deny all; ``` ![image](https://user-images.githubusercontent.com/407236/99252480-ee6d7e00-2806-11eb-8d0d-ce44d916136c.png) Where `192.168.0.1` is your local network and `1233.123.123.123` is your own IP ;)

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@rParslow commented on GitHub (Nov 16, 2020):

Thanks @Wadera it works fine when I'm on my Lan

But when I'm from an external IP
As I've a wildcard domain pointing on my Ngnix Reverse proxy ponting on anysubdomain.maydomain.tld:81 or 42.42.42.42:81
prompt the login panel of the manager.

Where can I modify the host config of the pannel ?

@rParslow commented on GitHub (Nov 16, 2020): Thanks @Wadera it works fine when I'm on my Lan But when I'm from an external IP As I've a wildcard domain pointing on my Ngnix Reverse proxy ponting on anysubdomain.maydomain.tld:81 or 42.42.42.42:81 prompt the login panel of the manager. Where can I modify the host config of the pannel ?

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@Wadera commented on GitHub (Nov 16, 2020):

Like I said on first post: If you using proxy over some router - block port 81 (disable forwarding).

Disable port forwarding for port 81 ;)

If you don't have access to router - then block in on your Dorcker host machine over Firewall (example: iptables):
https://stackoverflow.com/questions/7423309/iptables-block-access-to-port-8000-except-from-ip-address

@Wadera commented on GitHub (Nov 16, 2020): Like I said on first post: If you using proxy over some router - block port 81 (disable forwarding). > Disable port forwarding for port 81 ;) If you don't have access to router - then block in on your Dorcker host machine over Firewall (example: iptables): https://stackoverflow.com/questions/7423309/iptables-block-access-to-port-8000-except-from-ip-address

kerem commented

2026-02-26 06:33:39 +03:00

Author

Owner

@Rustymage commented on GitHub (Jan 12, 2021):

Try accessing from another location, such as someone else's internet connection or over a VPN.

I think you'll find you won't be able to connect.

I believe it only happens when you're on the same LAN. There's a technical explanation that I'll find the link too. However, in the meantime, try my suggestion.

@Rustymage commented on GitHub (Jan 12, 2021): Try accessing from another location, such as someone else's internet connection or over a VPN. I think you'll find you won't be able to connect. I believe it only happens when you're on the same LAN. There's a technical explanation that I'll find the link too. However, in the meantime, try my suggestion.

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

No description provided.

Rows
Columns