[GH-ISSUE #763] IP-Access List Not Working With 10.0.0.1/24 #648

Closed
opened 2026-02-26 06:33:49 +03:00 by kerem · 1 comment
Owner

Originally created by @varunsridharan on GitHub (Dec 7, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/763

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Are you sure you're not using someone else's docker image?
  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?

Describe the bug
I am trying to use 10.0.0.1/24 in IP Access List because my local network is configured with that IP and I want to allow some proxy sites only from my local network

But nginx throwing some error

2020/12/07 12:51:21 [warn] 193#193: low address bits of 10.0.0.1/24 are meaningless in /data/nginx/proxy_host/4.conf:47

To Reproduce

  1. Create an Access List With the IP 10.0.0.1/24

Expected behavior
IP Allow list should work

Screenshots
Access List Base

IP List

Operating System
Ubuntu

Originally created by @varunsridharan on GitHub (Dec 7, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/763 **Checklist** - [x] Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - [x] Are you sure you're not using someone else's docker image? - [x] If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? **Describe the bug** I am trying to use `10.0.0.1/24` in **IP Access List** because my local network is configured with that IP and I want to allow some proxy sites only from my local network But nginx throwing some error ``` 2020/12/07 12:51:21 [warn] 193#193: low address bits of 10.0.0.1/24 are meaningless in /data/nginx/proxy_host/4.conf:47 ``` **To Reproduce** 1. Create an Access List With the IP `10.0.0.1/24` **Expected behavior** IP Allow list should work **Screenshots** ![Access List Base](https://s2.do-spaces.com/2020/Dec/07/160734602133.jpg) ![IP List](https://s2.do-spaces.com/2020/Dec/07/160734608913.jpg) **Operating System** Ubuntu
kerem 2026-02-26 06:33:49 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@mbenkler commented on GitHub (Dec 26, 2020):

your subnet is 10.0.0.0/24 and not 10.0.0.1/24 if yout configure your subnet right in the access list it will work.

There's no such network as 10.0.0.1/24, because it doesn't start on a legitimate boundary between /24 network ranges. The last bit of the address is set, but is meaningless in this context. The correct address would be 10.0.0.0/24, which means the range from 10.0.0.0 to 10.0.0.255

<!-- gh-comment-id:751330679 --> @mbenkler commented on GitHub (Dec 26, 2020): your subnet is **10.0.0.0/24** and not 10.0.0.1/24 if yout configure your subnet right in the access list it will work. There's no such network as 10.0.0.1/24, because it doesn't start on a legitimate boundary between /24 network ranges. The last bit of the address is set, but is meaningless in this context. The correct address would be 10.0.0.0/24, which means the range from 10.0.0.0 to 10.0.0.255
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#648
No description provided.