Proton VPN WireGuard router illustration with security shield and protected connectivity

Proton VPN Connected but No Internet? 9 WireGuard Router Fixes

Proton VPN connected but no internet is a particularly misleading router problem: the WireGuard client appears active, yet a laptop behind the router cannot load a page. The status icon only tells part of the story. A tunnel can establish while DNS, routing, firewall policy, or the selected server path still prevents normal traffic.

I use a Cudy WR3000 as Proton VPN edge for my lab, and I have encountered this connected-without-internet symptom while experimenting with Proton WireGuard and Secure Core routes. The checks below separate a connection problem from a forwarding problem, so you can find the failing layer rather than resetting everything at random. This is a reproducible diagnostic procedure, not a claim that every suggested fix resolved an issue in a verified benchmark.

Affiliate disclosure: This guide includes sponsored Proton VPN links. HackersGhost may earn a commission at no additional cost to you. The diagnosis is useful even if you use another compatible WireGuard provider.

Key Takeaways

  • Start with one isolated client device and record what works with the Proton VPN tunnel connected; never assume “connected” means traffic uses Proton VPN.
  • Check recent handshakes and actual received/transmitted traffic separately. A fresh handshake is not proof that web requests succeed.
  • Compare connectivity by IP address versus domain name to isolate DNS failures from routing failures.
  • Cudy per-device VPN rules and a fail-closed kill switch can intentionally block traffic even while the interface looks healthy.
  • A new Proton WireGuard profile and a standard nearby server are useful controls when a Secure Core route fails.
  • After every change, confirm public IP, DNS resolver behavior, routed-device selection and loss-of-tunnel protection before calling the problem fixed.

Before the Fixes: Preserve a Known-Good Network Route

If WireGuard is not working on the router, do not begin by deleting the only available profile or disabling every firewall rule. Keep an administration path to the router outside the test connection, record the firmware and hardware revision, and export configuration where the router permits it. Make changes on one test client first, not across every household device.

This guide assumes a consumer router acting as a WireGuard client to Proton, not a WireGuard server accepting incoming connections. My Cudy WR3000 WireGuard router setup explains installation, while the diagnostic steps here begin after a profile has already been imported.

Privacy note: A temporary test without Proton VPN may expose your ordinary public IP and DNS to the ISP. Use only a non-sensitive test device and traffic, and avoid bypassing a required organizational VPN policy. If you need strict fail-closed behavior, stop after the offline router checks rather than disabling the kill switch.

Fix 1: Check Proton VPN Router Internet Access Without the Tunnel

When WireGuard is not working, first determine whether the upstream WAN connection is healthy. Check whether the router has a WAN address, gateway and working DNS; inspect its status page for link failures or recent reconnects. A failed ISP connection can look exactly like a VPN failure from the client’s perspective.

On your designated lab client, you can record the current gateway, addresses and routes with:

ip -brief address
ip route
ip -6 route

These Linux commands are read-only. If you use Windows on the test client, ipconfig /all and route print provide related information. Do not paste a real public IP or network credentials into support forums.

If the WAN is down, fix the underlying connection first. If WAN works but Proton VPN policy blocks clients, continue to the next checks. Remember that a router kill switch may make “WAN works” and “this protected client can browse” deliberately different outcomes.

Cudy WR3000 WireGuard Router Setup with Proton VPN

Start with the verified Cudy configuration before troubleshooting the tunnel.

Fix 2: Look at the Latest Handshake and Transfer Counters

A WireGuard client is not a browser test. When WireGuard is not working, inspect the router’s VPN status for a recent handshake, its endpoint, and both receive and transmit counters. Some routers display “connected” even when usable traffic is absent; other interfaces report the last remembered state.

  • No recent handshake: suspect an unreachable endpoint, expired or incorrect profile, device clock issue, upstream filtering, or a server-side outage.
  • Fresh handshake, almost no received data: investigate forwarding, server path, allowed IPs and policy routing.
  • Both counters rise, websites fail: move DNS, client route and MTU higher on the list.

On a Linux system that actually hosts the WireGuard interface, sudo wg show reveals the peer’s latest handshake and transfer counters. It will not show the router’s internal interface merely because your laptop is connected by Wi-Fi. Use the Cudy administration panel for router-level status.

Do not publish the private key from the configuration file. The official Proton WireGuard configuration guide explains why a dedicated generated client profile is required for third-party WireGuard implementations.

Secured laptop and network shield illustrating WireGuard handshake and connectivity checks

Fix 3: Test IP Connectivity Separately From DNS

One fast way to locate the failure is to compare a numeric IP connection with a domain lookup. When WireGuard is not working, start from a client that the router is explicitly supposed to route through Proton:

ping -c 2 1.1.1.1
getent ahostsv4 example.com
curl -4 -I --connect-timeout 8 https://example.com

Interpret the results carefully. If IP connectivity succeeds while name resolution fails, investigate DNS settings. If both fail, look at forwarding, policy routing and kill-switch state. If DNS and the HTTPS request work but a particular website does not, it could be that website, its IPv6 behavior or a filtered route rather than a global VPN failure.

ICMP can be blocked even when the internet works, so a failed ping alone is not conclusive. Likewise, an HTTPS request can fail due to certificate or website rules unrelated to WireGuard. Use multiple signals and repeat against at least one service you trust.

A router’s DNS setting may differ from the DNS applied to individual clients or browsers. Browser DNS-over-HTTPS, hardcoded DNS, and IPv6 resolvers can complicate the picture. My Proton VPN custom DNS investigation explores those privacy tradeoffs in more detail.

Proton VPN Custom DNS: 7 Real AdGuard Setup Lessons

Separate VPN connection failures from DNS and filtering problems.

Fix 4: Check Cudy VPN Policy and the Kill Switch

When WireGuard is not working only on certain devices, the router’s client policy is a prime suspect. Cudy can route all devices or only selected devices through Proton VPN; its kill-switch behavior can then block normal internet access when the protected path is unavailable.

In Cudy’s official VPN configuration guide, Proton VPN client policy includes a kill-switch mode and per-device routing choices. Exact control names vary by firmware and hardware revision, so confirm what is installed before copying screenshots from another model.

  • Confirm that your test device appears in the connected-device list.
  • Record whether the default is “Allow all devices” or “Ban all devices.”
  • Check whether that device has a specific VPN-routing override.
  • Inspect VPN Policy and required preferred DNS settings.
  • Confirm whether the kill switch is correctly blocking traffic after a tunnel failure, rather than mistakenly treating that as a broken ISP connection.

To diagnose WireGuard not working with selective routing, compare one explicitly VPN-routed client with another explicitly allowed to use WAN. Do not disable privacy controls for the whole network as a shortcut. Once your lab tests are complete, restore the intended fail-closed policy and verify it intentionally blocks bypass traffic.

Firewall shield protecting network traffic when the Proton VPN kill switch activates

Fix 5: Check Allowed IPs, Routing and Conflicting Subnets

Most Proton router profiles are intended to route internet traffic toward the selected VPN peer. But the downloaded AllowedIPs setting, local policy routes and overlapping LAN addresses decide what your router actually forwards. With WireGuard not working, check the imported profile against the original configuration without exposing its private key.

A full-tunnel IPv4 route commonly uses 0.0.0.0/0; IPv6 may also be included depending on the profile. Do not blindly add routes to an existing router: a conflicting default route or LAN overlap can sever management access or send traffic to the wrong interface. First inspect the router’s active routes and Proton VPN policy for the affected device.

Lab environments are especially prone to overlapping networks. VMware NAT networks, another downstream router and your ISP router may all use private IPv4 ranges. If two interfaces claim the same subnet, a client may have a valid handshake but no sensible return path. Change addressing only after documenting current subnets and creating a way back into router administration.

If a single device works but another fails, compare their IP assignment, default gateway and per-device VPN policy before regenerating keys. That is often a safer and faster diagnosis than treating every symptom as a Proton outage.

Fix 6: Generate a Fresh Proton VPN Profile and Try a Standard Server

If WireGuard is not working despite correct local rules, create a fresh configuration for the router in the Proton dashboard. Download the file for the correct client type, keep the old configuration safely archived, and test a standard server close to your location. Do not publish any part of the private key or upload the raw configuration to a public issue tracker.

Why compare profiles? One server or route may be under maintenance or temporarily unreachable even though another works. A normal server provides a simpler baseline than a multi-hop Secure Core route. If standard works and Secure Core fails, keep the diagnostic focus on the selected path, endpoint, reachability and profile rather than rewriting the entire LAN.

In my own Cudy setup I have seen a Proton Secure Core route report a connection while internet access failed, whereas another route behaved differently. That experience is the reason for this diagnostic sequence; it is not proof that Secure Core is generally unreliable. Record your server choice, profile creation time and observed result so you can tell a repeatable issue from a one-off network fault.

If your Proton plan or profile options change, regenerate instead of editing cryptographic fields by guesswork. For the supported router features and account options, you can review Proton VPN through HackersGhost.

Fix 7: Diagnose Proton VPN MTU and Fragmentation

MTU issues tend to show up as partly working connections: small requests succeed while large pages, uploads, or selected applications stall. If WireGuard is not working in that specific pattern, inspect the imported MTU and any manual router overrides. Do not assume that lowering MTU fixes every “no internet” symptom.

