VPN says "timeout" and won't connect: 8 causes and fixes
Why a VPN app hangs on "Connecting" or reports a timeout, and how to find the cause yourself in five minutes: another VPN, device limit, stale subscription, carrier filtering, DNS, wrong server.
"Timeout", "connection timed out", an endless "Connecting…": this is the most common thing people bring to support. There are only a handful of causes, and almost all of them can be checked without us. Go down the list in order; it is sorted from most to least frequent.
1. Another VPN is already on
A phone holds only one VPN tunnel. If another service, a corporate VPN or an antivirus "protection" is running, our tunnel cannot start and the app waits until it times out. Look for a key or "VPN" icon in the status bar. Android: Settings → Network → VPN, switch everything else off. iPhone: Settings → VPN, toggle off. Then connect Surok.
A related case: you refreshed the subscription while a foreign VPN was on. The server saw a foreign address and may have handed you a list without the in-country entry. Turn the other VPN off and refresh again.
2. Device limit reached
Plans are counted per device. If you removed and re-added the subscription in the app, it may present itself as a new device while the old record still holds the slot. The app then receives a stub instead of servers and shows a timeout or "no configuration selected". Open your account, section "Devices", and remove the extra one. Not sure which one? Remove all: the current device re-binds on the next refresh.
3. The link was opened in a browser, not added to the app
A subscription link is an address for the app, not a web page. Opening it in a browser shows your account but adds no VPN. In the bot tap "Connect", choose your device and app, then "Add subscription to …": the app opens and imports the link itself.
4. Stale server list
Servers change, and apps refresh the list every few hours. If you haven't opened the app for a while or disabled auto-update, pull the list down or tap the refresh icon next to the subscription name. In Happ it is the arrow to the right of "surokvpn.com", in v2RayTun the arrow above the list.
5. Wrong server selected
The first server in the list is not always the best for your network. Try in turn: "Europe · Wi-Fi", then a specific country, then the fallbacks. Each uses a different disguise, and different networks let different ones through. At least one works almost everywhere.
6. Your mobile carrier filters non-standard ports
Works on home Wi-Fi, fails on mobile data: carrier whitelisting. Only traffic that looks like an ordinary website passes. For that we have the "Europe · auto" profile: it goes through a CDN on port 443 and looks like image downloads. Pick it while on mobile data.
7. DNS is not answering
The app first has to resolve the server name. If your ISP's DNS or the private DNS configured on the phone is blocked, the connection dies before the first packet. Check: disable "Private DNS" on Android (Settings → Network → Private DNS → off) or the DNS profile on iPhone and retry. Surok's subscription uses IP addresses rather than names, so this mostly affects other providers' subscriptions.
8. Subscription expired or inactive
Obvious, but it happens: the trial ended, a payment failed, wrong account. In the bot tap "My account": the expiry date is right there. If the date is fine and the VPN is not, go back to the list above.
If nothing helped
Message the support bot with a screenshot of the app right after you press connect, your carrier's name and the network type: Wi-Fi or mobile. By account number we can see whether the subscription was refreshed, which server was issued and whether packets reached it. Usually it takes two or three messages.
And if you would rather not touch settings at all, Surok has its own app: it picks a working server itself, warns about another VPN and never meets half the problems on this list.
