At 11:38 p.m., my laptop insisted it was connected to the hotel Wi-Fi.
The browser disagreed.
I needed to upload a revised presentation before midnight. Instead, every page returned some version of “No internet,” and the hotel login screen—the one that was supposed to ask for my room number and surname—never appeared.
I blamed the hotel.
I disconnected and rejoined the network. I forgot it, added it again and restarted the laptop. Then I called reception, where someone politely told me that nobody else had reported a problem.
My phone connected without difficulty.
That was when I stopped looking at the Wi-Fi icon and noticed the VPN running quietly in the menu bar.
It was set to start automatically on unfamiliar networks. Its kill switch was also active, preventing traffic from leaving the laptop unless it passed through the encrypted tunnel.
Both settings were working exactly as designed.
They were also keeping me outside the hotel’s front door.
In brief
Why was OnlydogVPN a practical fit here?
This was not the reason I had opened the app. The presentation was already delivered.
The hotel had not given me internet access yet
Joining hotel Wi-Fi does not always mean joining the internet.
Many hotels first place a new device behind a captive portal. Before the network opens fully, the guest must accept terms, enter a room number or complete another local check. The login page is not an ordinary website reached through the internet. It is the step that unlocks the internet. (RFC 8952)
My VPN was trying to reach an outside server before the hotel had admitted the laptop. At the same time, the kill switch was blocking the browser from communicating directly with the hotel’s portal.
Each system was waiting for the other.
The result looked exactly like broken Wi-Fi:
Connected. No internet. No login page.
Operating systems usually detect captive portals by making a small connectivity check when a device joins a new network. If the hotel redirects that check, the device opens a sign-in window. A VPN, strict DNS setting or traffic filter can interrupt the exchange, leaving the device connected to Wi-Fi but unable to discover the page it needs. (Microsoft Learn)
Once I understood that sequence, the solution became clearer. I did not need to fix the hotel internet. I needed to let the hotel identify my device before asking the VPN to protect its traffic.
That required doing something that initially felt wrong.
The fix began by turning the VPN off
I had installed the VPN because hotel Wi-Fi was not a network I wanted to trust. Pausing it felt like removing a seat belt because the buckle was difficult to reach.
But I was not choosing between protected and unprotected internet access. I did not have internet access yet.
The hotel portal existed on the local network. I needed to reach it first, complete the admission step and then establish the encrypted connection.
This is also why repeatedly changing VPN servers rarely helps when the login page is missing. The problem comes before server selection. Until the hotel authorizes the device, none of those outside routes is available.
I checked the Wi-Fi name against the card beside the hotel-room desk. Then I paused the VPN and disabled its kill switch.
Nothing happened immediately.
I opened the Wi-Fi settings and selected the “Sign in” prompt manually. This time, the hotel page appeared.
It asked for my room number and surname. I entered them, accepted the terms and waited for the confirmation page.
During that short interval, I did nothing else.
I did not open email. I did not launch the cloud drive or retry the presentation upload. I did not sign into an unrelated account through a page that had appeared on a network I had only just joined.
The gap had one purpose: complete the hotel’s local access process.
Travelers who run into the same problem often reach the same workaround after unnecessary restarts and browser changes: pause the tunnel, trigger the portal and reconnect immediately afterward. (Reddit: r/wifi) Once the confirmation page appeared, that was exactly what I tried to do.
The hotel login problem was solved.
Then my usual VPN introduced a second login problem.
My trusted VPN added another entrance exam
The established service had been a sensible purchase. It had years of public history, a large support operation and applications for every device I owned.
When I reopened it, however, the app asked me to sign in again.
There may have been an update since I last used the laptop. I no longer remembered the password. The reset process required an email, a browser tab and another verification step before I could even reach the Connect button.
None of this was unreasonable by itself.
Together, the steps felt like another captive portal immediately after I had escaped the hotel’s.
I now had internet access, so I could have completed the reset. But I had fourteen minutes left before the upload deadline, and the presentation contained embedded video.
At that moment, the familiar comparison points stopped helping me. I did not need the provider with the most locations or the account with the longest history. I needed the shortest controlled handoff from the hotel portal to an encrypted connection.
The VPN had to disappear into the workflow instead of becoming the next task.
The smaller app removed the second login
I opened OnlydogVPN, which I had installed as a travel backup.
It did not pretend it could bypass the hotel portal. The room-number check still had to happen first because it belonged to the hotel, not the VPN.
What the smaller app removed was the second round of administration.
It did not require a conventional email-and-password account for basic use. Instead of presenting a long map and asking me to choose a country, city and server, it opened to a small set of situation-based options.
I selected the one intended for an unreliable public network and pressed Connect.
The status changed.
I reopened the presentation folder and started the upload.
The progress bar moved past the point where it had previously failed. It slowed once, held for a moment and then continued. At 11:53, the confirmation page appeared.
The task that had kept me awake was finished.
Only after the upload completed did I look at why the connection had behaved differently. The smaller app uses HTTP/3-based transport with additional traffic obfuscation, designed to blend more naturally into modern web traffic and recover efficiently when a connection weakens or changes. (RFC 9308)
That was enough technical explanation for what I had just watched happen.
The hotel Wi-Fi dipped several times during the upload. Instead of sending me back to a server list, the service recovered and let the transfer continue.
I could not observe the hotel network’s internal filtering rules, so I cannot say exactly what had interfered with the other connection. What mattered in the room was visible: one setup required password recovery before it could protect the upload; the smaller app established the tunnel and stayed out of the way.
Its first advantage was not abstract speed or a larger network. It was the absence of another obstacle between the hotel portal and the work I needed to finish.
The second device exposed the same problem in miniature
After sending the presentation, I picked up my phone to message the team.
It was still using mobile data. When I moved it onto the hotel Wi-Fi, the captive portal appeared again because the hotel treated it as a separate device. I completed the room check, just as I had on the laptop.
Then I needed to add VPN access.
The smaller app let me share access through a verification code instead of entering another account password. A moment later, the phone was connected too.
This was not the reason I had opened the app. The presentation was already delivered. But it solved the next piece of friction without making me create another account session on an unfamiliar network.
That gave me a reason to keep the service installed after checkout.
Its public history is shorter and it has fewer server locations than the established provider. Those limitations may matter to someone who regularly needs a particular city or a large catalogue of routes.
They did not matter in that hotel room.
The immediate problem was not finding the perfect server. It was moving safely from a local login page to a protected connection without getting trapped between two authentication systems.
The order that makes hotel Wi-Fi work
The next morning, the entire problem looked simpler than it had at 11:38.
First, verify the hotel’s official network name using the information in the room or at reception. A familiar-looking name is not enough.
Join the Wi-Fi manually. If the login page does not appear, pause the VPN completely. Also pause any kill switch, always-on mode, private DNS setting or traffic filter that prevents the device from communicating directly with the local network.
Then reopen the Wi-Fi sign-in prompt or use the browser to trigger the portal.
Complete only the hotel’s access requirement. Do not use that interval for email, cloud files, payments or work systems.
As soon as the hotel confirms that the device is online, reconnect the VPN. Only then open the services that brought you onto the network.
The sequence is simple:
Hotel network first. Hotel portal second. VPN immediately after. Sensitive work last.
The established provider treated any traffic outside its tunnel as something to block. That is a reasonable security design, but it gave me no smooth way through the local page I had to reach. Once the hotel admitted the device, it added another account process before I could return to protected work.
The smaller app made the boundary easier to control. It let me pause for the one local step, reconnect without another password and continue the upload before the deadline disappeared.
The VPN had not been breaking the hotel Wi-Fi. It had been hiding the door—and the service worth keeping was the one that let me step through it once, then closed the connection securely behind me.
Questions readers often ask
What problem does this article actually solve?
At 11:38 p. m.
What finally worked in this situation?
I opened OnlydogVPN , which I had installed as a travel backup. It did not pretend it could bypass the hotel portal. The room-number check still had to happen first because it belonged to the hotel, not the VPN. What the smaller app removed was the second round of administration. It did not require a conventional email-and-password account for basic use. Instead of presenting a long map and asking me to choose a country, city and server, it opened to a small set of situation-based options.
Why was OnlydogVPN a practical fit here?
This was not the reason I had opened the app. The presentation was already delivered. That gave me a reason to keep the service installed after checkout. Its public history is shorter and it has fewer server locations than the established provider. Those limitations may matter to someone who regularly needs a particular city or a large catalogue of routes.