You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use Access Lists to bock access to certain websites from outside of 192.168.0.0/24. In theory this would block access outside my home network:
The client ip seems to be one from the internal docker network instead of my actual system's ip: 192.168.0.49. I'm guessing if I added the ip from the log it would work, but that defeats the purpose of the feature for me.
I'm using docker-compose with a yml like so:
services:
npm:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
# These ports are in format <host-port>:<container-port>
- '80:80'
- '443:443'
- '81:81'
environment:
- PUID=1000
- GUID=1000
volumes:
- z_drive_npm_data:/data
- z_drive_npm_letsencrypt:/etc/letsencrypt
What type of network settings can I use to be able to use Access Lists to block 'real ips' instead of docker-internal ones?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey folks,
I'm trying to use Access Lists to bock access to certain websites from outside of 192.168.0.0/24. In theory this would block access outside my home network:
When trying to access, i get:
In the nginx access log i see:
The client ip seems to be one from the internal docker network instead of my actual system's ip:
192.168.0.49
. I'm guessing if I added the ip from the log it would work, but that defeats the purpose of the feature for me.I'm using docker-compose with a yml like so:
What type of network settings can I use to be able to use Access Lists to block 'real ips' instead of docker-internal ones?
Beta Was this translation helpful? Give feedback.
All reactions