Fixing “Site Can’t Be Reached” Errors

There is nothing worse than typing localnode.local into your browser and staring at a blank, spinning tab that eventually says "This site can't be reached". Here is the step-by-step checklist to get your server back online.

Overview

The "Site Cannot Be Reached" (ERR_NAME_NOT_RESOLVED or ERR_CONNECTION_REFUSED) error means your computer literally cannot find a path through the network to the server. It does not mean the apps crashed; it means the networking broke.

Step 1: Check your VPN status

Are you at a coffee shop or using cellular data? localnode.local only works if you are physically connected to your home Wi-Fi.

• If you are away from home, you MUST turn on your WireGuard VPN first.
• If you are at home but have a commercial VPN turned on (like NordVPN or ExpressVPN), it is likely blocking local network traffic. Turn it off and try again.

Step 2: Try the IP address instead of .local

The .local address relies on a protocol called mDNS. Some older routers or complex network setups (like mesh Wi-Fi with separate guest networks) accidentally block mDNS broadcasts.

1. Log into your home router's admin panel (usually 192.168.1.1).
2. Look at the list of "Attached Devices" or "DHCP Clients".
3. Find the device named localnode and note its IP address (e.g., 192.168.1.50).
4. Type http://192.168.1.50 directly into your browser.

If the IP address works but the .local address does not, bookmark the IP address. You can also try rebooting your Wi-Fi router, as this often fixes stuck mDNS broadcasts.

Step 3: Check power and ethernet

This sounds silly, but it is the cause of 50% of support tickets.

1. Go look at the physical LocalNode device.
2. Is the blue power LED illuminated? If not, the server is off. Press the power button.
3. Is the ethernet cable plugged in? The lights on the ethernet port should be blinking yellow/green. If they are completely dark, the cable is dead or the router port is broken. Try a different ethernet cable and a different port on the router.

Step 4: The hard restart

If the power light is on, the ethernet lights are blinking, you aren't on a VPN, but you still cannot load the dashboard via the IP address, the operating system may have locked up.

1. Press and hold the physical power button on the LocalNode for 10 seconds until the blue light turns off.
2. Wait 5 seconds.
3. Press the power button once to turn it back on.
4. Wait 3 minutes for the system to boot up.
5. Try loading the dashboard again.

Need help? Email hello@localnode.tech or visit localnode.tech/contact.