I had TN working with several apps including sabnzbd, sonarr, radarr and syncthing. I hadn’t set a static IP address when I first started this venture and the IP address was s192.168.1.129 as assigned by the DHCP on my router.
I went to the dashboard / Interface and edited it changing the DHCP as unchecked and setting an alias to 192.168.1.10. I tested the new address and it seems to work. Tried entering “Truenas.local” into my browser as well as the new addess, both bring up the logon and then the console.
The problem is that the web portal buttons for each of the apps do not work. They each show the new ip address with the appropriate port number, but say that the site can’t be reached.
I also tried deleting a couple of the apps and reinstalling. They got as far as “deploying” and hung there.
Also, after rebooting the NAS, only 2 apps (syncthing and readarr) started running. The others, 2 that I reinstalled and 2 that I left alone are stuck at “Deploying”. Also, the console is saying there are problems with 172.13.0.10:53 no destination available. This is not an IP address on my network.
How do I unscrew this mess I created?
I could do a complete reinstall, but I had to install core then upgrade to Scale to get the boot process to work at all. Any other suggestions would be appreciated.
FWIW, I had the same issue. My switch, router, and pihole (DNS and DHCP management) are in the closet in my office. The battery on the ups they’re plugged into went wonky and I had to reboot it. I recently rebuilt my pihole on newer hardware (pi5) and I forgot to reserve the mac for the TrueNas server. It got a new IP and caused all kinds of issues.
I managed to get the reservation set and the TrueNas box got the right IP. But Plex (especially on Android devices) went pear shaped and the server name in the Plex GUI kept changing. Also, trying to connect to the pod gave me the same ip error that you listed above, so I knew something was still amiss with the ip change. I use “host networking” for plex, saved me all kinds of headaches with Kubernetes routing.
After searching the forums, I came across a suggestion to update the ipv4 interface and gateway in the Apps>Advanced settings. Problem was, they were already set. So, I found the “Use GPU” check box, unchecked it, which forced a Kubernetes reconfig. The only GPU I have is onboard, which is reserved for TrueNas scale itself, so it has no bearing on the container. This allowed the Plex app to reconfigure with the correct ip, I can connect to the container, and everything in my Android Apps is back to normal.
The 172 addresses are for apps. and can be found Apps -->Configuration → Settings
It may have been all fine until the reboot which since the network was reconfigured, caused the issue to show up. Forcing an app to re-save its configuration seems to have worked for some.
In Trunas scale, port 53 is used by the Incus system for internal DNS resolution.
It’s also the standard port for DNS traffic, Services like Pihole can also use this port.
I believe yhere is a thread or a note somewhere that mentions if you are running Pihole or another DNS service on scale, you may need to configure it to use a different port if it conflicts with the Incus system’s default setting and I think the Incus port also can be changed if there is a conflict. See:
