The VPN That Worked at Home Failed the Moment I Started Travelling

The VPN worked beautifully until I left home.

For months, it had connected automatically whenever my laptop started. On my home fibre connection, video calls were clear, downloads were fast and the status icon rarely changed.

Then I arrived at a hotel with twenty-three minutes to sign a client contract.

The hotel Wi-Fi connected immediately, but the sign-in page would not appear. Chrome showed a blank tab. Email stayed offline. The VPN application kept trying to establish a tunnel through a network that had not yet granted me internet access.

I blamed the hotel first.

I disconnected from Wi-Fi, joined again and opened another browser. Nothing changed: no login page, no internet and a VPN trapped in a reconnection loop.

Finally, I turned the VPN off.

The hotel portal appeared at once.

I entered my room number, accepted the terms and reopened the contract. Then I switched the VPN back on.

The document loaded. I signed it and pressed Submit.

At 82%, the hotel connection dropped.

The VPN began reconnecting. The upload failed, and the signing page told me the session had expired.

At home, I had judged a VPN by speed and server coverage.

In the hotel room, neither mattered. I needed a connection that understood what travel actually looks like: captive portals, weak Wi-Fi and the possibility that a phone hotspot might have to replace the hotel network without warning.

Home had hidden the weakness

My home network was predictable.

I controlled the router, knew its password and kept it updated. It used modern Wi-Fi encryption, and my laptop usually remained on the same connection for hours. Those are the conditions official home-network guidance encourages: secure encryption, changed default credentials and current router software.

Under those conditions, my established VPN had little to recover from.

There was no hotel portal interrupting the first connection.

The public IP rarely changed.

The laptop did not move between access points, mobile data and unfamiliar Wi-Fi.

That environment made the provider feel effortless. It had years of public history, a large support operation and servers in many countries. At home, those strengths were useful. I could choose a region, keep the same route all evening and forget that the VPN was running.

Travel changed the job.

A travel VPN has to wait while a captive portal is completed, reconnect after a weak access point drops traffic and survive the moment a hotspot replaces the hotel network.

The service I trusted was excellent at remaining on one good connection.

I had never tested whether it could follow me through several bad ones.

The practical risk was interruption

Public Wi-Fi is often discussed as though every airport lounge contains someone visibly stealing passwords.

The more immediate problem is usually less dramatic. Modern websites commonly use HTTPS, but a traveller still depends on a network they do not manage, and individual applications may behave differently when that network becomes unstable.

That was my situation.

I needed one protected route for the contract, cloud storage, email and messaging. More importantly, that route had to remain usable when the underlying connection changed.

The hotel Wi-Fi was not failing for hours.

It was failing for seconds.

That was enough to destroy an authenticated upload.

Other travellers describe the same lived frustration: the device still shows Wi-Fi, yet internet or VPN access disappears repeatedly. (Reddit: r/GlInet) The interruption may be brief, but the consequence is not. A webpage can reload; an upload, call or signed session may have to start again.

My contract was now proof of that difference.

More servers gave me more restarts

I tried to repair the familiar VPN first.

The automatic server had failed, so I selected another nearby location. The connection returned, but the contract portal required a new login.

I signed again.

The upload reached 31% and stopped.

I changed protocol.

The VPN connected, but the cloud folder containing the supporting files would not sync.

I chose another city.

The browser worked. The messaging app remained silent until I restarted it.

Each choice was reasonable on its own. Together, they turned one interrupted upload into a technical project.

At home, a large server list had felt like flexibility.

While travelling, every server change created a new route, a new public address and another chance for the contract service to reset the session.

The provider did not lack tools.

It required me to operate too many of them while the client’s deadline kept moving.

With twelve minutes left, I connected the laptop to my phone’s hotspot.

The internet returned immediately.

The VPN did not follow cleanly. It stayed on Reconnecting long enough for the signing page to expire a second time.

That was the moment my comparison standard changed.