On a Linux test client, tracepath example.com may provide hints about path MTU, though it does not prove the Proton VPN tunnel’s effective MTU. A ping with the do-not-fragment flag, such as ping -M do -s 1320 1.1.1.1, is another diagnostic for IPv4 on supporting systems; intermediate firewalls may block it. A common WireGuard starting point is around 1420 bytes, but the correct value depends on encapsulation, carrier links and router implementation.

Adjust only one setting at a time, record the old value, and retest the exact failed request. If DNS itself cannot resolve a domain, an MTU change is probably not your first useful move.

Security magnifier and key illustrating investigation of Proton VPN DNS problems

Fix 8: Verify Proton VPN IPv4, IPv6 and DNS Routing

A fixed browser tab is not enough. With WireGuard not working intermittently, verify whether IPv4 and IPv6 take consistent paths and whether DNS is going through the intended resolver. An IPv4-only test can overlook a separate IPv6 path, and browser-managed DNS can differ from the router’s resolver.

  • Use a reputable IP and DNS leak test while the intended VPN-routed client is connected.
  • Record the public IPv4, any available IPv6, and apparent resolver network.
  • Compare with the desired Proton exit location; do not assume the DNS server must share the exact public IP as Proton VPN server.
  • Repeat after reconnecting, rebooting the router and deliberately interrupting the test tunnel.
  • If the router cannot tunnel IPv6, explicitly manage IPv6 routing rather than allowing an unnoticed WAN fallback.

Check the outcome on the specific test device. A second client allowed to bypass Proton should normally show a different public address. The expected result depends on the policy you chose. If the bypass device and protected device show the same ordinary ISP address, that warrants investigation even if the router status says “connected.”

Fix 9: Prove Proton VPN Recovers and Fails Closed

When WireGuard is not working after restarts, a temporary fix is not enough. Use an isolated test client, restore the selected server, then deliberately disconnect and reconnect Proton VPN through the router’s management interface. A correct kill-switch policy should block the protected device when the Proton VPN tunnel is unavailable. When the Proton VPN tunnel returns, the client should regain connectivity through the intended VPN exit.

Document four observations: the router’s reported status, latest handshake and transferred data, the protected client’s public IP and DNS behavior, and whether the kill switch prevents fallback. Repeat after a router restart and, if permitted, after the upstream link briefly drops. Do not test failover using production systems that cannot tolerate an outage.

If WireGuard is not working only after reboot, revisit startup order, time synchronization, DNS dependencies, profile availability and policy restoration. My Cudy WireGuard performance article looks at stability tradeoffs; this guide focuses on failure isolation and recovery steps.

How to Read the Symptoms Without Guessing

  • No handshake, no browsing: check WAN, endpoint resolution, router time, profile age and possible provider outage.
  • Handshake but no traffic: check client policy, allowed IPs, routing and firewall treatment of the Proton VPN tunnel.
  • Numeric IP works, domains fail: investigate DNS and conflicting secure-DNS settings.
  • Some sites work, large pages hang: investigate MTU, IPv6 and application-specific filtering.
  • Normal server works, Secure Core fails: isolate the selected Secure Core path and regenerate its profile rather than assuming the entire router is broken.
  • Internet works, real ISP address still appears: investigate bypass routes and kill-switch policy; this is a privacy failure, not a successful VPN fix.

When Is the Router Actually Fixed?

My acceptance criteria are stricter than a status icon. The assigned device must browse through the intended VPN exit, DNS must follow the chosen privacy policy, the correct clients must use or bypass the Proton VPN tunnel, and an intentional disconnect must not expose protected traffic. Only then do I stop calling it a WireGuard not working incident.

For commercial plans, Proton VPN offers options that may suit a permanent router setup, but a subscription upgrade cannot fix incorrect routing or DNS. Diagnose first, then decide whether the desired server and feature choices justify paying.

Final Verdict

With Proton VPN connected but no internet, the correct fix starts by asking which layer failed? Status, handshake, payload, DNS, routing and privacy behavior are separate checks. Work through them in order, change one variable at a time, and record the results. A VPN that reconnects but quietly bypasses the Proton VPN tunnel is not fixed.

Large cybersecurity question mark and padlock for Proton VPN router questions

Proton VPN Router FAQ

Why does WireGuard show connected with no internet?

Should I turn off the Cudy kill switch?

Can Secure Core cause a different result from a standard server?

Does changing DNS solve every failed Proton router connection?

Can I reuse the same WireGuard profile on several devices?

VPN & Network Infrastructure Cluster

ⓘ

Some links in this article are affiliate links. If you use them, I may earn a small commission — at no extra cost to you. I only recommend tools I’ve actually tested inside my own cybersecurity lab. Read the full disclaimer.

In many cases, these links unlock better deals than you’ll find on your own.
No paid reviews. No sponsored opinions. Just real testing and real setups.

If you decide to use them, you’re not just getting a discount — you’re helping keep this lab running.

Leave a Reply

Your email address will not be published. Required fields are marked *