VPN Not Working in India? The Fix Wasn’t Another Server

The upload bar froze at 83 percent while my client waited for the final production files in London. I was in a Bengaluru hotel room, using the Wi-Fi beside the desk because it seemed stronger than the signal near the bed. When the connection slowed, I switched the laptop to my Jio hotspot. The VPN immediately changed from green to Reconnecting and stayed there. I blamed the mobile signal, restarted the hotspot and selected a different server. The tunnel failed again before the upload resumed.

The files were not optional.

They contained the approved images, copy and configuration package for a product launch scheduled to begin when the London team came online. The client already had the drafts. What they needed now was the signed version I had promised before breakfast.

Without the VPN, the hotel network could reach ordinary websites, but the client’s protected upload portal rejected the connection.

With the VPN, the portal opened—but only while I remained on hotel Wi-Fi.

The moment I moved to mobile data, the tunnel stopped connecting.

That was the real problem behind “VPN not working in India.”

The subscription was active. The laptop was fine. The internet itself had not disappeared.

The same VPN simply behaved differently on two Indian networks five seconds apart.

The India location was not necessarily nearby

I initially assumed the nearest server would be the safest choice.

The large provider displayed two Indian locations, so I selected one and expected a short, direct route.

India’s VPN market changed after CERT-In issued cybersecurity directions requiring certain providers operating relevant infrastructure in the country to retain specified customer information for five years. The agency later clarified that the requirement applied to consumer VPN services rather than private corporate VPNs. (CERT-In)

Several major providers responded by removing physical servers from India. Some continued offering Indian IP addresses through machines hosted elsewhere. One major provider, for example, says its virtual Indian locations are physically hosted in Singapore and the United Kingdom. (ExpressVPN)

That did not make a virtual location useless.

It did mean that India in the server menu did not tell me the whole journey.

My apparently nearby connection could leave the country before reaching the client portal. On hotel broadband, that route was slow but usable. On the Jio hotspot, the provider’s automatic connection would not hold at all.

I had been choosing cities.

The network was reacting to the connection itself.

The established provider worked until I changed networks

The major provider had been a reasonable first choice.

It had years of public history, a large support operation and far more independent reviews than the smaller services on my devices. I had used it successfully in Europe and Southeast Asia.

On the Bengaluru hotel Wi-Fi, it connected after about twenty seconds.

The upload portal accepted the route.

The 412-megabyte package reached 41 percent, paused, continued to 83 percent and then stopped when the hotel network weakened.

That was when I turned on the phone’s hotspot.

The laptop joined Jio immediately. Ordinary websites opened. The VPN did not.

I switched from the Indian location to Singapore.

Still reconnecting.

I tried the provider’s automatic “fastest” option.

The app displayed a green status for four seconds, then disconnected before the upload portal reopened.

Jio users have described similar cases in which automatic VPN connections failed until they changed the connection mode manually. (Reddit) That matched the practical problem on my desk: the provider kept retrying an approach the mobile network would not carry.

The VPN was not broken everywhere in India.

It was failing on the network I needed at that moment.

More server choices were not changing that.

Indian networks do not all behave the same way

The difference between the hotel Wi-Fi and the hotspot was not as strange as it first appeared.

Research across major Indian internet providers has found that networks use different blocking methods and do not always restrict the same destinations. (Singh) A connection that works on one provider may therefore fail on another without anything changing on the device.

That explained the contradiction.

The hotel broadband could carry the established provider’s tunnel, although poorly.

The Jio hotspot could carry ordinary internet traffic, but the VPN’s automatic mode repeatedly stalled.

Changing countries inside the app did not solve the mismatch underneath.

By then, the London team had started sending messages.

Can you share the final package before stand-up?

I typed Uploading now, which was becoming difficult to defend.

The free extension opened the wrong part of the workflow

I tried a free browser proxy because it promised a one-click Singapore connection.

The client portal opened.

For a moment, that looked like progress.

Then I remembered that the production package was being sent by the client’s desktop transfer tool, not through the browser.

The extension covered the webpage.

It did not cover the application performing the upload.

I could have split hundreds of files into smaller browser uploads, checked them again and asked the client to rebuild the delivery. That would have converted one network problem into a file-management problem.

The free option had solved the screen I could see while leaving the actual task untouched.

I closed it.

