WireGuard is designed to be incredibly silent. If it fails to connect, it won't pop up an error message; it simply drops the traffic. Here is how to diagnose and fix the most common connection issues.
Overview
Because WireGuard uses UDP instead of TCP, the app on your phone doesn't technically know if the server actually received the connection. It just throws the encrypted data into the void and hopes the server responds. If the server doesn't respond, your internet simply stops working.
Issue 1: The VPN toggles on, but nothing loads
You toggle the switch, the VPN icon appears at the top of your phone, but Safari says "You are not connected to the internet."
Diagnosis: This means the "Handshake" failed. Your phone sent the encrypted request to your home router, but the router blocked it or sent it to the wrong place.
How to fix it:
- Open the WireGuard app, tap your connection, and look at the Transfer stats at the bottom. You will likely see "Sent: 4 KB, Received: 0 KB". The 0 KB means the server never responded.
- Log into your home Wi-Fi router's admin panel.
- Check your Port Forwarding rules. Ensure you are forwarding port 51820 on protocol UDP to the exact internal IP address of your LocalNode.
- Ensure your LocalNode IP address hasn't changed (e.g., if it used to be .50 and is now .51, the port forwarding rule is sending the VPN traffic to a dead end).
Issue 2: It worked yesterday, but not today
You set up the VPN perfectly, tested it at a coffee shop, but three weeks later while on vacation, it suddenly stops working.
Diagnosis: Your home internet provider changed your Public IP address.
Most residential internet plans use "Dynamic IPs". Your ISP might change your house's public address randomly. Since your WireGuard app is programmed to look for the old address, it can no longer find your house.
How to fix it:
- You must set up Dynamic DNS (DuckDNS). This gives your house a permanent domain name (like
myhouse.duckdns.org). - In the WireGuard app on your phone, edit the connection.
- Change the Endpoint from the hardcoded IP address (e.g.,
72.14.x.x:51820) to your new DuckDNS domain (myhouse.duckdns.org:51820).
💡 Tip: You can also fix this permanently by asking your ISP for a "Static IP", though they usually charge an extra $10/month for this feature.
Issue 3: Cannot access localnode.local
The VPN connects successfully, you can browse Google, and you can access your dashboard via 192.168.1.50, but typing localnode.local fails.
Diagnosis: mDNS (Multicast DNS) does not travel across VPN tunnels by design. The .local address only broadcasts to devices physically on the same network switch.
How to fix it:
- The simplest fix is to just use the IP address (e.g., bookmark
192.168.1.50 instead of the .local address). - Alternatively, you can set the DNS Server inside the WireGuard app settings to point to your LocalNode IP, and ensure AdGuard Home is running, as AdGuard automatically resolves local hostname queries.
Next Steps
Need help? Email hello@localnode.tech or visit localnode.tech/contact.