Nginx Proxy Manager - Docker networks

[fighttrooper]

Hi All,

Recently I installed NPM for the first time in docker, using Rusty`s tutorial.
After a lot of trial and error, I`ve managed to setup a proxy host to another docker container app (komga).
However, I`ve been trying to point the reverse proxy to the dsm login page, and it doesn`t seem to work.

How do you configure the docker network for NPM so I can access both docker containers and the dsm page (or photos, videostation.. native syn apps)? So far, I`ve managed to direct the proxy using the container name instead of the LAN IP. My current docker network setup is every container app on the default bridge network and the custom NPM-bridge network (that was installed with the container).

Also, just to make sure I haven`t accidentaly opened too much: the port forwarding on the router is only for 80/443 --> custom ports. And the only firewall changes is to let these custom ports through? No ports for the db (3306) or for the docker network (subnet/gateway) have to be opened?

After I have all the proxy hosts setup, my endgoal is to use Authelia for further security.

Thanks!

 

[Rusty]

If the npm is in bridge then you shouldn’t have problems getting your dsm page behind it. What error are you getting and how exactly are you configuring it?

 

[fighttrooper]

I`ve restarted both NPM and Mariadb now a few times and I`ve gotten it (mostly) to work.
If I point the domain to http - 10.0.0.x - custom dsm http port, it works (both http and force SSL)
If I point the domain to https - 10.0.0.x - custom dsm https port, I receive a 502 bad gateway (force SSL ON).

Thanks for the quick reply

 

[Rusty]

If I point the domain to https - 10.0.0.x - custom dsm https port

No need to internally also push it to HTTPS. You can use HTTPS (public) to HTTP (internal, that works for you). That's why you are using reverse proxy.