By then, the comparison had become simple.

I did not need another country or another browser tab.

I needed a tunnel that could establish itself on the Jio hotspot and carry the desktop upload to completion.

The backup treated the network as the problem

I had installed OnlydogVPN^↗ several weeks earlier but had not made it my main service.

The established provider had more locations, more ratings and a much longer public history. The smaller app’s shorter record was the reason I had treated it as a backup.

But its opening screen matched the situation better.

Instead of presenting a world map first, it offered presets based on what I was trying to do. I selected the option for a restrictive or unreliable network.

The app connected through the Jio hotspot.

I reopened the client portal.

It loaded without another server search.

Then I returned to the desktop transfer tool and pressed Resume.

The progress bar remained at 83 percent for several seconds.

It moved to 84.

Then 86.

I placed the phone beside the window where the 5G signal was strongest and stopped touching anything.

Ninety-one percent.

Ninety-six.

The hotel Wi-Fi reappeared in the laptop’s network list, but the hotspot remained connected and the tunnel stayed up.

At 100 percent, the portal began verifying the package.

A minute later, the client message arrived:

Files received. We’re good for launch.

That completed the task.

The result explained enough

The backup uses an HTTP/3-based connection with additional obfuscation for networks that interfere with familiar VPN traffic.

The important explanation was already on the screen.

The established provider connected through the hotel broadband but repeatedly failed on the Jio hotspot.

The free extension reached the browser but not the upload application.

The backup established one usable route and carried the remaining 17 percent of the package.

I could not observe the mobile operator’s internal filtering rules. I could compare the outcomes on the same laptop, phone and hotspot.

In this situation, adapting to the network mattered more than moving through a longer list of server locations.

The hotel Wi-Fi returned at the worst moment

Once the package passed verification, I began downloading the client’s final approval document.

The Jio signal dropped from 5G to 4G.

The file paused.

At almost the same moment, the laptop rejoined the hotel Wi-Fi automatically.

I expected the VPN to disconnect and force me back through another server selection.

Instead, the connection recovered and the document continued downloading over the hotel network.

That was a smaller result than delivering the production package, but it solved the next problem naturally.

The main failure had been establishing the tunnel on mobile data.

The next risk was losing it when the laptop moved back to Wi-Fi.

The service handled both without asking me to choose another city.

The phone took over after the work was finished

The London team approved the launch shortly before I left the hotel.

I needed the client chat and monitoring dashboard on my phone during the taxi ride, but the backup had only been configured on the laptop.

The laptop displayed a verification code.

I entered it on the phone and connected without creating another conventional email-and-password account.

The client chat refreshed.

The launch dashboard opened.

That did not rescue the upload. The main task was already complete.

It simply meant I could leave the desk without losing access to the project.

The laptop went into my bag.

The phone took over.

“VPN not working” can hide several different failures

Before that morning, I had treated every failed connection as the same problem.

It was not.

Sometimes the VPN app cannot authenticate.

Sometimes one Indian provider carries the tunnel while another interrupts it.

Sometimes an Indian server is actually a virtual location outside the country.

Sometimes the browser works because only an extension is active, while the application doing the real work remains outside the tunnel.

And sometimes a VPN connects but cannot recover when the device moves between 5G, 4G and hotel Wi-Fi.

Rapidly changing countries can hide those differences.

A better test is to keep the original task unchanged and alter one thing at a time.

Switch between Wi-Fi and mobile data.

Try a mode designed for restrictive or unreliable networks.

Confirm whether the VPN protects the whole device or only the browser.

Then return to the upload, call, message or page that failed.

A green connection icon is not the result.

The completed task is the result.

The upload changed the comparison

The established provider remained the better-known company.

It had more servers, more reviews and a support operation I had used before.

But on the Jio hotspot, its automatic connection never carried the client package.

The free extension opened a webpage but could not reach the application doing the real work.

The smaller backup had fewer public reviews and a shorter history.

It was also the option that recognised the network problem, connected without another round of country switching and kept the upload moving until the client confirmed receipt.

At 7:26 a.m., the London team began the launch with the correct files.

The hotel Wi-Fi had weakened. The Jio signal had changed. Both had already interrupted something that morning.

The useful VPN was the one that stopped asking me to guess which Indian server might work and simply carried the final 17 percent across the network I actually had.