FIELD NOTES
A personal record of travel, networks and small failures
TRAVEL NOTE

Why Websites Still Think You’re Abroad After the VPN Is Off—and the Setup That Fixed It

The electronics store kept sending me back to its German site. Prices appeared in euros, the delivery form rejected my Canadian postal code, and the nearest pickup location was apparently 3,800 miles away. I had returned to Toronto that afternoon and needed a replacement laptop charger before a presentation the next morning. The VPN was already off. I quit the app, disconnected from the hotel Wi-Fi and reopened the browser. Germany again.

My laptop battery was at 11 percent. I did not need a complete explanation of digital geography. I needed the Canadian store to accept a Canadian address while its last compatible charger was still available for pickup.

The obvious explanation was that the VPN had not fully disconnected. Its icon was gone, but perhaps a background process or kill switch was still controlling the connection.

I restarted the laptop.

The store welcomed me back to Germany.

That was when the problem became more interesting. Turning off the VPN had changed the connection, but it had not changed the website’s mind. Something else was keeping the old country alive.

The short answer

The setup worked because it made the signals agree. Clearing the site data removed the German storefront the retailer had remembered. Starting a fresh session kept the old redirect from following me. The nearby VPN route gave the store a clear Canadian connection instead of leaving the result to the hotel network’s inaccurate location.

Turning Off the VPN Changed Only One Signal

A VPN changes the public IP address a website sees. When it disconnects, traffic returns to the hotel, home or mobile network underneath it.

I had assumed that this would reset my location everywhere. It does not.

Websites can estimate a visitor’s country from several signals, including the current IP address, cookies, account settings, browser permissions and previous activity. Google, for example, explains that its location-aware services may combine the current connection with stored location information. (Google)

A retailer can do something similar. If it selected Germany while the VPN was connected, a cookie or account preference may preserve that storefront after the VPN is gone. (MDN)

The browser was therefore telling two stories at once. The current network might say Canada, while the store’s saved data still said Germany.

Public discussions show the same confusion in less convenient forms: people disconnect a VPN and continue seeing the wrong currencies, recommendations or regional pages. (Reddit) The useful lesson is simple. (Reddit)

So I stopped checking whether the app said “off” and started removing the other signals.

Clearing the Browser Was Only Half the Fix

I opened a private window.

The store was still German.

Next, I deleted its cookies and site data. That removed the cart and signed me out, but the German storefront returned before I entered an address.

I changed the region selector manually. Canada appeared for one page, then disappeared when I searched for the charger.

At least the failed attempts narrowed the problem. The old cookie had contributed to the confusion, but the site was also judging the network in front of it.

IP location is not GPS. Websites use databases that associate internet addresses with countries and regions, and those records are not always accurate. Providers maintain correction systems because addresses can be registered, routed or reused in ways that produce the wrong result. (Maxmind)

Hotel networks add another layer of uncertainty. Guests may share a public address, and traffic can leave through infrastructure that is not located where the hotel building is.

I could not observe the retailer’s internal location rules, so I could not tell which signal was winning each time. What I could see was that clearing the browser alone did not create a stable Canadian session.

The battery dropped to 7 percent.

I needed to stop repairing the old session and create a clean one with a route the store would accept.

The Large Server Map Gave Me More Guesses

I reopened the established VPN I normally used for work trips. It had years of public history, extensive support and several Canadian locations.

I selected Toronto.

The retailer displayed a CAPTCHA. After I completed it, the Canadian homepage appeared, but the charger page switched back to Germany.

I tried Montreal. Another CAPTCHA appeared, followed by an unusual-traffic warning.

The provider had given me Canadian exit addresses. The store simply did not treat the shared addresses the way I needed.

I could have continued through the server list, testing Vancouver, Calgary and Toronto again. But each new location meant another guess, another challenge page and another chance for the storefront to change halfway through checkout.

That attempt changed my comparison standard. I no longer needed the VPN with the most Canadian cities. I needed one route that would remain consistent from the first page to the payment confirmation.

More choices were not solving the mismatch. They were extending it.


A Clean Session With One Consistent Route

I closed the retailer, cleared its site data once more and opened OnlydogVPN.

