Why is Telegram not working even with a VPN: reasons and solutions
Get Telegram back in 2 minutesfrom $0.06 a day · card or crypto · 14 servers online Download for WindowsWe analyze why Telegram is not loading messages and calls when the VPN is on, and how to fix it on Android, iPhone, Windows, and Mac. Real steps for 2026.
Telegram is not working with the VPN on: reasons and solutions
Why is Telegram not working with the VPN on — one of the most common questions in thematic chats and forums. I turned on the VPN to bypass the block, but the messenger stopped. Texts sometimes come through, but photos get stuck at 0%. Or nothing loads at all. There are several reasons, and they vary — that's why the advice to "just change the server" works in about half of the cases.
Below is an analysis of specific scenarios with concrete steps. No fluff.
In short: why Telegram is not working with the VPN on
If you need a quick answer: most often, five things are to blame. The MTU does not match the tunnel, the VPN server is overloaded or blocked, a built-in proxy is enabled within Telegram, DNS is leaking outside the tunnel, or Telegram is bypassing the VPN through split tunneling.
Get Telegram back in 2 minutes
- Download the NvoVPN app
- Sign in with Google or email
- Tap “Connect” — Telegram works again
from $0.06 a day
card or crypto
14 servers online
Main reasons in one list
- Incorrect MTU — text goes through, media gets stuck at 0%. Typical for WireGuard with MTU 1420.
- Blocked or overloaded VPN server — everything freezes, changing the location helps.
- Provider DPI is throttling the protocol — VPN seems connected, but traffic is being cut. Characteristic for OpenVPN and WireGuard without obfuscation.
- Built-in MTProto/SOCKS5 proxy is enabled simultaneously with the VPN — conflict of two tunnels.
- Split tunneling — Telegram is excluded from the tunnel and goes directly, where it is blocked.
- DNS leak — Telegram server addresses are resolved through the provider's DNS, which returns incorrect results.
How to quickly understand what the issue is
Look at the symptom:
- Text comes through, but photos and videos are stuck → MTU is too large, go to the section about WireGuard.
- Nothing loads at all, but other sites work through the VPN → the server's IP is blocked or DPI is throttling the protocol.
- Calls do not connect, but messaging works → UDP is being cut on the server or corporate Wi-Fi.
- Telegram works on mobile internet, but not through home Wi-Fi with the same VPN → the issue lies with the provider and DPI on that specific line.
- Stopped working after updating the VPN app → the default MTU may have changed.
Analysis of reasons: what exactly is breaking Telegram
Each point is a separate mechanism of failure. Symptoms vary, solutions vary.
Blocked or overloaded VPN server
VPN provider servers regularly end up on the block lists of Roskomnadzor and telecom operators. This especially concerns popular locations — the Netherlands, Germany, the USA. The IP addresses of such nodes circulate in block lists like hot cakes.
Overloading is a separate story. Free VPNs and cheap services with hundreds of users on one server give a ping of 500+ ms and packet loss of 20-30%. Telegram cannot handle this — especially calls and file transfers.
Symptom: everything freezes at once, other applications through the VPN also lag. Solution: change the location or server.
Incorrect MTU with WireGuard and media loading failure
This is something almost no one explains properly. MTU (Maximum Transmission Unit) — the maximum size of a data packet. WireGuard defaults to an MTU of 1420. But if your internet provider or router works with an MTU less than 1500 (PPPoE, for example, gives 1492), then WireGuard packets start to fragment.
Text messages are small — they go through normally. Photos and videos are large — they break into pieces, some are lost, Telegram waits, does not receive, and the progress bar gets stuck at 0%.
The solution is simple: reduce the MTU in the WireGuard settings to 1280. This resolves the issue in most cases. On a router with VPN, check the MTU of the WAN interface — it should match the provider's value.
DPI and blocking of the VPN protocol by the provider
DPI (Deep Packet Inspection) is a technology that Russian providers actively use to filter traffic. The system analyzes the structure of packets and recognizes the signatures of VPN protocols. OpenVPN looks very distinctive on the network. WireGuard is also recognizable — it has a specific structure of UDP packets.
When DPI detects VPN traffic, it throttles or drops it. Formally, the VPN is connected, the icon is lit — but the traffic does not go through. Or it goes, but in bursts.
For such cases, obfuscation is needed: Shadowsocks disguises traffic as random noise, VLESS/XRay can hide under TLS, Amnezia WireGuard adds junk packets and changes headers so that WireGuard becomes unrecognizable. This really works better than plain WireGuard on home Rostelecom or MTS.
The built-in proxy (MTProto/SOCKS5) inside Telegram conflicts with VPN.
Many configure MTProto proxy or SOCKS5 directly in Telegram — this was a popular way to bypass blocks before the widespread adoption of VPNs. And then they forget to turn it off when switching to VPN.
The result is a double tunnel. Telegram tries to connect through the proxy, the proxy works through the VPN, resulting in a chain with double latency and conflicting routes. Calls often do not work at all — they are especially sensitive to delays.
The rule is simple: either VPN or built-in proxy. Both at the same time — no.
DNS leak and substitution of Telegram data center addresses.
When the VPN is connected, DNS requests should go through the tunnel. If there is a leak — requests go to the provider's DNS server. And there may well be NXDOMAIN or a substituted address for Telegram servers.
Symptom: Telegram does not connect at all, while other sites open through the VPN. This can be checked in a minute through a browser DNS leak test.
On Android 9+, there is a system private DNS (for example, 1.1.1.1 or dns.google). If it is enabled at the same time as the VPN, they may conflict — the DNS of the tunnel is ignored. Check: Settings → Network → Private DNS, set to "Automatic" or disable while the VPN is active.
Split tunneling: Telegram goes past the VPN tunnel.
Split tunneling is a feature that allows you to choose which applications go through the VPN and which go directly. A useful thing, but there is a nuance: if Telegram is added to the exceptions list (intentionally or by mistake), it goes directly — to where it is blocked.
It's easy to check: go to the settings of the VPN application, find the split tunneling section and make sure that Telegram is not excluded there.
IPv6 bypasses the VPN tunnel.
Some VPN applications and configurations tunnel only IPv4. If the provider gives you an IPv6 address, and the VPN does not intercept it, part of the traffic goes directly, bypassing the tunnel. Telegram can connect to its servers via IPv6 — and then its traffic bypasses the VPN.
Quick solution: disable IPv6 on the network adapter or router or ensure that the VPN tunnels IPv6 as well: in the WireGuard and AmneziaWG configuration, the AllowedIPs line should include ::/0 (along with 0.0.0.0/0).
Step-by-step solution for devices.
Android.
First — check split tunneling in the VPN application. Find Telegram in the exceptions list and remove it from there.
Second — disable the built-in proxy in Telegram: Settings → Data and Storage → Proxy. Make sure it is empty or the switch is off.
Third — if media does not load, find the MTU settings in the VPN application (usually in the advanced settings of WireGuard) and lower it to 1280.
Fourth — check the system private DNS: Settings → Network and Internet → Private DNS. Temporarily set to "Off" and check if Telegram started working.
Fifth — if nothing helps, change the protocol: WireGuard → OpenVPN UDP → OpenVPN TCP → Shadowsocks. The last option is for cases when DPI cuts everything.
iPhone and iPad (iOS).
On iOS, you cannot manually change the MTU — this is a system limitation. Therefore, the solution here is to change the protocol and server.
Disable the proxy in Telegram: Settings → Data and Storage → Proxy. Turn it off if it is enabled.
In the VPN application, change the server — preferably to another country. If it does not help, switch the protocol. On iOS, IKEv2 and Shadowsocks work well — the latter is especially resistant to mobile operators' DPI.
Check if "Private Wi-Fi Address" is enabled in iOS settings with some conflicting DNS resolver. Settings → Wi-Fi → (network) → DNS.
Windows.
Open the VPN client settings, find the split tunneling section and make sure that Telegram (telegram.exe) is not in the exceptions list.
For WireGuard: open the tunnel configuration file and find the MTU line. If it is not there — add MTU = 1280 in the [Interface] section. Save and reconnect the tunnel.
Clear the DNS cache: Win+R → cmd → ipconfig /flushdns. After that, reconnect the VPN.
Check if Windows Defender Firewall is blocking Telegram traffic when the VPN adapter is active. Control Panel → Firewall → Allow an app.
macOS.
For WireGuard through the official client from the App Store: open the tunnel, click Edit, add the line MTU = 1280 in the [Interface] section.
Check the system DNS: System Preferences → Network → (active connection) → DNS. When the VPN is connected, the DNS servers of the VPN provider should be listed there, not the internet provider's.
Clear the Telegram cache: ~/Library/Application Support/Telegram Desktop — the folder can be found through Finder (Cmd+Shift+G). It is not worth deleting the contents of the tdata folder, but the logs and temp folders can be cleaned.
What to check on a router with VPN
If the VPN is up on the router, but Telegram is not working on some devices, it is almost always the MTU on the WAN interface.
Access the router interface, find the WAN settings. If the connection type is PPPoE, the MTU is usually 1492. The WireGuard tunnel on top of it should have an MTU 80 bytes lower: 1412 or lower. Check the WireGuard interface settings on the router, lower the MTU to 1280, and restart the tunnel.
Double VPN (tunnel chain) is a separate nightmare for calls. Each layer adds encapsulation and reduces effective MTU. Calls through two tunnels almost always break — packets are fragmented twice.
How to check that the VPN is indeed the culprit
Honest diagnostics start with a simple step.
Test with VPN turned off and back on
Turn off the VPN. Open Telegram, try to send a message and a photo. If everything works — the problem is definitely in the tunnel, you can follow the steps above. If Telegram does not work even without the VPN — the issue lies with the provider, network-level blocking, or an account problem.
Reverse test: turn the VPN back on and immediately check Telegram. If it broke right after turning it on — that confirms the tunnel is at fault.
Checking speed and packet loss
No "magic numbers" are needed — a methodology is required. Run a ping to a known address (for example, 1.1.1.1) with the VPN turned on: in Windows, this is ping 1.1.1.1 -t in cmd, on Mac and Linux — ping 1.1.1.1. Watch for response time and the lines "Request timed out" — they indicate packet loss.
Losses above 2-3% ruin calls and significantly slow down media loading. If the ping is 200+ ms and there are losses — the server is overloaded or the route is poor. Change the location.
Checking for DNS leaks
With the VPN turned on, open a browser and go to dnsleaktest.com or ipleak.net. Click on Extended test. Check whose DNS servers are shown in the results. If there are addresses from your internet provider (MTS, Rostelecom, Beeline) — there is a leak. DNS should belong to the VPN provider or a neutral resolver like Cloudflare (1.1.1.1).
Comparing behavior on two servers
Switch to a server in another country and check Telegram again. If everything works on the other server — the IP of the first server is blocked or overloaded, the problem is not in the settings, but in the specific node. A good VPN service offers a choice of dozens of locations specifically for such cases.
What DOES NOT help and why
Half of the advice on the internet about this topic is garbage. Let's break it down specifically.
Endless reinstallation of Telegram
Reinstallation does not fix MTU. It does not fix DPI. It does not fix an overloaded VPN server. These are network-level problems — they exist regardless of which version of Telegram is installed. The only case where reinstallation actually helps is a corrupted cache or a bug in a specific version of the app. This is rare.
Blindly turning on all "bypass" options at once
"I'll turn on both the proxy and the VPN, and also Tor on top" — a classic approach that only makes things worse. A chain of tunnels increases latency, further reduces MTU, and creates routing conflicts. This hits calls particularly hard — UDP packets with voice start arriving in the wrong order or get lost.
Free overloaded VPNs
This is a separate topic. Free VPNs — Psiphon, Lantern, Touch VPN — operate on servers packed with users to the brim. The IP addresses of such services are the first to end up on blocklists because they concentrate suspicious traffic. If Telegram does not work when the VPN is on — this is the first suspect when using a free service.
Paid services with obfuscation perform significantly better. NvoVPN, for example, offers protocols with obfuscation for the Russian market — AmneziaWG and VLESS/XTLS-Reality, resistant to DPI.
VPN and built-in Telegram proxy at the same time
| VPN protocol | Visibility to DPI | Speed | Resistance to blocks |
|---|---|---|---|
| WireGuard | High | Very high | Weak under active DPI |
| OpenVPN UDP | High | High | Weak |
| OpenVPN TCP | Medium | Average | Average |
| IKEv2 | Average | High | Average |
| Shadowsocks | Low | High | Good |
| VLESS/XRay | Very low | High | Very good |
| Amnezia WG | Very low | High | Very good |
WireGuard and OpenVPN are fast, but easily detectable by DPI. Shadowsocks, VLESS, and Amnezia are specifically designed for obfuscation—they make traffic look like regular HTTPS. During active blocks, these protocols tend to last longer.
Enabling the built-in Telegram proxy over a working VPN is not "double protection," it's a conflict. The traffic tries to go through two routes simultaneously, and the operating system unpredictably chooses one of them.
Telegram does not work with VPN after the screen is locked: check background restrictions
If messages load while the app is open but stop coming after the screen is locked, check background operation restrictions. Telegram and the VPN app may be prohibited from transferring data in the background, and power saving may suspend their operation. Changing the server does not eliminate such restrictions on the device.
- On Android: open the system app settings and separately check Telegram and the VPN. In the battery section, allow background operation, and in the mobile data section — allow background data transfer. If data saving is enabled, check permissions for both apps. The names of the sections depend on the phone manufacturer.
- On iPhone: ensure that both apps are allowed to use cellular data. To check, temporarily disable low power mode. However, simply disabling background app refresh does not prove the reason for the lack of notifications: delivery of notifications and content updates are different mechanisms.
- On any phone: check notification permissions for Telegram, "Do Not Disturb" mode, and notification settings for specific chats. If messages appear immediately after opening the app, it is important to distinguish between loading delays and the simple absence of notifications.
After changing the settings, connect the VPN, open the desired chat, and lock the screen. Ask your contact to send a message, then check if the notification arrived and if the message appeared when opening the app. Change settings one by one to determine which restriction affected the result.
Telegram does not connect even with VPN on a public or work network.
In a hotel, café, or other guest network, authorization through a welcome page may first be required: accepting terms, entering a code, or confirming access. Until this step is completed, connecting to the wireless network does not guarantee internet access. Checking Telegram and VPN functionality before authorization is pointless.
Open the system notification "Join Network" or a similar item in the wireless connection settings. If the login page does not appear, temporarily disable the VPN and try again. At this stage, do not open sensitive data; after authorization, turn the VPN back on and only then check the messenger. Do not install unknown certificates and apps at the request of the login page.
On a work computer, separately check local access rules. Firewalls or security software may restrict outgoing connections for specific applications, even when the browser opens websites. Do not disable protection entirely: check the block log and permissions for the Telegram and VPN executables. On a managed device, report the issue to the administrator — changing network rules may be prohibited by organizational policy.
To contact support, document the exact connection status in Telegram, the network name, and the results of checks through another permitted network. Do not send login codes, two-factor authentication passwords, VPN keys, or configuration files with secrets.
Frequently Asked Questions
Why does Telegram load text but not open photos and videos when the VPN is on?
A classic sign of too large MTU with WireGuard. Text messages are small and pass normally, while large packets with media files get fragmented and lost. Go to WireGuard settings and reduce the MTU to 1280. If it cannot be changed manually (for example, on iOS) — try another server or switch to Shadowsocks.
Should I enable the proxy inside Telegram if the VPN is already working?
No. Proxy and VPN conflict simultaneously and create a double tunnel with unpredictable routing. Choose one: either VPN (preferably — it protects all device traffic) or the built-in MTProto proxy of Telegram. Disable the proxy: Settings → Data and Storage → Proxy.
Why do calls in Telegram not connect through VPN?
Telegram calls use UDP and partially P2P. Some VPN servers and corporate/school networks completely block UDP — in this case, WireGuard does not start at all. Try changing the server, selecting a protocol that supports UDP, or switching to OpenVPN TCP. Also, check split tunneling — Telegram should not be on the exclusion list.
Which VPN protocol is better for Telegram when the provider blocks it?
With active DPI, Shadowsocks, VLESS/XRay, and Amnezia WireGuard are more resilient — they obfuscate traffic and are not recognized by standard signatures. WireGuard and OpenVPN work faster but are more noticeable to DPI of Russian operators. If the provider actively blocks VPNs — start with Shadowsocks.
Telegram stopped working only after changing the VPN server — what should I do?
The IP of the new server may be blocked by Roskomnadzor or overloaded with other users. Return to a working location or choose another server in the same country. If the problem persists across multiple locations — check if the MTU has changed after updating the VPN application.
Can Telegram not work due to a DNS leak when using a VPN?
Yes. If DNS requests go outside the tunnel, the addresses of Telegram's data centers may resolve through the provider's DNS, which returns a substituted or blocked address. Check via dnsleaktest.com while the VPN is on. If the results show the provider's servers — enable DNS protection in the VPN client settings. Additionally, on Android, check the system's private DNS.
Get Telegram back in 2 minutes
- Download the NvoVPN app
- Sign in with Google or email
- Tap “Connect” — Telegram works again
1-day trial — 29 ₽, no auto-renewal