You moved your server to a new network with a different IP scheme (e.g., moving from 192.168.1.x to 10.0.0.x).
(Optional) If you use custom routing or bonding, you may also see network-rules.cfg .
I can give you tailored steps to safely build out your network structure from scratch. Share public link
Run the following commands to delete the network configuration files: rm network.cfg rm -f network-rules.cfg Use code with caution. unraid reset network settings
He logged in and restored some settings: the static IP he preferred, the bond he’d configured for link aggregation, the custom DNS. Small adjustments—like smoothing out a creased shirt—made the server feel like itself again. He checked the syslog and found the corruption likely dated to the power surge; one line showed a write error to the flash drive the night the storm hit. He made a note: replace the USB flash drive and add a UPS.
For advanced users who are currently SSH’d into a server with a bad network config (e.g., you changed the WebUI port but can still SSH via the local LAN):
Since you cannot access the WebGUI, you must shut down the server using the physical power button. You moved your server to a new network
Change your IP back to DHCP or fix the gateway/DNS settings. Apply and Reboot: Switch back to the standard boot mode. Troubleshooting Post-Reset Tips
: Open the USB drive and navigate to the /config folder.
Navigate back to Settings > Network Settings to re-apply any necessary settings. Best Practices to Prevent Future Lockouts Share public link Run the following commands to
. This is often necessary if you lose access to the WebGUI after a configuration error. Method 1: Physical Flash Drive Access (Easiest)
On the Unraid boot menu, select "Unraid OS (Safe Mode)".
Avoid pulling the power plug unless the server is completely frozen, as this can cause parity errors or data corruption. Step 2: Remove and Mount the USB Flash Drive Unplug the USB flash drive from your Unraid server.