[GH-ISSUE #1723] How to whitelist IP for the admin gui #1282

New issue

Closed

opened 2026-02-26 06:36:33 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @jayjupdhig on GitHub (Jan 3, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1723

we have an external plesk server and we would only allow the proxy manager via that ip on port 81. how to realize?

Originally created by @jayjupdhig on GitHub (Jan 3, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1723 we have an external plesk server and we would only allow the proxy manager via that ip on port 81. how to realize?

kerem closed this issue

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

kerem commented

2026-02-26 06:36:34 +03:00

Author

Owner

@chaptergy commented on GitHub (Jan 3, 2022):

Please stop. This issue tracker is not your personal support chat. We can't help with every small little hiccup you experience. Debug a little yourself. Google the problem. Look for already existing issues. Just try out different things. A few of the issues you have opened in the past hours wouldn't have been necessary if you had googled the problem. For help with specific proxy setups, there is the reddit community. This issue tracker is only for bugs and feature requests.

But to answer your question, you can do it easily through port 80 / 443 by creating a proxy host with an access list. (Note, you might need https://github.com/jc21/nginx-proxy-manager/discussions/1724). Add this IP in the access list. Unexpose / remove port 81 in the docker compose.

If it is absolutely necessary to keep it on port 81, there is no other way than to mount a different production.conf into the container to /etc/nginx/conf.d/production.conf, which contains a modified nginx config with an allow and deny directive.

@chaptergy commented on GitHub (Jan 3, 2022): Please stop. This issue tracker is not your personal support chat. We can't help with every small little hiccup you experience. Debug a little yourself. Google the problem. Look for already existing issues. Just try out different things. A few of the issues you have opened in the past hours wouldn't have been necessary if you had googled the problem. For help with specific proxy setups, there is the [reddit community](https://www.reddit.com/r/nginxproxymanager/). This issue tracker is only for bugs and feature requests. But to answer your question, you can do it easily through port 80 / 443 by creating a proxy host with an access list. (Note, you might need https://github.com/jc21/nginx-proxy-manager/discussions/1724). Add this IP in the access list. Unexpose / remove port 81 in the docker compose. If it is absolutely necessary to keep it on port 81, there is no other way than to mount a different [`production.conf`](https://github.com/jc21/nginx-proxy-manager/blob/develop/docker/rootfs/etc/nginx/conf.d/production.conf) into the container to `/etc/nginx/conf.d/production.conf`, which contains a modified nginx config with an allow and deny directive.

kerem commented

2026-02-26 06:36:34 +03:00

Author

Owner

@jayjupdhig commented on GitHub (Jan 11, 2022):

Another question HERE: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1736

@jayjupdhig commented on GitHub (Jan 11, 2022): Another question HERE: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1736

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

No description provided.

Rows
Columns