A VPN can fail to connect for a dozen different reasons — from a carrier filtering the protocol to the wrong time on your device. We go through them in order, from most to least common, and give a step-by-step routine that solves most problems within minutes.
These recommendations apply to any VPN service; wherever the fix depends on the app, we describe how it works in MeduzaVPN.
A five-minute quick check
Before digging into the details, go through this sequence. It’s built so that the most likely causes are checked first.
- Make sure the internet works without the VPN: open any website.
- Switch protocol in the app: from WireGuard or OpenVPN to MeduzaVPN ULTRA, then to VLESS.
- Switch networks: if you’re on Wi-Fi, try mobile, and vice versa.
- Check the date and time on your device, and turn on automatic sync.
- Turn off the kill switch while you check, so it doesn’t block the diagnosis.
- Restart the app, then the device.
- Check your subscription status in your profile — an expired one also looks like “won’t connect.”
Also check the state of the server itself. In MeduzaVPN it’s shown in the app: if the server is “deploying” or “moving” after a location change, the connection will appear on its own within a few minutes. An expired subscription or an unpaid renewal also looks like a connection failure, even though the cause isn’t the network.
If the connection appears after step two, you can stop reading: the carrier is filtering the protocol, and you’ve already worked around it. Save that protocol for this network.
Mobile network or Wi-Fi: why it matters
The same app with the same server can work at home and fail to connect from a phone out on the street. That’s because filtering is set up differently for mobile carriers than for home providers.
Mobile networks
Carriers more often restrict UDP traffic, apply stricter DPI rules, and react faster to uniform encrypted streams. Here, classic protocols fail first, while protocols with disguise hold up longer. Switching to a TCP transport inside the protocol sometimes helps.
Home and office Wi-Fi
Home providers are usually more lenient, but the router can add its own problems: outdated firmware, IPv6 disabled locally while enabled on the server, overly aggressive NAT. Office and hotel networks often block everything except ports 80 and 443 over TCP — in that case only a protocol that can work over 443 will connect.
Practical takeaway: test the VPN separately on every network you use it on, and save a protocol for each one.
Protocol not getting through: switch it
The most common cause in 2026 is that the carrier recognises the protocol by its handshake and resets the connection. Symptoms: the app hangs on “Connecting…” for a long time and then times out, or it connects and drops a minute later. The server’s address is still reachable — you can check it with ping.
| Not working | Try | Why it helps |
|---|---|---|
| WireGuard, IKEv2 | MeduzaVPN ULTRA | ULTRA has no recognisable handshake — the traffic looks like ordinary web browsing. |
| MeduzaVPN ULTRA | VLESS with REALITY | The connection is disguised as TLS to a real website, running over TCP 443. |
| VLESS | Shadowsocks, then SoftEther | A different kind of disguise; SoftEther travels as HTTPS over port 443. |
| Any UDP protocol on mobile | The same protocol over TCP | Some carriers restrict UDP entirely. |
In MeduzaVPN, every protocol runs on the same personal server, so switching doesn’t change your location or IP address. For more on how they differ, see the pages for MeduzaVPN ULTRA and VLESS.
DNS, time and MTU
DNS: the tunnel is up, but sites don’t open
If the status says “Connected” but pages don’t load, check whether the site opens by IP address. If it does, name resolution isn’t working. Causes: DNS requests are bypassing the tunnel and reaching your provider, which filters them, or the app got the wrong DNS from the system. Turn on “DNS through VPN” in the settings, or set a public resolver manually.
Time and date
Every modern protocol checks certificates or timestamps. If your device’s clock is off by a few minutes, the handshake gets rejected, and the app reports a certificate error or simply doesn’t connect. Turn on automatic time sync — it solves the problem in most cases.
MTU: it connects, but everything is very slow
MTU is the maximum packet size in the tunnel. If it’s larger than the network can pass through, large packets get dropped: small pages load fine, but video and large files hang. Lower the MTU in the protocol settings to 1280–1360 and check again. This is an especially common cause on mobile networks.
Device-side issues: Android, iOS, Windows
Android: battery optimisation and “Always-on”
Android aggressively puts background apps to sleep, and for some manufacturers this affects even VPNs. Symptom: the connection drops when the screen turns off. Open the battery settings for the MeduzaVPN app and choose “Unrestricted.” You can also turn on “Always-on VPN” in the system network settings — then the system brings the tunnel back up on its own after a restart.
iPhone and iPad: the VPN profile
On iOS, the app creates a system VPN profile on first connection. If you declined permission or the profile got corrupted, the app won’t be able to bring up a tunnel. Check the “VPN & Device Management” section in Settings: the MeduzaVPN profile should be there. If it isn’t, reinstall the app and allow it to create the profile.
Windows and macOS
On Windows, the connection is most often blocked by antivirus software or a third-party firewall: add the app to your exceptions. If the virtual adapter disappeared after a system update, reinstall the app. On macOS, check that the VPN extension is allowed to run in “System Settings → Privacy & Security.”
Kill switch, routers and other network causes
Kill switch
A kill switch blocks traffic while the VPN isn’t connected. It protects against leaks, but during troubleshooting it gets in the way: if the tunnel can’t come up, the device looks fully disconnected from the network. Turn the feature off temporarily, find the cause, and turn it back on.
Router
If the VPN is set up on a router, check that the time is synced, the firmware is up to date, and the WAN connection doesn’t restrict UDP. For OpenWrt routers, MeduzaVPN provides ready-made configurations; instructions are on the VPN for a router page. If the VPN doesn’t connect on the router but works from a phone on the same network, the problem is in the router’s configuration, not with the carrier.
Split tunneling
If some apps don’t see the VPN while others do, check your split-tunneling rules — the app you need may have ended up in the exceptions.
When to contact support
If you’ve gone through the quick check, switched protocol, and verified time and DNS, and there’s still no connection — it’s more efficient to work through it together from here. Contact MeduzaVPN support and include:
- your device and OS version;
- the type of network and your carrier;
- the server location and protocol you tried;
- the exact error text, or the point where the connection stalls;
- the log from the app, if there’s a button to send diagnostics.
A personal server lets us check whether packets are reaching it from your side and pinpoint exactly where the path breaks. In most cases the fix is switching protocol or transport, which we can tailor to your carrier.
If you don’t use MeduzaVPN yet, the first seven days of a subscription are free — enough to test it on all your networks. See the terms on the personal VPN pricing page.
FAQ
The VPN connects, but sites won’t open. Why?
Most often it’s DNS: the tunnel is up, but name lookups either don’t go through it or go straight to your provider, which filters them. Check that “DNS through VPN” is enabled in the app, and try opening a site by IP address. The second common cause is an MTU that’s too large, which drops big packets — lower it in the protocol settings.
Why does the VPN work at home but won’t connect on a mobile network?
Mobile carriers usually filter traffic more strictly than home providers and often restrict UDP. Switch to a protocol with disguise — MeduzaVPN ULTRA or VLESS with REALITY — and, if available, to a TCP transport. You can save that choice separately for your mobile network.
The connection drops after a few minutes. What should I do?
If the drop happens on a mobile network, it could be filtering based on traffic statistics — switch protocol. On Android, a common cause is battery optimisation putting the app to sleep: turn it off for the VPN. On iOS, check that the VPN profile isn’t being disconnected by the system when you switch networks.
Do I need to reinstall the app?
Usually not. Reinstalling only helps with a corrupted VPN profile on iOS or macOS, when the system refuses to create a tunnel. In other cases it’s more effective to switch protocol and check the device’s time and DNS. Before reinstalling, make sure you remember how to sign back into your account.
Can antivirus software or a firewall interfere with a VPN?
Yes, especially on Windows. Some antivirus programs intercept network adapters and block the creation of a virtual interface, and a firewall may not let UDP through. Add the MeduzaVPN app to your exceptions, or temporarily disable protection to check whether that’s the cause.
What is a kill switch, and why did the internet disappear after I turned it on?
A kill switch blocks all traffic while the VPN isn’t connected, so data doesn’t leak out directly. If the tunnel can’t come up, the device is left without internet — that’s expected behaviour. Turn the kill switch off while you troubleshoot, restore the connection, and turn it back on.
What should I tell support to get the issue resolved faster?
Give your device and OS version, the type of network (home Wi-Fi, mobile, office), your carrier, the location and protocol you tried, and the exact error text. If the app has a button for sending diagnostics, tap it — the log will come in with your request. That way we can see exactly where the connection stalls.