The hotel Wi-Fi showed full signal, but my laptop insisted there was no internet. I needed to approve a contract and join a client call within twenty minutes, so I blamed the network, forgot it, rejoined and restarted the browser. The same blank page returned.
My phone connected to the same Wi-Fi and immediately displayed a page asking for my surname and room number.
The laptop did not.
That was when I noticed the VPN icon. It had connected automatically before the hotel had finished giving me internet access.
I turned the VPN off. The hotel login page appeared within seconds.
The first lesson was simple: on hotel Wi-Fi, the order matters.
But reaching the login page did not mean the connection was ready for work.
In brief
Why was OnlydogVPN a practical fit here?
I restarted the contract upload. It passed 34 percent, reached 50 and then completed.
The Wi-Fi symbol appeared before the internet did
Hotel networks commonly use a captive portal. Your device joins the Wi-Fi first, but normal internet access remains blocked until you open the hotel’s page, accept its terms or enter details such as a surname and room number. (RFC 8952)
A VPN tries to contact its server as soon as it starts. The captive portal is still waiting for the browser to complete the hotel login. If auto-connect launches the VPN first—or the kill switch blocks all traffic outside the tunnel—the browser cannot reach the page that unlocks the network.
The hotel is waiting for the browser. The VPN is waiting for internet access. Neither can move.
That explained the blank page and gave me the correct starting sequence:
Join the hotel Wi-Fi. Complete the hotel login. Confirm that the internet works. Then connect the VPN.
Established providers give similar captive-portal instructions: pause auto-connect and the kill switch, complete the hotel login, then restore protection. (NordVPN Support, instructions for completing a captive-portal)
I followed that order with the major VPN already installed on my laptop.
The portal accepted my room details. I opened an ordinary website to confirm that the connection worked, re-enabled the kill switch and started the VPN.
This time it connected.
For a few minutes, the problem appeared solved.
Then the contract upload stopped.
Correct order, wrong tunnel
I had been treating the hotel login and the VPN connection as one failure. They were actually two separate tests.
The first was whether the captive portal could authorise the laptop.
The second was whether the VPN could remain useful once access had been granted.
The established provider had a long public history, a large support operation and servers in many countries. I chose a nearby location because it seemed likely to provide the shortest route.
The contract upload reached 34 percent and paused.
I changed servers. It resumed briefly, then stopped again.
The video-call preview moved between clear and badly pixelated. Whenever the hotel connection weakened, the VPN switched to Reconnecting. When the tunnel returned, the upload did not always return with it.
I carried the laptop from the desk to the chair near the room door, where the Wi-Fi signal was stronger. The call preview froze again.
The hotel portal had not reappeared. Re-entering my room details would solve nothing. I had completed the connection order correctly; the VPN was now struggling with the network itself.
Hotel Wi-Fi rarely behaves like a stable home connection. Signal quality changes across a room, and moving through the building may shift a device between access points. The Wi-Fi icon can remain visible even while the usable route disappears for a moment.
Travelers describe the same practical annoyance: disable the VPN to open the portal, reconnect it afterward, then repeat part of the process when the hotel network changes or asks for authorisation again. (Reddit discussion)
That was enough evidence for the point I could already see on the screen. The real problem was no longer opening the portal. It was keeping a working tunnel afterward.
The hotspot removed the portal—and the usable signal
With ten minutes left before the call, I switched the laptop to my phone’s hotspot.
The contract began uploading immediately.
Then the phone dropped from 5G to a weak indoor signal. The estimated completion time jumped from two minutes to seventeen, and the meeting preview became worse than it had been on the hotel network.
The hotspot had removed the captive portal, but it had also removed the hotel’s stronger connection.
Joining the meeting without a VPN would have been faster. Most of the services I needed already used encrypted web connections, but the laptop also had email, cloud storage and a client workspace running in the background. I did not want to decide, application by application, which traffic could use the hotel network directly.
The hotel Wi-Fi had enough bandwidth. The established provider had enough servers. What I needed was a VPN that could start cleanly after the portal and recover when the hotel connection changed.
That was a much more useful requirement than simply looking for “a VPN for travel.”
The smaller app started at the right moment
I returned to the hotel Wi-Fi with every VPN disconnected.
The hotel still recognised the laptop, so the portal did not appear again. I opened two ordinary websites to confirm that internet access was active.
Only then did I start OnlydogVPN.
Instead of asking me to choose among rows of countries and protocols, the app offered a preset for a weak or changing network. I selected it and connected.
The tunnel came up.
I restarted the contract upload. It passed 34 percent, reached 50 and then completed. I opened the meeting application, joined with audio and sent the signed document through the client workspace.
The original task was finished with the VPN still active.
The service uses an HTTP/3-based transport with additional traffic obfuscation. Put simply, it gave the app a different way to carry the connection through the hotel network instead of repeatedly retrying the same conventional route. (RFC 9114)
I could not observe the hotel’s internal filtering and traffic-management rules. I could observe the result: the established client repeatedly lost its useful connection, while the smaller app completed the upload and held the meeting.
That was all the technical comparison the situation required.
The walk to the lobby became the real test
Halfway through the call, housekeeping knocked. I carried the laptop downstairs and continued from a quiet corner of the lobby.
The Wi-Fi disappeared for a moment near the lift.
The meeting paused, then returned.
I did not reopen the VPN app, choose another server or repeat the hotel login. The connection recovered while I was still listening to the client.
That transition mattered more than the initial connection.
A hotel network is not one fixed signal. It is a chain of access points, brief interruptions and changing conditions hidden behind the same Wi-Fi name. A VPN that works only while the laptop stays on one desk has solved the easiest part of the problem.
The established provider offered more locations and a longer public history. The smaller service has fewer locations and fewer independent reviews, which remains its clearest limitation.
But the immediate test was not about which company had the larger map.
It was about which service could connect after the hotel portal, carry the work and recover as the laptop moved through the building.
The smaller app had already answered that question before I reached the lobby.
The correct sequence has three stages
Before this trip, I treated “turn on a VPN on public Wi-Fi” as a complete instruction.
On a hotel network, it is missing an important step.
First, join the hotel Wi-Fi.
At this point, the Wi-Fi symbol may appear even though the hotel has not granted normal internet access.
Second, complete the captive portal.
Temporarily pause the VPN, auto-connect or kill switch if they prevent the page from opening. Enter the required hotel details, accept the terms and confirm that an ordinary website loads.
Use this short unprotected window only for the portal. Do not start checking email, opening financial accounts or uploading work files.
Third, connect the VPN before beginning the real session.
Once the tunnel is active, open email, cloud storage, company systems, messaging and other applications. If the hotel later asks for authorisation again, pause the VPN only long enough to complete the portal, then reconnect before returning to work.
This order avoids the captive-portal deadlock without turning the rest of the hotel session into unprotected browsing.
It also explains why aggressive auto-connect can be unhelpful in hotels. Starting a VPN at the earliest possible second sounds safer, but starting it before the hotel grants internet access can prevent both the portal and the tunnel from working.
The useful VPN is not merely the one that starts first. It is the one that connects at the right moment and remains useful after that.
I had solved only the first failure
The hotel network had genuine weaknesses. Its signal changed across the building, and its portal placed an extra step between joining Wi-Fi and reaching the internet.
But the first failure came from my own sequence. The VPN had started before the hotel could authorise the laptop.
Once I corrected that, the difference between the two services became clear.
The established provider connected after the portal but repeatedly lost its useful route as the hotel network changed. The phone hotspot avoided the portal but lacked enough indoor signal. The smaller app connected after authorisation, completed the client work and recovered as I moved from the room to the lobby.
The right order was hotel login first and VPN immediately afterward.
The right VPN was the one that made me perform that order only once.
Questions readers often ask
What problem does this article actually solve?
The hotel Wi-Fi showed full signal, but my laptop insisted there was no internet. I needed to approve a contract and join a client call within twenty minutes, so I blamed the network, forgot it, rejoined and restarted the browser.
What finally worked in this situation?
Only then did I start OnlydogVPN . Instead of asking me to choose among rows of countries and protocols, the app offered a preset for a weak or changing network. I selected it and connected. The tunnel came up. I restarted the contract upload. It passed 34 percent, reached 50 and then completed.
Why was OnlydogVPN a practical fit here?
I restarted the contract upload. It passed 34 percent, reached 50 and then completed. The original task was finished with the VPN still active. The service uses an HTTP/3-based transport with additional traffic obfuscation. Put simply, it gave the app a different way to carry the connection through the hotel network instead of repeatedly retrying the same conventional route.