-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes
- Are you sure you're not using someone else's docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes. They do not seem to different between WAN and LAN IPs as I do here.
Describe the bug
I am only 50% sure this is not a me problem. When I forward ports 80 and 433 from my router to my machine running NPM, client IPs are showing up correctly in my services (I am using Nextcloud as my test example). When I access my services via my local DNS server, staying within my LAN, all of my IPs show up as the same 192.168.1.x IP, which I assume is the Docker IP of the NPM container, since my LAN IPs are restricted to a 192.168.4.0/24 subnet.
Nginx Proxy Manager Version
v2.9.18
To Reproduce
Steps to reproduce the behavior:
- Set up service, e.g. Nextcloud, to be proxied by NPM
- Access the service's domain name locally with multiple clients using a local DNS server, e.g. Pihole
- Check Nextcloud logs and see all client IPs are identical
- Access the service's domain name from outside the network, using an internet DNS, observe that client IPs are shown correctly.
Expected behavior
Each client IP should correspond to the client's actual LAN IP.
Screenshots
N/A
Operating System
Docker on Ubuntu 20.04.
Additional context
Docker version '3'. Nextcloud version 22.2.0, official Docker image. LetsEncrypt SSL certs using a Duck DNS domain name. Pihole as a DNS server running on a different machine on my LAN.