pacmac

Changed my Unraid address from 10.0.13.2 to 10.0.13.5. No more problems in 4 hours. I don't understand why. The address was not used by any other machine in my network.

Every few minutes, the Unraid Web UI stops responding: when I try to refresh, I get an "ERR_CONNECTION_REFUSED" error in the browser. The GUI remains completely unreachable for several seconds, regardless of refresh attempts, and only becomes available again on its own. Despite this, my server responds to pings and I can still access the web interfaces of all Docker containers and network services without interruption. Is anyone else experiencing this? Docker apps and other network connections are always reachable even while the Unraid UI is inaccessible. In the diagnostics, you will see that I have had problems with my cache pool, forget about that, it was caused by a SSD power cable failure, but the problems started long time before that happened. sparta-diagnostics-20251012-1541.zip

This is my configuration: # Crete separate routing tables per interface echo "1 vlan13" >> /etc/iproute2/rt_tables echo "2 vlan1" >> /etc/iproute2/rt_tables # Add route to tables ip route add 10.0.13.0/24 dev br0.13 table vlan13 ip route add default via 10.0.13.1 table vlan13 ip route add 192.168.2.0/24 dev br0 table vlan1 ip route add default via 192.168.2.1 table vlan1 # Add rules based on the origin to use the correct table ip rule add from 10.0.13.2/32 table vlan13 ip rule add from 192.168.2.50/32 table vlan1 Modify it for your use case, test it in a shell and when it works for you, just save it in /boot/config/go and reboot.