Table of contents
- Quick checks that fix the problem most often
- Most common reasons ProtonVPN fails to connect
- Fix network issues first
- Test a different connection
- Watch for captive portals
- Try another DNS or router path
- Change the protocol when the default one fails
- Check app settings and account status
- Sign out and sign back in
- Make sure the app is up to date
- Check free plan limits and server load
- Firewall, antivirus, and system conflicts
- A practical step-by-step order to follow
- When reinstalling makes sense
- Conclusion
- FAQ
- Why does ProtonVPN connect on mobile data but not on Wi-Fi?
- What protocol should I use if ProtonVPN will not connect?
- Can antivirus software stop ProtonVPN from connecting?
- Is the free plan more likely to have connection problems?
- What should I do if ProtonVPN still will not connect after reinstalling?
If ProtonVPN is not connecting, the problem is usually one of five things: your network is blocking the VPN handshake, the app is using the wrong protocol, a firewall or antivirus tool is interfering, the app itself needs an update, or your account or selected server is the issue. In most cases, you can fix it by switching networks, changing protocols, or checking security settings.
Before you go deep into settings, start with the basics. A lot of connection problems disappear after a quick restart, a different Wi-Fi network, or a protocol change.
Quick checks that fix the problem most often
- Make sure your regular internet connection works without the VPN.
- Disconnect any other VPN, proxy, or private DNS tool.
- Restart ProtonVPN, then restart your device if needed.
- Try a different server, especially if the first one is crowded.
- Update the app if you have not done that in a while. If needed, get the latest build from the official Proton VPN download page.
Most common reasons ProtonVPN fails to connect
| Symptom | Likely cause | Best fix |
|---|---|---|
| Stuck on connecting | Protocol mismatch or blocked network | Switch protocol and try another network |
| Connects on mobile data but not Wi-Fi | Router, firewall, or captive portal issue | Log into the Wi-Fi portal, then reconnect |
| Works on one server but not another | Server load or temporary maintenance | Pick a different server or wait and retry |
| Fails only on the free plan | Limited servers are full | Try another free server or connect later |
| App never gets past handshake | Firewall or antivirus conflict | Allow ProtonVPN through security software |
Fix network issues first
Test a different connection
If the VPN works on mobile data but not on home Wi-Fi, the network is probably the problem, not the app. Public Wi-Fi, office networks, and some home routers block VPN traffic or interfere with DNS. A fast way to check is to switch to a phone hotspot and try again.
Watch for captive portals
Some Wi-Fi networks require you to sign in through a browser before they allow normal traffic. If you connect to the network but ProtonVPN keeps failing, open a browser first and complete the login page. Then try the VPN again.
Try another DNS or router path
DNS filtering can break the handshake or make the app look frozen. If your router uses custom DNS, try the default settings for a test. On some networks, simply restarting the router clears a stale connection state.
Change the protocol when the default one fails
ProtonVPN can use different protocols, and the best one depends on the network. Smart Protocol is a good starting point, but it does not always pick the best option on restrictive Wi-Fi. If ProtonVPN is not connecting, test the protocols one by one.
| Protocol | Strength | When to use it |
|---|---|---|
| WireGuard | Fast and modern | Good for everyday use and stable networks |
| OpenVPN UDP | Balanced speed and reliability | Useful on most home and office networks |
| OpenVPN TCP | More reliable on restrictive networks | Best choice for public Wi-Fi or networks that block UDP |
| Smart Protocol | Automatically selects a protocol | Good first try, but not always the final answer |
Rule of thumb: if WireGuard fails, try OpenVPN UDP. If that still fails, move to OpenVPN TCP. It is slower, but it often gets through strict networks.
Check app settings and account status
Sign out and sign back in
Account sync issues can cause connection failures even when the network is fine. A fresh sign-in helps the app pull the latest server and account data. This is especially useful after a password change or a long period of inactivity.
Make sure the app is up to date
Old builds can break after protocol changes or operating system updates. If the app has not been updated in a while, install the latest version and try again. If the current install seems corrupted, reinstalling usually helps.
Check free plan limits and server load
If you use proton vpn free, connection issues are more common during busy hours because the available servers can get crowded. That does not mean your account is broken. It often just means you need to switch to another free server or wait a bit and try again.
Firewall, antivirus, and system conflicts
Security software is one of the most overlooked reasons ProtonVPN not connecting. Firewalls can block the tunnel before it finishes, and antivirus tools sometimes treat VPN traffic as suspicious, especially after a recent update.

- Allow ProtonVPN through the firewall on your device.
- Check whether antivirus or endpoint protection has a network filter enabled.
- Temporarily disable third-party security tools for a quick test.
- Remove old VPN drivers if you used another VPN before ProtonVPN.
If the app starts working right after you change a security setting, you have found the conflict. Turn the protection back on one step at a time so you can see which setting caused the block.
A practical step-by-step order to follow
- Confirm your internet works without the VPN.
- Switch to another network, such as mobile data or a hotspot.
- Open the Wi-Fi sign-in page if the network uses one.
- Change the VPN protocol from Smart Protocol to WireGuard or OpenVPN.
- Try a different server.
- Sign out of ProtonVPN and sign back in.
- Check firewall and antivirus rules.
- Update or reinstall the app if nothing else works.
This order saves time because it starts with the highest-probability fixes. You do not want to spend twenty minutes changing app settings if the real issue is a blocked Wi-Fi network or a crowded server.
When reinstalling makes sense
If ProtonVPN keeps failing after you have tried different networks, protocols, and servers, a clean reinstall is worth it. This is especially true after an operating system upgrade or when the app behaves strangely on every network. Use the official download source, remove the old version completely, then install a fresh copy before signing in again.
Conclusion
When ProtonVPN is not connecting, the fastest fix is usually not complicated. Start with the network, then the protocol, then the app, and finally the firewall or account. That order covers the most common causes without wasting time. If you work through the steps above, you can usually get the VPN working again without resetting your whole device.
FAQ
Why does ProtonVPN connect on mobile data but not on Wi-Fi?
Your Wi-Fi network is probably blocking VPN traffic, forcing a captive portal, or using a firewall rule that interferes with the tunnel. Try a hotspot to confirm.
What protocol should I use if ProtonVPN will not connect?
Try OpenVPN TCP first on restrictive networks, then OpenVPN UDP or WireGuard on normal networks. Smart Protocol is fine as a starting point, but not always the best final choice.
Can antivirus software stop ProtonVPN from connecting?
Yes. Some antivirus tools inspect or block VPN traffic. Add ProtonVPN to the allow list or test with the antivirus temporarily disabled.
Is the free plan more likely to have connection problems?
It can be, mainly because free servers are more crowded. If one server fails, try another free location or connect later when traffic is lower.
What should I do if ProtonVPN still will not connect after reinstalling?
Check your firewall, router, DNS settings, and account status. If all of that looks fine, the issue is likely network-side rather than app-side.