To resolve the loss of internet access after setting a static IP on your Unraid server, you must verify that the Gateway and DNS settings in the Web UI match your router's configuration. The local network works because the subnet mask is correct, but routing fails when the default gateway address is missing or incorrect. This guide details the exact steps to restore full connectivity while maintaining your fixed address.
Understanding the Network Configuration
When you switch from DHCP to a static IP address, the system stops receiving automatic instructions for where to send traffic destined outside your local subnet. In most home and small office networks, this destination is handled by the router acting as the default gateway. If this value is not explicitly defined in the Unraid configuration, packets intended for the internet have no path to follow, resulting in the symptoms described: local shares are accessible, but web browsers cannot load external sites.
Additionally, Domain Name System (DNS) resolution often fails silently if not configured properly. Even if the gateway is correct, your server needs to know how to translate domain names like "google.com" into IP addresses. Without valid DNS servers specified, the connection appears dead despite having a valid route to the internet.
Verifying Router Settings
Before modifying Unraid, ensure your router has reserved the IP address you intend to use. Log into your router’s administration panel and locate the DHCP reservation or Static Lease section. Create an entry that binds your Unraid server’s MAC address to the desired static IP. This prevents IP conflicts where another device might accidentally claim the same address, which would cause intermittent connectivity issues.
Note the Subnet Mask, Default Gateway, and DNS Server addresses displayed in your router’s status page. These values are critical for the next step. For example, a typical home router uses 192.168.1.1 as the gateway and provides DNS services via its own IP or public resolvers like 8.8.8.8. Write these down accurately.
Configuring Static IP in Unraid
Access the Unraid Web UI by navigating to the server’s IP address in your browser. Go to the Main tab and click the Settings icon, usually represented by a gear symbol in the top right corner. Select the "Network Settings" option from the menu. You will see fields for IPv4 Address, Netmask, Gateway, and DNS.
Clear any existing values in the IPv4 field and enter the static IP you reserved earlier. Ensure the Netmask matches your router’s configuration, typically 255.255.255.0 for standard Class C networks. Enter the Default Gateway address exactly as noted from your router. Finally, input the Primary and Secondary DNS servers. Using both a local DNS (your router) and a public one (like Google or Cloudflare) provides redundancy.
After entering these details, click "Apply Changes." The interface may briefly disconnect as it reconfigures the network adapter. Wait for the page to reload or refresh your browser to reconnect using the new static IP.
Troubleshooting Connectivity Issues
If internet access remains unavailable after applying changes, perform a quick diagnostic check. Open the Terminal via the Tools menu and run
ping 8.8.8.8. A successful response indicates that the gateway and routing are functioning correctly. If this fails, the issue lies with the gateway configuration or physical connectivity.
Next, test DNS resolution by running
nslookup google.com. If this command hangs or returns an error, the DNS settings in the Network Configuration are incorrect. Return to the Settings menu and verify the DNS entries. Common mistakes include typing extra spaces or selecting the wrong interface if multiple NICs are present.
For advanced troubleshooting, you can inspect the routing table by running
ip route show. Look for a line starting with
default via followed by your gateway IP. If this line is missing, the system does not know how to reach external networks. In such cases, check if the network interface is enabled and assigned to the correct VLAN or bridge.
If you suspect a conflict with virtual machines or Docker containers, ensure they are also configured to use the same gateway. Misconfigured bridges can sometimes intercept traffic meant for the host. Refer to
IPTables: NAT Source Address Bridge Interface on Linux if you are using complex bridging setups that might interfere with host routing.
Another useful resource for diagnosing packet flow is
Finding Specific Data in Wireshark Capture, which can help visualize whether packets are leaving the interface correctly.
Frequently Asked Questions
Why does my local network work but the internet does not?
Local communication relies only on the IP address and subnet mask, which remain unchanged during the transition. Internet access requires a default gateway to route traffic outside the local subnet. If the gateway is missing or incorrect, the server cannot find a path to external networks, even though local devices are reachable.
Can I use public DNS servers like 8.8.8.8 instead of my router’s DNS?
Yes, you can use public DNS servers directly in the Unraid Network Settings. This bypasses your router’s DNS service entirely. However, some local features like hostname resolution within your LAN may fail if the public DNS does not know about internal devices. It is often best to use your router as the primary DNS and a public resolver as secondary.
What happens if I assign a static IP that is already in use?
An IP conflict occurs when two devices share the same address on the same network. This causes unpredictable behavior, including dropped connections and inability to access either device. Always reserve the IP in your router’s DHCP settings before assigning it statically to Unraid to prevent overlap with other clients.
How do I revert to DHCP if the static configuration breaks access?
If you lose access to the Web UI, connect a monitor and keyboard directly to the Unraid server. Boot into the OS and open the terminal. Run the command
ip addr to identify your network interface name. Then, use
dhclient to request a new lease from the router. Alternatively, edit the
/boot/config/network.cfg file manually to set the method back to DHCP.
Does changing the IP affect my Docker containers or VMs?
Containers and VMs typically communicate with the host via a bridge interface, so their direct access to the host’s IP is not strictly required for internal networking. However, if you reference the host IP in container configurations or port mappings, you must update those references to the new static IP. Failure to do so may result in broken links or failed health checks.