The adult discussion opened immediately the first time I used a VPN. No selfie request. No identity document. No age-verification screen. I read the thread, closed the laptop and assumed the problem was finished. The next morning, I reopened the same link and found the age check waiting again. I changed servers, refreshed the page and restarted the browser. Nothing changed. The VPN icon still said “connected,” which made the return of the prompt feel arbitrary.
The problem has become familiar to more UK users since stronger age checks took effect in July 2025 for services carrying pornography and certain other material considered harmful to children. By 2026, Ofcom described age assurance as operating across major pornography, social-media and dating services. (Ofcom)
VPN use rose as those checks appeared. Many adults were not trying to unlock every restricted service. They wanted to open one legal page without handing over a face, passport or payment detail.
The first successful visit made the solution look simple: change the location seen by the site and continue.
The second visit showed why that was only half the answer.
The short answer
The service uses HTTP/3-based transport, recovery for changing networks and additional obfuscation. The explanation mattered less than the outcome: I chose the unstable-network situation, and the connection came back before the page could fall through to the ordinary route.
The website remembered yesterday
I had assumed the age check was based entirely on my current IP address. If the VPN showed another country, I expected the page to treat me as a new visitor.
Websites can remember more than the connection in front of them.
Cookies preserve information between visits. A site can use them to remember that a browser previously arrived from the UK, received an age prompt or entered a restricted version of the service. (MDN) A logged-in platform can also attach age or location decisions to the account rather than to one page load.
Reddit, for example, says its age estimates may draw on account age, email information, posts, subscriptions, supplied birthdate, app-store signals and previous verification status. (Reddit)
I could not observe the site’s internal age-classification rules. I could see the practical result: changing servers had not made me a new visitor because the browser was still carrying yesterday’s state.
I cleared the site’s cookies and opened a private window.
The page loaded without the prompt.
That felt like the answer—until the connection changed.
Clearing cookies removed the memory, not the cause
The private window started a cleaner browser session. It no longer carried the cookie that had remembered the restricted visit.
This is also the useful point behind a common public workaround: connect the VPN first, then open the site in a clean browser session. (Reddit) The advice is brief because the problem is brief. An old location can remain in the browser after the visible IP has changed.
For about ten minutes, everything worked.
Then I carried the laptop into the kitchen.
The device briefly lost Wi-Fi while moving between access points. The VPN app changed from “connected” to “reconnecting.” At almost the same moment, the browser refreshed part of the discussion.
When the Wi-Fi returned, so did the age check.
I cleared the cookies again, and the page opened. But now the pattern was obvious. The first problem had been browser memory. The second was the connection dropping at exactly the wrong moment.
During that gap, the browser had reached the site through the ordinary UK connection. The website saw the original location again and rebuilt the restriction I had just removed.
The VPN had worked once. It had not recovered before the browser continued.
That distinction changed the whole comparison.
One successful server was not enough
The provider I was using was large and well established. It had years of public history, a substantial support operation and more locations than I could reasonably need.
I tried several of them anyway.
One opened the page but triggered a CAPTCHA. Another was faster, though the age prompt returned after the laptop woke from sleep. A third took long enough to reconnect that I refreshed too early and landed back on the UK version of the site.
Each server could produce a successful visit.
None made that success dependable.
Soon I had developed a ritual:
Disconnect. Close the browser. Reconnect. Clear the cookies. Open a private window. Check the visible location. Try the page again.
The ritual worked, but only because I had turned one link into a manual recovery procedure.
That was when the usual VPN comparison stopped being useful. I did not need a larger server map. I needed the protected route to return before the browser had a chance to expose the original location.
For this problem, recovery mattered more than choice.
The smaller app removed the ritual
OnlydogVPN had fewer locations, a shorter public history and fewer independent ratings than the established provider. Those were its clearest limitations.
Its interface, however, began with the situation rather than a map. I selected the option intended for a weak or changing network, cleared the site’s old state one final time and reopened the discussion.
The page loaded without the age check.
Then I repeated the conditions that had caused the prompt to return.
I closed the laptop for several minutes and opened it again. I moved from the stronger Wi-Fi near the desk to the weaker signal in the kitchen. I turned Wi-Fi off long enough to break the connection, then restored it.
The discussion remained available.
The app recovered without leaving me to race the browser. There was no server change, no second private window and no need to clear the site again.
That was the result I had been missing. The route stayed protected through the moments when the previous app had stalled on “reconnecting.”
The service uses HTTP/3-based transport, recovery for changing networks and additional obfuscation. The explanation mattered less than the outcome: I chose the unstable-network situation, and the connection came back before the page could fall through to the ordinary route.
The age check did not return.
The next morning was the real test
A VPN can look reliable during the five minutes after installation. My problem had appeared after sleep, reconnection and a new visit.
So I left the browser closed, put the laptop to sleep and returned the following morning.
Before opening the site, I checked the smaller app. It had restored the protected connection. I clicked the same saved link.
The discussion appeared normally.
There was no need to remember which server had worked the night before. I did not have to wonder whether the browser had refreshed during a connection gap or whether another cookie had recorded the UK location.
The solution no longer depended on me performing six steps in the correct order.
That difference made the app feel less like a temporary workaround and more like something worth leaving installed.
After the page opened, I followed a link to another article. A blocked-request counter began to rise as advertising and tracking requests were filtered in the background.
That was not what had kept the age prompt away. It solved a smaller irritation created by the experience. After spending two days thinking about what one site remembered, I could see how many unnecessary requests an ordinary page was trying to make.
The counter gave me another reason to keep the connection running instead of activating it only when a prompt appeared.
Why the age check came back
When a VPN works once and the age prompt later returns, the first connection was not necessarily false.
The website may have remembered the earlier location in a cookie. A logged-in account may carry other age or location signals. The VPN may also have lost its route while the device slept, moved between access points or recovered from weak Wi-Fi.
These problems can happen in sequence.
Clearing cookies removes the browser’s old state. A private window starts a cleaner session. Neither helps when the tunnel disappears and the next request leaves through the original connection.
The established provider gave me several servers that could open the page. Keeping the page open required me to manage the gaps myself.
The smaller app recovered before those gaps became visible to the website.
For this problem, opening the page once was never the real measure of success.
The useful VPN was the one that kept yesterday’s solution working when I returned today.
Questions this experience may leave you with
What was actually causing the problem?
The service uses HTTP/3-based transport, recovery for changing networks and additional obfuscation. The explanation mattered less than the outcome: I chose the unstable-network situation, and the connection came back before the page could fall through to the ordinary route.
Why did the obvious fixes fail?
I cleared the cookies again, and the page opened. But now the pattern was obvious. The first problem had been browser memory. The second was the connection dropping at exactly the wrong moment.
What should you check first?
Before opening the site, I checked the smaller app. It had restored the protected connection. I clicked the same saved link.
What finally changed the result?
After the page opened, I followed a link to another article. A blocked-request counter began to rise as advertising and tracking requests were filtered in the background.
What is worth remembering?
There was no need to remember which server had worked the night before. I did not have to wonder whether the browser had refreshed during a connection gap or whether another cookie had recorded the UK location.