Hey there NASrs. I recently brought my Truenas back to life after a couple months off, and it’s booting fine (after a series of memory errors) but now the web interface is defaulting to 0.0.0.0
Am I right in assuming that it is trying to pull an IP and not getting one served from my switch?
This is the most likely cause - a DHCP timeout, which you can either address the root cause of, but I’d set a static IP myself.
I’m more concerned with
“a series of memory errors” isn’t something I’d take lightly. Are we talking about “Memory size changed, press F1 to continue” or something a little more severe?
Post a picture of your network configuration page (from TrueNAS) so we know what we’re dealing with.
Also let us know what the internal IP of your router is. A common IP of a router in a home network is 192.168.1.1, but there are many different variants and approaches.
If you are referring to the listen address configuration - that is perfectly well and the default. It means “listen to any local address the system might have”.
So I should probably explain the setup more clearly here. I have a QNAP Switch that everything is going into, but there’s no link to the router. I’m in a shared office coworking space, so don’t have access to the actual internet router.
the Switch shows an ip of 169.254.100.101, and its a QNAP QSW M408 2C.
I’ve set ix0 and ix1 to static IP addresses on the Truenas as you can see in the photo, both under the same domain as the switch.
And now I can even see the truenas in the network when i arp -a!
truenas.local (169.254.245.200) at xxxxxxx on en0 [ethernet]
but trying to connect via SMB or using the WebGUI is still not working. I feel like I am soooo close, but don’t know the next step to take.