[3 / 1 / 1]
218KiB, 750x840, Screenshot_2025-12-15-11-22-14-612_com.discord-edit.jpg
Quoted By:
I'm trying to host PhotoPrism on a Docker container running inside a Ubuntu VM, but I'm struggling to get it accessible from the outside.
My Setup:
ISP Router (Public IP) -> Secondary Router (Internal Network) -> VM Host -> Linux VM (Docker).
Services: PhotoPrism and Nginx Proxy Manager (NPM) running in Docker.
DNS: A-record is pointing to my current Public IP.
Firewall: Port 80 and 443 are opened on the VM (UFW) and I've attempted port forwarding on both routers.
The Problem:
Despite having the ports opened, I cannot reach port 80
On the first router, I forwarded 80/443 to the WAN IP of the second router.
On the second router, I forwarded 80/443 to the local IP of the VM.
Inside the VM, Docker is mapping 80 and 443 for NPM.
Is there a specific way to debug which "layer" of the NAT/Firewall is dropping the packets?
My Setup:
ISP Router (Public IP) -> Secondary Router (Internal Network) -> VM Host -> Linux VM (Docker).
Services: PhotoPrism and Nginx Proxy Manager (NPM) running in Docker.
DNS: A-record is pointing to my current Public IP.
Firewall: Port 80 and 443 are opened on the VM (UFW) and I've attempted port forwarding on both routers.
The Problem:
Despite having the ports opened, I cannot reach port 80
On the first router, I forwarded 80/443 to the WAN IP of the second router.
On the second router, I forwarded 80/443 to the local IP of the VM.
Inside the VM, Docker is mapping 80 and 443 for NPM.
Is there a specific way to debug which "layer" of the NAT/Firewall is dropping the packets?
