per-App IP addressing - how does it work?

Apps and Virtualization
21

Here is what I’m trying to do:

Use Case: Right now, I have some of my TrueNAS Apps (notably Kavita, Audiobookshelf, and Authentik) exposed to the outside world, and use the Nginx Reverse Proxy to provide https access to those applications while I am outside of my network. I want to move my Nginx Reverse proxy from 192.168.1.2 to 192.168.1.8 and change the http port from 30021 to 80 and https port from 30022. This should allow me to utilize DNS Rewrite on my AdGuard Home instance (still on 192.168.1.2) so that I can point appname.mynetwork.net to 192.168.1.8. This should allow me to access those applications in case of a network outage.

I am utilizing the following:

  • TrueNAS version 25.04.1
  • Nginx Proxy Manager App Version: v2.12.3 / Version: v1.2.0

This was working as expected prior to my changes.

Steps I have performed so far:

  1. Went into Network → Interfaces and added 192.168.1.8/24 to the pre-existing lP address of * 192.168.1.2/24
  2. Tested and Saved the network changes.
  3. Went into System → General Settings → GUI → Settings and changed the GUI IP from 0.0.0.0 to 192.168.1.2 . While 192.168.1.8 was available, it was not set.
  4. Went into Apps and the Network configuration for Nginx and assigned the 192.168.1.8 IP address for the following ports:
  • WebUI: 30020
  • http: 30021
  • https: 30022
  1. After saving the IP address changes, I tested one of my apps and got failure (expected).
  2. I went into my router for port forwarding and changed the IP address from 192.168.1.2 to 192.168.1.8 for 80 → 30021 and 443 → 30022. After saving, the apps are working as expected.
  3. I went into the Apps and the Network configuration for Nginx, and attempted to change the http port to port 80 and https to port 443. When attempting to save, I get the error message “Error: Network, Port is already in use.”

Observations:

  • I can access the WebUI by http://192.168.1.8:30020/ and http://192.168.1.2:30020/ . But, why 192.168.1.2
  • Testing by http://192.168.1.8 and https://192.168.1.8 gives me the error message that the site cannot be reached.
  • I temporarily changed the http port of TrueNAS from 80 to 81 and the https port of TrueNAS from 443 to 8443. This allowed me to set the port in the Nginx container.
  • I then modified the port forwarding on my router to port 80 and 443 in 192.168.1.8 respectively. My apps are working.
  • I then applied the change of *.mynetwork.net to point to 192.168.1.8 as a DNS rewrite and it operated as expected.

So, apparently, the ports of 80 and 443 of the TrueNAS GUI on 192.168.1.2 affect the usage on 192.168.1.8. Why? I don’t know.

Addendum: I just moved the TrueNAS GUI IP addresses back to 80/443, and TrueNAS is working as expected, and my apps are still working as expected. Go figure. I’m wondering if I’m going to hit something when Nginx gets updated in the future.

1 Like