1. Check the internet connection without the VPN
Disconnect the VPN briefly and try loading a familiar HTTPS page. If it still does not load, resolve the Wi-Fi or mobile connection first. On hotel and airport Wi-Fi, finish the network’s sign-in page before reconnecting. Confirm the network name with staff before entering details.
This test sends the test page outside the tunnel. Reconnect before doing anything that requires the VPN. Do not dismiss a browser certificate warning or enter sensitive information into an unexpected sign-in page.
2. Check the correct account and connection path
In the mVPN Android app, check that you are signed in, review the balance and select a server shown in the app. For a manual WireGuard profile, check the profile’s status and location in the web dashboard. Use the setup instructions for the path you actually chose.
An unavailable balance, disabled profile or unavailable server can explain a failed session. Check the displayed status before purchasing more data or replacing a configuration; neither action is a guaranteed fix for a network problem.
3. Reconnect and compare one network at a time
- Disconnect, select an available location, and reconnect.
- Check whether another VPN app is active. Pause the conflicting tunnel during this test; do not disable device security or your firewall.
- If possible, test on a second trusted network, such as your own mobile data. Be aware of mobile charges.
- Test the same page again. If it works on one network only, that suggests a network-specific restriction or routing issue.
WireGuard uses UDP. Some networks restrict that traffic. Trying a different server may help identify the scope of the problem, but access on every network or to every service is not guaranteed.
4. For manual WireGuard profiles, inspect the right signals
If the client shows a latest handshake, generate some traffic by loading a page and then check it. A recent handshake suggests the peer exchange is working, but does not prove DNS or internet routing is correct. No recent handshake can have several causes, including endpoint reachability or an inactive profile. Received and sent counters provide another clue, not a diagnosis by themselves.
If names fail to resolve while other connectivity works, DNS is a possible cause. Use the provider-issued configuration and supported DNS settings; do not paste random DNS, endpoint, MTU or AllowedIPs changes from a forum. If your profile was revoked or replaced, import the current file or QR code through the official setup flow. Do not reuse one private configuration on several devices.
Persistent keepalive can help maintain a NAT mapping during idle periods. It is not a general cure for missing internet access. WireGuard’s documentation recommends enabling it only when needed; ask support before changing a managed profile.
5. Send support useful observations
Record your device and OS, app version, selected location, connection time with timezone, whether the network is Wi-Fi or mobile data, the visible error, and whether the test worked without the VPN or on another trusted network. For manual profiles, describe whether a recent handshake and received traffic appeared.
Never publish your configuration file, QR code, private key, password or subscription link. Redact account details and secrets from screenshots. These checks narrow the cause; they do not guarantee that a particular website or network will work.
Common questions
Does “connected” mean every app is using the VPN?
No. Connection status alone does not prove route coverage or that every service is reachable. Follow the setup flow and test the service you need.
Should I keep recreating profiles?
No. First check the underlying network, account status and selected location. Replace a profile when it is revoked, outdated or support directs you to do so.
Should I turn off my firewall?
No. Leave security protections in place. Compare networks and use the supported configuration to narrow the issue.
Sources and product scope
The protocol details follow the official WireGuard documentation. mVPN billing and platform availability were checked against the public product configuration on 5 October 2026; the app or dashboard shows your account-specific options.