For home use, geographic choice and long, uninterrupted sessions were useful.

For travel, rapid recovery across changing networks mattered more.

The smaller app began with the situation

I had OnlydogVPN installed as a backup from an earlier trip.

It has fewer server locations than the established provider, a shorter public history and fewer independent reviews. Those limitations would matter if I needed an IP address in a particular small city.

I did not need a city.

I needed to move between hotel Wi-Fi and my phone hotspot without signing the contract for a third time.

The smaller app organised its options around situations instead of opening with a server map. I selected the preset for an unstable public network and connected while the laptop was using my phone.

Then I reopened the contract.

The page loaded.

I signed.

The upload began again.

At 44%, the phone moved from a strong 5G signal to a weaker one near the hotel window. The progress bar paused briefly, then continued.

At 67%, I deliberately returned the laptop to the hotel Wi-Fi—the transition that had broken the earlier attempts.

The upload paused.

The protected connection recovered.

The progress bar continued from 67%.

It reached 100% without returning me to the login page.

Less than a minute later, a confirmation email appeared:

Signed document received.

That completed the task.

I had spent most of the previous twenty minutes comparing servers and protocols. The connection that finally worked required only one decision: the network in front of me was unstable.

Travel rewards recovery, not a perfect speed test

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

HTTP/3 runs over QUIC, which is designed to keep a connection usable as the network path changes rather than treating every handoff as a completely new session. (RFC 9000)

The practical effect was easier to understand than the protocol name:

Hotel Wi-Fi disappeared.

The phone hotspot took over.

The protected session returned.

The upload continued.

I could not observe the hotel’s internal filtering or traffic-management rules. I could observe the difference between the two services.

The established provider was fast after it settled onto a stable network.

The smaller app recovered quickly when the network underneath it changed.

At home, that distinction might remain invisible for weeks.

During travel, it decided whether the contract arrived.

The phone did not become another setup problem

After sending the contract, I needed to join a short client call.

The laptop battery was low, so I wanted the meeting ready on my phone as a backup. With the established provider, that normally meant finding my password and confirming another device login.

The smaller service let me link the phone with a verification code.

I approved the code from the laptop, connected the phone and opened the meeting app.

The call arrived while I was walking from the room toward the lift. The phone left the hotel Wi-Fi and switched to cellular data.

The audio softened for a moment.

The call continued.

Device sharing had not signed the contract; that problem was already solved. It removed the next travel friction naturally: the backup device was ready before I needed it.

At home, every device was already configured and every password was within reach.

On the road, fewer setup steps were part of reliability.

Travel and home use are different tests

A home VPN gets the benefit of a controlled environment.

The router is familiar. The internet connection is usually stable. Devices stay in one place. Under those conditions, broad server coverage, router support and long sessions may be the features that matter most.

A travel VPN faces a different test.

It has to wait while you complete a captive portal.

It has to remain useful when hotel Wi-Fi weakens.

It has to recover when a phone hotspot replaces the access point.

It has to add a second device without turning an urgent task into account recovery.

Before travelling, I would now test those exact moments.

I would connect to a hotspot, begin a harmless upload and switch back to Wi-Fi.

I would close the laptop lid, reopen it and check whether the protected route returns before cloud applications resume.

I would confirm that the phone and laptop can both connect without searching for credentials in an airport queue.

A benchmark on home fibre cannot answer any of those questions.

My established provider still offered more locations, a longer operating history and a larger support organisation. Those strengths remained real.

But it asked me to manage servers and protocols during the moments when the network was least predictable.

The smaller service offered fewer geographic choices, but its situation-based connection completed the contract upload, survived the move between hotel Wi-Fi and mobile data and made the backup phone ready in under a minute.

At home, I wanted a VPN I could leave alone on one network. While travelling, I needed one that could keep finding its way back—and the trip was decided by the connection that finished the upload, not the one that had won the speed test in my living room.