I have a Synology NAS, and it runs a bunch of services in docker containers. One of them is called Tautulli, which is an app that monitors Plex statistics. Among other things, this is something I want to proxy.
What I did – I set up an old PC running Linux, I installed docker, then I installed nginxproxymanager, so it's running on it's own standalone host, not as a container on any NAS. I mapped the ports as "8888:80" and "8443:443", as I already have something on 80/443. I made port-forwarding rules to forward those 2 ports to my npm IP, for when I get around to accessing things from the outside. That's the last step, tho, I can't even make the first step work yet … LOL
npm comes up fine, on my workstation I put in the IP and port 81, and sign in as expected (http://10.0.0.10:81). A good start!
In my Cloudflare I have an A record (services.mike-leone.com) that points to the local IP of the host running npm (10.0.0.10) – that's mostly for when I get around to using certs, or actually accessing npm from the outside world. I'm nowhere near there yet.
Then I made an A record in my local DNS – tautulli.services.mike-leone.com – that ALSO points to my npm IP (10.0.0.10). This is the name of my proxied source host entry in npm.
Correct so far? The entry for the proxied source host has to be a name that resolves locally to the npm server?
Then, as a target for that proxied host, I put in the IP of my NAS and the port Tautulli uses (8181). I didn't even get to the SSL part yet, I need to see npm work first (since I haven't been successful at that yet).
I click on the proxied host name, and I get …
Hmmm… can't reach this page
tautulli.services.mike-leone.com refused to connect.
I know that's the right IP, it's the npm server:
C:\Users\turgo>nslookup tautulli.services.mike-leone.com
Server: pi.hole
Address: 10.0.0.5
Name: tautulli.services.mike-leone.com
Address: 10.0.0.10
If I just type the target in a browser (http://10.0.0.82:8181), I get the Tautulli home page just fine.
So where did I go wrong? I'm not understand some basic step. Or my npm isn't forwarding to the host or ports I want it to forward to. Or something. I'm just scratching my head, at this point, as to why I can't even get it to proxy correct, never mind use a cert. Or access from the outside.
Clues or lightbulbs, anyone?
Thanks
Source: r/nginxproxymanager · by /u/SomeConfusedOldGuy