If you prefer to assign a known working static IP instead of using DHCP, configure it like this:
Last updated: October 2025. Compatible with Unraid 6.12.x and 7.0.0+
| Problem | Solution | Files Involved | | :--- | :--- | :--- | | WebGUI unreachable after IP change | Delete network.cfg from USB on another PC | /boot/config/network.cfg | | NIC hardware changed (MAC mismatch) | Delete network-rules.cfg | /boot/config/network-rules.cfg | | Complete lockout, no local console | Remove USB, delete both CFG files on another computer | Both files above | | Fresh install but keep disk config | Delete only network CFGs from existing /config folder | Both files above | | Need temporary network to rescue data | Boot Safe Mode, remove files, restart emhttp | N/A | unraid reset network settings install
If the server is completely unresponsive, press the physical power button once for a clean shutdown. Avoid pulling the power plug unless absolutely necessary. Step 2: Access the Flash Drive on a PC
file, which dictates how the server identifies itself to your router. By removing this file, you essentially "reinstall" the default network configuration, forcing Unraid to request a fresh DHCP address upon its next boot. The Step-by-Step Recovery Process If you prefer to assign a known working
Ensure Ethernet cables are securely connected.
There are several reasons why you might need to reset your network settings in Unraid: Step 2: Access the Flash Drive on a
If your Docker containers or VMs fail to start after a network reset, verify that Enable Bridging is set to Yes in your network settings, as many containers rely on the br0 interface to function. To help tailor this to your exact issue, let me know:
Reset Network to default - General Support - Forums - Unraid