VPN Not Working in Indonesia? The Hotel Wi-Fi Was Blocking the Tunnel, Not the Internet

The client upload stopped the moment I switched on my VPN. With the VPN off, the hotel Wi-Fi opened email, news sites and the project dashboard. With it on, every tab stalled behind a spinning circle. I was in Ubud, trying to send a 640-megabyte product video before a London agency’s morning review. I blamed the hotel router, restarted the laptop and reconnected through the Wi-Fi login page. Ordinary browsing returned. The VPN killed it again.

The agency had already delayed the review once.

My job was simple: upload the final video, open the private review page and stay online long enough to answer questions about the edits.

The meeting began in thirty-four minutes.

The hotel connection was not especially fast, but it was usable. Before I enabled the VPN, the upload estimate showed twenty-one minutes.

Then the internet appeared to disappear.

That was the confusing part.

The Wi-Fi worked.

The VPN worked on my phone’s mobile data.

They simply did not work together.

Indonesia is not one uniform network

Indonesia requires internet providers to restrict access to prohibited online content. Its official TRUST+Positif framework supplies addresses for blocking by internet services and providers. (Indonesia Ministry of Communication and Informatics)

How that filtering appears can vary from one network to another.

OONI measurements have documented differences between Indonesian providers, including widespread DNS interference. (Open Observatory of Network Interference) A site that opens on a café connection may therefore fail on a hotel network or mobile carrier.

I had already noticed that inconsistency during the trip.

Reddit opened through one coworking space but not through my Indonesian SIM.

A design-reference site worked in Jakarta and failed on the Ubud hotel Wi-Fi.

Those differences explained why I wanted a VPN in the first place.

They did not explain why enabling mine stopped every website, including the ones the hotel normally allowed.

So I stopped testing individual pages and focused on the connection itself.

The established provider worked everywhere except the hotel

I had used the same major VPN provider for years.

It had a long public history, extensive support and more locations than I had ever needed. It worked at home, in airports and through my phone’s Indonesian mobile connection.

I selected Singapore, the nearest familiar option.

The app remained on Connecting.

After thirty seconds, the laptop still showed the hotel Wi-Fi symbol, but no traffic moved.

I disconnected the VPN.

Email loaded immediately.

I tried Australia.

The same thing happened.

A Japanese route connected briefly, then the browser reported that the network had changed.

The provider offered several connection modes, so I switched from its default to WireGuard.

The failure became immediate. As soon as the tunnel started, the hotel connection stopped carrying traffic.

OpenVPN did not help either. It tried to connect for nearly a minute and then timed out.

At that point, changing countries was no longer a meaningful test.

Every route was attempting to cross the same hotel network in a form it would not carry.

One traveler described almost the same symptom on Indonesian hotel Wi-Fi: ordinary internet access worked, but enabling WireGuard cut the connection. (Reddit) My screen was showing the same practical split.

The hotel allowed browsing.

It did not allow my usual VPN tunnel to remain usable.

Mobile data proved the account was fine

I turned off the hotel Wi-Fi and connected the laptop to my phone’s hotspot.

The established VPN connected to Singapore immediately.

The project dashboard opened.

The upload began.

That removed several possible explanations at once.

My subscription had not expired.

The app was not broken.

The laptop could create a VPN connection.

The failure belonged to the hotel network.

Unfortunately, the mobile signal inside the room was weak.

The upload reached 11 percent, paused and changed its estimate to more than two hours. The signal improved near the balcony, but rain was blowing across the table.

I now had two incomplete options.

The hotel Wi-Fi was fast enough but rejected the tunnel.

The hotspot accepted the tunnel but could not carry the file reliably.

The review was twenty-three minutes away.

The free extension protected the wrong part of the task

I installed a free browser extension offering a nearby route.

It connected quickly.

The blocked design-reference site opened again. So did the browser version of the client dashboard.

For a moment, that looked sufficient.

Then I returned to the desktop upload application.

It was still using the direct hotel connection.

The extension covered one browser, not the file-transfer tool, meeting application or background sync process holding the latest project notes.

I could have moved the upload into a browser tab, but a previous interruption had already forced that method to restart from zero.

The extension restored one page.

The task required the whole laptop.

I removed it before another partial solution consumed the remaining time.

By then, the requirement was clear: I needed a full-device VPN that the hotel network would actually carry.

