[GH-ISSUE #1737] Is it possible to setup LAN_ONLY access to a certain webpage? #1292

Closed
opened 2026-02-26 06:36:36 +03:00 by kerem · 3 comments
Owner

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

Hi,
Is it possible to setup LAN_ONLY access to a certain webpage?
e.g. I would like to have LAN-ONLY access to subdomain.mydomain.com/index.json

Can anyone point in the right direction.

TIA

Originally created by @BobWs on GitHub (Jan 7, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1737 Hi, Is it possible to setup **LAN_ONLY** access to a certain webpage? e.g. I would like to have **LAN-ONLY** access to `subdomain.mydomain.com/index.json` Can anyone point in the right direction. TIA
kerem 2026-02-26 06:36:36 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Kieffer87 commented on GitHub (Jan 7, 2022):

You can setup LAN only access by creating a new Access List that allows your LAN subnet(s) for example 192.168.1.0/24 The default action is to deny if it doesn't match.

Once the Access List has been created, you assign the list to the proxy host.

<!-- gh-comment-id:1007543139 --> @Kieffer87 commented on GitHub (Jan 7, 2022): You can setup LAN only access by creating a new Access List that allows your LAN subnet(s) for example `192.168.1.0/24` The default action is to deny if it doesn't match. Once the Access List has been created, you assign the list to the proxy host.
Author
Owner

@BobWs commented on GitHub (Jan 8, 2022):

You can setup LAN only access by creating a new Access List that allows your LAN subnet(s) for example 192.168.1.0/24 The default action is to deny if it doesn't match.

Once the Access List has been created, you assign the list to the proxy host.

I have already done that, but the certain page subdomain.mydomain.com/index.json is still accessible from the internet.

I also tried to add this into the advanced tab/custom nginx configuration

location /public {
  allow 192.168.0.0/24;
  deny all;
}

That is the folder where the index.json file is, but that is not working either.

<!-- gh-comment-id:1007904723 --> @BobWs commented on GitHub (Jan 8, 2022): > You can setup LAN only access by creating a new Access List that allows your LAN subnet(s) for example `192.168.1.0/24` The default action is to deny if it doesn't match. > > Once the Access List has been created, you assign the list to the proxy host. I have already done that, but the certain page `subdomain.mydomain.com/index.json` is still accessible from the internet. I also tried to add this into the advanced tab/custom nginx configuration ``` location /public { allow 192.168.0.0/24; deny all; } ``` That is the folder where the index.json file is, but that is not working either.
Author
Owner

@BobWs commented on GitHub (Jan 8, 2022):

Sorry my bad!
I totally forgot that I also had this subdomain on a external server, that's why the page was still reachable from the internet.
So when I removed it from the remote server, NPM is working fine with LAN ONLY access list.

Anyway thanks for reaching out!

<!-- gh-comment-id:1007996442 --> @BobWs commented on GitHub (Jan 8, 2022): Sorry my bad! I totally forgot that I also had this subdomain on a external server, that's why the page was still reachable from the internet. So when I removed it from the remote server, NPM is working fine with LAN ONLY access list. Anyway thanks for reaching out!
Sign in to join this conversation.
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#1292
No description provided.