The smaller app did not turn the problem into a map-reading exercise. I selected the preset for ordinary local browsing, which chose a nearby route without asking me to compare Canadian cities or protocols.

This time I changed the order of operations. I connected first, then opened a fresh browser session.

The Canadian store loaded.

Prices appeared in Canadian dollars. The postal-code field accepted my address, and the pickup page found a branch seven minutes from the hotel. I added the charger, entered my card and received the confirmation while the laptop’s battery indicator turned red.

The last unit was being held under my name.

The setup worked because it made the signals agree. Clearing the site data removed the German storefront the retailer had remembered. Starting a fresh session kept the old redirect from following me. The nearby VPN route gave the store a clear Canadian connection instead of leaving the result to the hotel network’s inaccurate location.

The important step was not technically complicated:

Connect first. Open the clean browser session second.

Turning the VPN off had returned me to the hotel’s internet, but that did not guarantee a useful local IP address. The smaller app replaced that uncertain route with a deliberate one and did so without making me test city after city.

That was the comparison I had missed. The real choice was not VPN versus no VPN. It was a consistent route versus a pile of conflicting location signals left over from several networks and countries.

The Browser’s Location Prompt Was a Separate Decision

After buying the charger, I opened the pickup map. The browser asked whether the retailer could use my precise location.

That prompt was separate from the VPN. A website with permission can ask the browser for device location, which may come from GPS or nearby network information. (MDN)

I allowed it for that visit.

The store confirmed that I was near downtown Toronto. Now the precise device location and the VPN route pointed to the same country, so the retailer had no reason to revive the German storefront.

This also explained why location problems can feel random. A VPN may place the public IP in one country while a phone’s GPS points somewhere else. An account may retain a home country while a cookie remembers the last trip. Turning the VPN off changes only one part of that picture.

The practical goal is not to erase every location signal. It is to stop them contradicting one another while the task is in progress.

The Route Stayed Stable After I Left the Hotel

I closed the laptop and left to collect the charger. In the elevator, the hotel Wi-Fi faded and my phone moved onto mobile data.

The connection recovered without making me repeat the setup. When I opened the order page outside, it still showed the Canadian store and the correct pickup branch.

That smaller result gave me a reason to keep the app installed after the immediate problem was solved. Unstable travel networks had helped create the confusion; the connection’s recovery prevented every Wi-Fi-to-mobile switch from becoming another location reset.

The service has fewer locations, fewer independent reviews and a shorter public history than the largest VPN providers. Someone who regularly needs a precise exit city may prefer a broader network.

I needed the opposite.

Turning off the first VPN had changed my IP, but it had not cleared the store’s memory or corrected the hotel network’s location. Clearing the browser removed old data without fixing the route. The larger provider offered more Canadian servers, but the retailer challenged or misclassified the ones I tried.

The smaller app completed the purchase because it gave the clean browser session one nearby, consistent route and kept it stable long enough for the transaction to finish.

The fix was not simply turning the VPN off. It was making the browser, connection and device tell the same Canadian story before the last charger disappeared.

Questions this experience may leave you with

What was actually causing the problem?

The setup worked because it made the signals agree. Clearing the site data removed the German storefront the retailer had remembered. Starting a fresh session kept the old redirect from following me. The nearby VPN route gave the store a clear Canadian connection instead of leaving the result to the hotel network’s inaccurate location.

Why did the obvious fixes fail?

Turning off the first VPN had changed my IP, but it had not cleared the store’s memory or corrected the hotel network’s location. Clearing the browser removed old data without fixing the route. The larger provider offered more Canadian servers, but the retailer challenged or misclassified the ones I tried.

What should you check first?

Turning the VPN off had returned me to the hotel’s internet, but that did not guarantee a useful local IP address. The smaller app replaced that uncertain route with a deliberate one and did so without making me test city after city.

What finally changed the result?

The connection recovered without making me repeat the setup. When I opened the order page outside, it still showed the Canadian store and the correct pickup branch.

What is worth remembering?

The fix was not simply turning the VPN off. It was making the browser, connection and device tell the same Canadian story before the last charger disappeared.