The backup treated the hotel as the problem

I had installed OnlydogVPN^↗ before leaving home but had not made it my default.

The established provider had more reviews, more locations and a much longer public record. The smaller app’s shorter history was why I had kept it as a backup.

But another server list was not useful now.

The country was not the obstacle.

The hotel network was.

The backup organised its options around situations, so I selected the preset for a restrictive or unreliable public network.

The connection established while the laptop remained on the hotel Wi-Fi.

Email still loaded.

The client dashboard opened.

Then the desktop upload application connected and found the unfinished file.

I restarted the transfer.

The progress passed 10 percent.

Then 25.

Then 50.

This time, the hotel internet did not vanish when the VPN became active.

At 82 percent, I opened the meeting link in a second window. The waiting room loaded without disturbing the upload.

The file reached 100 percent with six minutes left.

The client portal generated a preview.

I checked the final frame and sent the review link to the agency producer.

The message changed from Sending to Delivered.

That completed the task that had caused me to search for a fix.

The route blended into traffic the hotel already carried

The service uses an HTTP/3-based connection with additional traffic obfuscation.

The explanation did not need to be longer than the result.

The established provider worked over mobile data but failed whenever it crossed the hotel Wi-Fi.

The browser extension opened one restricted page but left the upload and meeting applications outside its connection.

The backup kept the whole laptop online and carried the file to completion.

I could not observe the hotel network’s internal filtering rules. I could compare what happened when each connection started.

For this problem, traffic the local network would carry mattered more than a larger server list.

The meeting created a second test

The agency joined the call two minutes after the upload finished.

The producer opened the video and shared her screen.

The first scene played smoothly.

Then the hotel lights flickered.

The Wi-Fi disappeared.

For a second, the meeting froze on a close-up of the product label.

The laptop switched to my phone’s hotspot.

The VPN recovered on the new network.

The meeting resumed without removing me from the room, and the review page stayed open on the same frame.

“Still with us?” the producer asked.

“Yes.”

We continued.

The hotspot was slower than the hotel connection, but it now had to carry only the call. The large upload was already complete.

That recovery solved the smaller problem that followed the first one.

The obfuscated route had allowed the hotel Wi-Fi to carry the work.

The network recovery kept the review alive when the Wi-Fi disappeared entirely.

Changing DNS would have fixed a different failure

Earlier in the trip, changing DNS had helped me reach a site redirected by another Indonesian network.

That can work when DNS blocking is the obstacle.

It would not have repaired the hotel connection.

The websites already opened when the VPN was off.

The failure began only when the VPN tried to establish its tunnel.

That distinction saved time once I recognised it.

When one site fails but the VPN remains connected, the issue may involve that destination or the network’s DNS filtering.

When the entire internet stops the moment a VPN activates, changing browsers or clearing cookies is unlikely to help.

My problem existed before the client page could even receive a request.

The tunnel itself had to get through first.

The same provider can behave differently across Indonesia

Before the trip, I had spoken about “the internet in Indonesia” as though it were a single environment.

The week in front of me was much less tidy.

The Jakarta airport Wi-Fi carried my established VPN.

My Indonesian SIM carried it too, although the mobile signal varied.

One coworking space allowed Reddit directly.

The Ubud hotel blocked some sites and made my familiar VPN modes unusable.

The solution therefore was not simply to choose a closer country.

Distance had not stopped the connection.

The shape of the connection had.

That was why the established provider could work perfectly over mobile data at breakfast and fail completely inside the hotel an hour later.

It was also why the smaller backup succeeded without asking me to search through more countries.

It addressed the network I was actually using.

The delivered review link settled the comparison

The agency approved the video after two small caption changes.

I made them during the call and uploaded a smaller replacement file. The connection remained active until the producer confirmed that the final version had reached the campaign folder.

The established provider remained the better-known company. It had more locations, more ratings and years of public history.

The free extension connected quickly and opened a page restricted by the hotel.

Neither carried the complete work session on that network.

The smaller backup had fewer locations and a shorter public record. It was also the option that connected through the hotel Wi-Fi, finished the large upload and kept the meeting alive when the laptop moved to mobile data.

My VPN had not failed because Indonesia was too far from the right server.

It had failed because the hotel recognised the tunnel before my work could pass through it.

The useful connection was the one that reached the client before the hotel network realised there was anything unusual to refuse.