Just did the upgrade to the latest Fangtooth Point Release and can’t
access my web admin panel at all. It simply isn’t resolving. I can access
the console ok and have verified it can ping out/has the right IP address
set still.
Just curious if anyone else has had this problem? Or if there is some command
set to test/force a reset of the middleware on the Truenas CLI?
I’ve done two full reboots with the same problem…
Not something I have heard of or ran into. When you say console I assume you are seeing the options 1-12 or whatever? Have you tried to reset the interface?
Hi ChicagoMed,
I’ve run into similar issues after upgrades in the past. Since you can access the console, you might want to try resetting the web interface from there. You can do this by selecting the option to reset network settings or restart the web service, depending on what’s available in your menu.
If that doesn’t work, you could also check the system logs from the console to see if there are any error messages related to the web interface. Sometimes, a quick look there can provide clues on what might be going wrong.
I tried to fix the ‘root cause’ and replace certificates etc but eventually just had to do a UI reset. I had to add the Default Route back to Nic1 where the UI is bound and was able to access the UI.
But now I have a new problem. My second NIC is unreachable via SMB or ping even thought I have bound it to the SMB interface.
I tried adding a Static Route but it doesn’t seem to help.
I don’t ever remember having this problem during my initial setup and so wondering if anyone might know what to do.
Thanks!
Cross posting this status update from the TrueNAS forums too..
Ok I am starting to understand what is going on but not still not sure a) what to do about it and b) why this all just happened after Fangtooth.
I connect to Truenas from different VLANs on my network. I have an Admin VLAN which certain clients live on that access the WebUI, and a User VLAN that the rest of the clients live on that access the SMB. My Admin VLAN has permissions at the router/firewall level to access both.
What appears to be happening here is an assymetric response where I access one interface say 10.1 from 10.3 and because the reply is not going back to a 10.1 interface somewhere the packet is dropped.
If I manually add a static route it works but essentially then I would have to have a gateway for each VLAN I am routing through which seems excessive, and again, this was never a problem before.
ChatGPT suggested changing:
net.ipv4.conf.enp3s0f1.rp_filter = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.default.rp_filter= 0
net.ipv4.icmp_echo_ignore_all = 0
But adding these to sysctl in the GUI didn’t seem to do anything. And in the /etc file everything was commented out so I am assuming there is a default override somewhere?
Can anyone explain to me what’s going on and why it changed in Fangtooth?