overtross

Disabling Tailscale got my webGUI back, so maybe we should just close this until I figure out what's really what. Thanks for the help this far!

Is there some way to enable it from the console? "/etc/rc.d/rc.sshd start" just produces "SSH Daemon... Disabled". The only indicated usages of rc.sshd are start, stop, restart, reload, update, and status. None produced anything but variations on "not running" or "disabled".

willownas-diagnostics-20251009-0931.zip

Environment: Updated from Unraid 7.0.x → 7.1.4 Server boots normally; console shows all services starting. br0 has my expected static IP (192.168.1.18). System appears on my router’s device list, but I can’t reach it from Windows (no web UI, SSH, or ping). Console says SSH is disabled. What I’ve Checked: Physical connection and switch port are fine (device shows active in router). ifconfig output: eth0 has no IP, br0 has the correct IP and lists bond0 under it. Backed up /boot/config/network.cfg and replaced with a minimal version (no bonding, bridge → eth0). After reboot, still can’t reach web UI or SSH. From console: ps aux | grep sshd → no process brctl show → br0 attached to bond0 (before replacing network.cfg) Router shows correct MAC and IP lease Console login works fine locally. What I Tried: Manually started SSH with /etc/rc.d/rc.sshd start → still unreachable from LAN. Confirmed 192.168.1.18 is pingable only from router’s diagnostics, not from any LAN host. Reset network.cfg; no change. Symptoms Summary: Server boots cleanly. Network link light on NIC is active. Console shows correct IP but no external connectivity. Web UI and SSH both inaccessible from LAN. Looking for guidance on: How to fully reset or rebuild network stack in 7.1.4 (preferably without reinstalling). How to confirm whether br0 → bond0 mapping is stuck in memory despite config file changes. Any known 7.1.x issues with bonding/bridging after upgrade.