Home VPN server cannot be reached remotely: start by checking what actually fails, then compare a second device and a wired path if one is available. A single symptom does not prove a router defect.
Before you change anything
Do not treat an LED color or error message alone as a confirmed diagnosis. Use the model and indicator position.
First question
Was the test performed from a different network?
Record the answer before making a change. If you cannot test it, keep the cause open.
Separate the paths
- Check whether other devices see the same failure.
- Compare a wired client with Wi-Fi if possible.
- Record the router WAN address/status and the modem or ONT status.
- Note the exact model, indicator location, light pattern and recent changes.
Safe next action
Read the researched procedure below for model-specific prerequisites and rollback.
Verify and undo
Repeat the failing action after one controlled change. If the problem worsens, restore the previous wiring or setting. Do not interrupt a firmware update or use a factory reset as a first diagnostic step.
Official sources
- GL.iNet WireGuard server troubleshooting (full_text; checked 2026-11-01)
- ASUS WireGuard server setup (full_text; checked 2026-11-01)
Check your exact US model, hardware revision, and firmware on the linked support page before changing settings.