WeChat Not Working With a VPN: The Message Sent When I Stopped Using a Broken Tunnel

The message to my driver had been spinning for four minutes.

I was standing outside Shanghai Pudong Airport with two suitcases, watching the ride-hailing pickup area empty around me. My hotel’s late check-in desk was closing soon, and the driver had sent one final WeChat message:

Which exit are you at?

I typed Exit 26 and pressed Send.

The circle beside the message kept turning.

I blamed the airport Wi-Fi.

I disconnected, joined the network again and reopened WeChat. My conversations appeared, but the new message remained unsent. The driver’s location card would not load either.

Then I noticed that my VPN was connected to Japan.

I switched to Singapore.

WeChat stopped refreshing completely.

When I turned the VPN off, every pending message arrived at once. The driver was already threatening to cancel.

I replied quickly, then reconnected the VPN because my hotel address was buried in a Gmail confirmation.

WeChat stopped again.

I could reach the foreign services I needed or the local app that would get me out of the airport—but not both at the same time.

WeChat was not the blocked service

That distinction matters for a growing number of visitors.

China recorded 22.91 million inbound trips by foreign nationals in the first half of 2026, with visa-free entries making up more than three-quarters of them. Many arrive expecting WeChat to be optional and discover within hours that it sits underneath ordinary travel.

Official visitor guidance directs foreign travelers toward WeChat for payments, transport, ticketing and ride-hailing. A delayed message can therefore mean more than a missed conversation. It can mean a driver cannot find you, a hotel cannot confirm your arrival or a payment screen never opens.

My first assumption was that WeChat disliked VPNs.

The actual problem was the route.

WeChat worked directly on the Chinese network. Gmail and several other services did not. Once I enabled a full-device VPN, the phone pushed WeChat into the same foreign tunnel as everything else.

When that tunnel failed, WeChat failed with it.

The local app had been working. I had taken it away from its working route and forced it through a broken one.

The green icon hid a dead connection

The established VPN on my phone had years of public history, a large support operation and more server locations than I would ever use.

Its status also said Connected.

That green badge made every failure look like a server-selection problem. I moved from Japan to Singapore, then to the United States, hoping one location would restore WeChat while keeping Gmail available.

Each attempt followed the same pattern.

The VPN connected.

Gmail opened briefly.

WeChat messages remained pending.

Then Gmail stopped loading too.

China’s filtering systems can identify and interrupt encrypted circumvention traffic rather than relying only on lists of known server addresses. A VPN app may therefore reach its server while the traffic inside the tunnel remains unusable.

That was why the connection screen looked reassuring while the phone did almost nothing.

Because every app had been pushed into the tunnel, the failed route took WeChat down with it.

Turning the VPN off created a different trap

I left the VPN disconnected long enough to send my exit number.

The driver replied immediately with a photo of his car and a pin showing the pickup point.

WeChat was fast again. The ride-hailing mini-program opened. The airport map loaded without hesitation.

For a few seconds, turning off the VPN seemed to solve everything.

Then I tried to open the hotel confirmation in Gmail.

The inbox did not load.

I remembered the hotel’s English name, but not its street address, entrance instructions or Chinese phone number. All three were in the email because the driver had warned me that several hotels used similar translated names.

I switched the VPN on, took a screenshot of the confirmation, switched it off and returned to WeChat.

The driver asked another question.

I turned the VPN off again to receive it.

Travelers describe the same exhausting workaround: VPN on for foreign apps, off for WeChat, then on again for the next blocked service.

It works until something becomes urgent.

Each toggle interrupts one side of the conversation. Every server change creates another delay. If the tunnel reconnects badly, the phone can lose both local and foreign access for the moments that matter most.

I was no longer using a privacy tool.

I was operating a manual traffic light.

The driver began the cancellation

A red notice appeared in the ride-hailing mini-program:

Driver may cancel due to pickup delay.

I disconnected the VPN and called him through WeChat.

