If access to work services depends on the connection, a VPN failure can stop work. An ISP may be able to block VPNs, but the sources used in this article do not directly confirm such practice by internet providers: the EFF describes VPN blocking mainly by streaming services. Low speed by itself also does not prove a block. Below is a troubleshooting procedure that will help find the cause of the failure.
What can prevent a VPN connection
An internet provider, or ISP, passes data between your device and the VPN server. An established tunnel hides your destination websites from the provider, but the very act of connecting to a VPN server may be noticeable. Whether the provider restricts such connections is not confirmed by the sources consulted here, so treat any failure first as a fault to be diagnosed rather than as proven blocking.
Availability needs to be checked on a specific connection. Draw conclusions about a particular network only after checks: an overloaded server, weak Wi-Fi and router settings cause similar symptoms.
| Possible cause | What to check |
|---|---|
| One server's address is unreachable | Connect to a different VPN location |
| The app's sign-in or tunnel setup fails | Note the error stage and try again later |
| A filter prevents the server's address from being obtained | Check network filters and the name resolution error |
| The line or server is overloaded | Compare connections under identical conditions |
Changing DNS, the service that looks up addresses by name, helps only if the problem is at that stage. In its default protection mode Firefox may fall back to the system resolver with some VPNs; this is described further below and in Firefox's help on DNS over HTTPS.
Does the provider allow VPN use
A VPN failure on your line does not by itself mean VPNs are prohibited under the contract. Check the current terms of your tariff and any active network filters with your provider. Distinguish between the terms of service and technical availability: a prohibition in network rules and a failed connection are different circumstances. In an office, restrictions may be imposed by the employer, even if the telecom operator passes VPN traffic through.
Do not switch off protective settings at random. Note the error message: the app may be unable to sign in to the account, establish the tunnel, or open websites after connecting. These are different stages, and support needs to know precisely the one at which the failure occurs.
How to tell a block apart from an ordinary fault
| Test result | What it indicates |
|---|---|
| Works on the mobile network, fails at home | The cause lies with the home route, filters or router; deliberate blocking is not yet proven |
| Only one server fails | A problem with the address, the server or the route to it is likely |
| Slow both with and without a VPN | Check Wi-Fi and the line's bandwidth first |
| Tunnel connected but websites do not open | Check DNS and ask the VPN's support to trace the name resolution and routing stages |
An example scenario: an employee cannot open a work service through the home VPN. Over the mobile network the same server is reachable, while at home changing servers helps. Work access is restored; the result points to a problem with a specific route or address, but does not confirm a block on all VPNs.
What the provider sees when a VPN is running
For traffic inside a working tunnel, the provider sees the connection to the VPN server rather than the destination websites, which the tunnel usually hides from it. The very fact of VPN use, however, may be noticeable.
Check split routing: this setting sends some apps around the VPN. Their connections do not receive the tunnel's protection. If the VPN drops, behaviour depends on the app and on whether there is a feature blocking connections outside the tunnel.
The EFF explains that a VPN shifts trust to the VPN operator. For more on HTTPS, accounts and the boundaries of network privacy, see the general overview of visibility of visited websites.
Short answers about additional settings
Does a private browser window help?
No, it does not change the connection route and does not lift network restrictions. Chrome and Firefox explain that private mode limits the saving of session data in the browser, but does not make your activity invisible to the network.
Firefox shows DoH "Not active" after enabling the VPN. Is this a sign of blocking?
By itself, this status does not prove a VPN block. In its default mode, Firefox may disable secure DNS with certain VPNs or because of organisational and parental policies, falling back to the system DNS. Check the status and level of protection in Firefox's help on DNS over HTTPS.
What to do if your VPN stops working
A provider may be able to block a VPN, but nothing consulted for this article confirms that it does, and a single failure or slowdown does not prove it. Compare one server on the home and mobile networks, then try a different server and an available protocol, and save the error texts for support.
When the basic internet works but the VPN does not connect, a choice of servers and connection methods helps. I recommend CitadelVPN: the service offers more than 40 locations, VLESS tcp/gRPC/xhttp options and Hysteria2 for difficult networks. Give the support engineers the results of comparing your home and mobile networks, the client's name and the error text — this will help choose the next option to test. Change one condition at a time and, once connected, open the work service you need on your own device. The availability of a specific line and service must be checked on site; having different connection options does not guarantee it.