I’m about to install Nginx Proxy Manager for TrueNAS for the first time. My use case is for accessing my Docker containers using a domain name rather than the plain IP address. I think the anwer to my question is a simple yes, but want to double-check before so that I don’t lock myself out of TrueNAS:
Since NPM is on the same IP address as TrueNAS and will handle requests on port 80 and 443, I should move TrueNAS’s WebUI to new ports, right? Like 880 and 8443?
Right. I use 81 and 444 in my guide, but the ports you use are pretty much arbitrary.
Or put NPM on its own IP address leaving TN on 80 & 443
True, that’s another way to go about it.
I’ve tried to make TrueNAS’ WebUI available at truenas..net. But adding a proxy host like I do for all other services doesn’t work. All I get is this window:
There are some entries for https in TrueNAS’ General Settings. Are there any changes needed there?
Are there any benefits doing that?
Did you turn on websocket support for that proxy host?
Of course not… 
Thanks!
Other than the obvioius - not really
I’m being so new to reverse proxies and TN that I don’t feel confident that I even can tell what the obvious is.
That you keep TN’s UI on the default port and don’t risk forgetting where you put it?
I changed mine (truenas UI ports), no need to mess around with ports on caddy that way (my reverse proxy), custom IPs, etc.
Since I bookmark the link to Truenas in my browser, I don’t think one can forget the ports. But cvan be done either way. I take the easier route generally.
