If your VPN won't connect, don't worry. Most connection problems have a simple cause. Follow the steps below in order to get back online.
If your VPN is not connecting, first check that your account or plan is active and that your device's date and time are correct. Then try a different server, and if your app supports more than one protocol, try switching between WireGuard and V2Ray with REALITY. Finally, test on a different network, such as mobile data instead of Wi-Fi, to see whether the network itself is causing the problem.
Before working through every step below, check this table. It often points straight to the fix you need.
| Symptom | Most likely cause | Immediate action |
|---|---|---|
| Fails on one server only | That server is temporarily down or congested | Switch to a different server location |
| Fails on Wi-Fi, works on mobile data (or the reverse) | That specific network may be filtering VPN traffic | Try a different protocol, such as V2Ray with REALITY, or switch networks |
| Connects, but no websites load | DNS resolution failure | Flush your DNS cache or switch to a public DNS server |
| Connects, then drops after a few seconds | Battery optimization or an unstable network | Turn off background restrictions for the app, or switch networks |
| "Authentication failed" or "Handshake failed" | Expired plan, wrong config, or device clock drift | Re-import your configuration and check your device's date and time |
These are two different problems, and it helps to know which one you have before you start troubleshooting.
The app gets stuck on "Connecting," shows an authentication or handshake error, or fails right away.
The app shows a successful connection, but web pages won't load or time out.
Log into your RapidPing dashboard with the email you used at purchase. If you've run out of data or your plan has expired, the VPN won't connect. Buying a new plan or topping up solves this instantly.
VPN connections use secure handshakes that can fail if your device's clock is significantly out of sync. Set your device to automatic date and time in its settings.
Open your VPN app and confirm the correct config or subscription link is selected. If you recently reset your device, changed your plan, or reinstalled the app, re-import a fresh config from your RapidPing dashboard.
A single server can occasionally be busy or briefly unreachable. Switch to another server location in your app and try connecting again. This can quickly tell you whether the problem is specific to one server.
If you're on a network that filters VPN traffic, switching from WireGuard to V2Ray with REALITY (or the other way around) may resolve the problem. Every RapidPing plan includes both, so you can switch without buying anything new. No protocol can guarantee a connection on every restricted network.
An outdated app is a common, easy-to-miss cause of connection failures. Check your app store or the app's own update option and install the latest version.
Security software can inspect and drop encrypted VPN traffic. Add your VPN app to its exception list. If you disable security software briefly to test, turn it back on right after.
This clears temporary glitches and resets your device's network interfaces. Restart the app first; if that doesn't help, restart the device itself.
Do steps 1 and 2 first, even if they seem too simple. An expired plan or an incorrect device clock can be easy-to-miss causes of failed connections — and both take under a minute to check.
If your app shows a successful connection but nothing loads, the problem is often related to DNS, routing, or your device's network settings rather than the VPN tunnel itself.
ipconfig /flushdns | macOS Terminal: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder1.1.1.1) or Google (8.8.8.8) in your network or VPN app settings.| Error message | Common cause | Recommended fix |
|---|---|---|
| Connection timed out | Server offline, high latency, or blocked port | Switch server, try another protocol, or test another network |
| Authentication failed | Wrong credentials or an expired plan | Re-check your login, or verify your plan status in the dashboard |
| Handshake failed | Wrong config, device clock drift, or a firewall block | Re-import the config, fix your device clock, or allowlist the app |
| Server unreachable | Network routing block or a temporarily offline server | Pick a different server, or try a different protocol |
| Connected, but no data flows | DNS issue or a broken network interface | Flush DNS, switch DNS server, or restart the device |
Make sure the VPN permission prompt was accepted when you first connected. Check Settings → Apps → your VPN app → Battery, and turn off any battery-saving restriction that could be closing the app in the background.
Check Settings → VPN and confirm the correct profile is selected and turned on. If you use "Connect On Demand," turn it off and try connecting manually once to see if that's the cause.
Windows Firewall or antivirus software can sometimes block VPN apps. Check whether the VPN app is allowed through Windows Firewall, or try Settings → Network & Internet → Advanced network settings → Network reset if the issue persists.
macOS may ask you to approve a system extension the first time you install a VPN app. Check System Settings → Privacy & Security for a pending approval request if the app won't connect after installation.
Some networks, like hotel or airport Wi-Fi, require you to open a login page in your browser before any other traffic is allowed. Complete that sign-in page first, then open your VPN app.
If your VPN connects on one network but not the other, the issue may be specific to that network rather than your account. Try switching servers or protocols while on the network giving you trouble.
If a connection issue only happens on one specific network (like your office or a certain café), the network may be filtering or interfering with VPN traffic rather than there being a problem with your plan or device.
If one server doesn't connect, the whole service is down
A single server can be temporarily busy
Switching to a different server location usually reconnects you right away.
A VPN should always connect instantly with zero setup
One correct setup step matters
Importing the right config or subscription link once is usually all that's needed. After that, connecting is a single tap.
Strong Wi-Fi signal means the VPN will definitely connect
Signal strength and VPN connection are different things
Connection problems are usually caused by app settings, filtering, or account status — not how strong your Wi-Fi signal is.
This usually happens when the server is unresponsive or the network is dropping the connection handshake. Switching to a different server or trying another protocol usually resolves it.
Yes. Many antivirus programs include their own network filtering that can conflict with VPN apps. Adding your VPN app to the antivirus or firewall's exception list usually fixes this.
Wi-Fi and mobile data are separate connections, and each can have its own restrictions. If one works and the other doesn't, the problem is often with that specific network rather than your account.
V2Ray with REALITY is designed to make its traffic less distinguishable from ordinary TLS traffic, which may help on some networks with VPN filtering. No protocol can guarantee a connection on every restricted network.
This is usually a DNS problem rather than a connection problem. Try flushing your device's DNS cache or switching to a public DNS server, such as 1.1.1.1 or 8.8.8.8.
Yes, in many cases. A single server can be temporarily busy or briefly unreachable. Switching to another location is one of the fastest ways to test whether the problem is server-specific.
You can check your remaining data and plan status by logging into your RapidPing dashboard with the email used at purchase. A plan with no data left will not be able to connect.
Contact RapidPing support with your device type, app name, and what happens when you try to connect. Having these details ready helps the team find the cause faster.