Cannot access Truenas Scale web interface from LAN, but can via Tailscale

TrueNAS General
,
1

I just updated my Truenas Scale install to 24.10 from 23.10, and after updating I cannot reach the web interface from LAN by entering its IP in the browser.

I have tailscale configured on the system and I can access it through tailscale normally.

How do I fix this problem?

2

What is the output of ip addr?

3

This is the output of ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether a8:a1:59:43:7b:74 brd ff:ff:ff:ff:ff:ff
    inet 192.168.88.166/24 brd 192.168.88.255 scope global dynamic enp9s0
       valid_lft 43511sec preferred_lft 43511sec
    inet6 fe80::aaa1:59ff:fe43:7b74/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:75:bf:eb:ba brd ff:ff:ff:ff:ff:ff
    inet 172.16.0.1/24 brd 172.16.0.255 scope global docker0
       valid_lft forever preferred_lft forever
4: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 100.85.9.119/32 scope global tailscale0
       valid_lft forever preferred_lft forever
    inet6 fd7a:115c:a1e0::a701:978/128 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::fd7e:b1c9:4edf:7e80/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
4

Without me doing much of anything it started working by itself, I still don’t know what was the problem but whatever

5

Good to know. Looking at the output there, it doesn’t look like there are any conflicts with the subnets, but if you have connectivity issues again, you may want to check if the subnets are overlapping and therefore, conflicting with each other.