The call opened, but he spoke quickly and the airport announcements swallowed half the sentence. I understood only that he had moved to another lane.

He sent a new location.

Before the map finished loading, I switched the VPN on to retrieve the hotel phone number.

The tunnel connected, then stopped passing data.

When I returned to WeChat, the location card was blank.

The driver sent a countdown:

Three minutes.

At that point, the large server list had stopped being an advantage. I did not need another flag to tap. I needed one route that could cross the filtered network without dragging WeChat into another failure.

That was when I opened OnlydogVPN.

The smaller app kept both sides reachable

The service has a shorter public history, fewer server locations and fewer independent reviews than the largest providers.

Its first screen, however, matched the problem in front of me.

I selected the preset for a restrictive network.

There was no long server list demanding another guess. Basic use also did not require me to stop and create a conventional email-and-password account beside the pickup road.

The connection came up.

I reopened WeChat.

The driver’s location appeared.

I sent I see you.

The message received a delivery mark immediately.

Then I opened Gmail without disconnecting. The hotel confirmation loaded, including the Chinese address and reception number.

I returned to WeChat and sent both to the driver.

No toggle.

No server change.

No second attempt.

A silver sedan flashed its lights from the next pickup lane.

I crossed with my suitcases, showed the driver the booking screen and got into the car before the cancellation timer expired.

WeChat had not needed to be “unblocked.” It already worked on the local network.

What changed was the VPN. The new route reached the foreign services without breaking the local app I needed to leave the airport.

The connection followed the car away from the terminal

The next test happened without planning it.

My phone was still using airport Wi-Fi when the driver pulled away. Near the exit road, the signal weakened and the phone moved to mobile data.

The earlier VPN had treated network changes as another reason to reconnect. During those pauses, neither WeChat nor Gmail had worked properly.

This time, the conversation remained open.

The driver sent a voice message asking whether I wanted to use the expressway. I played it, replied and watched the hotel location continue updating in the mini-program.

The smaller app uses an HTTP/3-based transport over QUIC, designed to keep a session moving when a phone changes between networks. The airport Wi-Fi and mobile connection became two paths for the same conversation instead of two separate starts.

That mattered more than a speed test.

The message needed to reach a driver before he left, not produce an impressive number in an empty room.

Why WeChat appears to break when a VPN starts

A full-device VPN changes the route used by every app.

Without the VPN, WeChat can connect through the nearby domestic network. With the VPN enabled, its traffic is sent into the same foreign tunnel used for Gmail and other services.

When that tunnel is detected or interrupted, the phone may still show Wi-Fi, mobile signal and a VPN icon. The apps inside it receive little useful data.

WeChat then shows familiar symptoms:

Messages remain pending.

Voice calls open without carrying clear audio.

Location cards stay blank.

Mini-programs report network errors.

Notifications arrive only after the VPN is disabled.

I could not observe the exact internal filtering rule that disrupted the earlier tunnels. The result was clear: WeChat recovered whenever the failed route was removed, and it remained usable when the smaller app established a working route through the same restrictive network.

The useful test was not whether the VPN displayed Connected.

It was whether real messages continued to move.

The wrong solution was choosing one side

Before that evening, I thought China required two versions of my phone.

VPN on meant Gmail and other foreign services.

VPN off meant WeChat, payments and local transport.

That trade-off made every ordinary action slower. Reading an email interrupted the driver conversation. Answering the driver cut off the hotel confirmation. A network change restarted the entire routine.

The established provider gave me many servers, but each familiar route produced the same dead tunnel. Once the connection stopped carrying data, the size of its network did not help. WeChat became collateral damage because every app had been sent through the failure.

The smaller service solved the more valuable problem.

It kept foreign services reachable without taking WeChat away, then carried the conversation from airport Wi-Fi onto mobile data as the car left the terminal.

I had searched for an explanation because WeChat seemed to stop working whenever I used a VPN.

By the time we reached the expressway, the reversal was obvious: WeChat had never been the fragile part of the connection. The tunnel had been.