A "this content isn't available in your region" message and a Google page asking me to click every square with a bus in it look like two completely different problems, but for anyone doing remote work through a VPN, they trace back to the same thing: a connection that doesn't look enough like one ordinary person. I've been doing client work from wherever the wifi holds up for a while now, and the captcha problem is the one that actually gets in the way of getting paid — you can work around a blocked show, but you can't work around a search engine that won't let you past a picture grid.
Quick disclosure before I go any further: this page includes affiliate links, and if you sign up for a VPN through one of them, I earn a commission at no extra cost to you. The only services I mention are ones I've actually paid for and used while working out of a shifting lineup of flats and coworking spaces, including NordVPN, which is the one I reach for most often. You can find my full transparency policy elsewhere on this site.
Why Does Google Treat Remote Workers on a VPN Like a Bot Network?
Google doesn't see a person when you connect through a VPN — it sees an IP address, and that address is usually shared by hundreds of other users at the same time. Load a search results page from a hotel in one city and a coworking desk in another, both through the same server, and to Google's traffic-monitoring systems that looks less like international travel and more like a single account logging in from everywhere at once.
That reputation problem is separate from the more familiar issue of a show or an app deciding you're in the wrong country — geo-blocking checks where you appear to be, while a captcha is judging how suspicious your connection's recent behaviour looks, which is a different fight entirely.
The Coworking Wifi Problem Nobody Mentions
Second Home Lisboa, the coworking space in Alcântara where I ended up for a stretch, was where this really clicked for me. The shared wifi there was already flagged as suspicious by Google before I'd even turned my VPN on — every laptop in the building funnels out through the same handful of addresses, and mine was just adding another layer on top of an IP that was already having a bad reputation day.
My partner noticed the pattern faster than I did, mostly because constant captcha prompts meant I kept groaning and re-typing search queries mid-call. What we were actually running into is something called Carrier Grade NAT — Carrier Grade NAT routes a huge number of separate devices through one visible address, so instead of looking like two people working from an apartment in Lisbon, we looked like one entity that happened to be five hundred people. If you want the fuller version of how public networks complicate all this, How to Use a VPN for Secure Work Emails on Public Cafe Wifi goes into it properly — I won't repeat it all here.
Does Switching Servers Actually Stop the Captchas?
Sometimes. Switching to a different server resets your visible IP address, and if the one you land on has a cleaner recent history, the captchas can ease off within minutes. The catch is that you're gambling on a server you know nothing about — some regions have entire IP ranges that are already worn out from other VPN users hammering them, and you won't know which until you try.
Before I landed on anything that reliably worked, I tried talking my sister back in Stockport into staying logged into a few of my accounts and doing an awkward screen-share workaround whenever I hit a wall, so I wouldn't have to touch any settings myself. It was slower than just solving the actual problem, and coordinating time zones for something so small became its own small nightmare.
My friend Bram — who somehow never travels without a full-size mechanical keyboard, loud enough that I can hear individual keys over a voice call — insists that switching the protocol matters more than switching the server, and he is not shy about repeating this every time the subject comes up. He has a point often enough that I've stopped arguing.
What Finally Cut Down the Captcha Loops
Protocol switching turned out to be worth the fuss. Moving from OpenVPN to WireGuard, or NordVPN's own version of it called NordLynx, seemed to reset whatever reputation flags had built up — I couldn't tell you the exact mechanism, only that the captchas thinned out noticeably within the same session. NordVPN is the service I had this working on, mostly because their servers are labelled by what you're using them for, which matters when you're mid-deadline and don't have patience to test six options.
That same account is also where I found Meshnet, a feature for linking devices directly that I've written about separately in Why I Use NordVPN Meshnet for Secure Remote Work and File Sharing — it's not the fix for captchas specifically, but it's the kind of feature that made staying with one provider worth it rather than juggling several.
Obfuscated servers made the next real difference — they dress your VPN traffic up as ordinary HTTPS traffic instead of something that visibly announces itself as a VPN, which apparently matters to whatever is scoring your connection behind the scenes. There's a proper walkthrough of the setup in this guide on obfuscated servers if you want the click-by-click version. Staying logged into a Google account with some history behind it helped too, though it's a small privacy trade-off worth knowing about before you do it.
A dedicated IP is the other option worth knowing about — paying extra for an address that's yours alone instead of shared with strangers, so you're not carrying anyone else's bad behaviour into your own reputation. A nomad I got to know during a stretch in Lisbon, Reuben, was the one who first flagged this to me; he's the type who'll hand you a referral code for something he has no financial stake in, purely because he likes comparing notes on what's working for people. Back at the flat in Graça that's become my base between longer runs to Bangkok and Mexico City, I've got a cluster of sticky notes on the wall logging which server actually worked for iPlayer last — trusting my own memory stopped being an option a while ago.
Proxy Errors Are a Different Problem
Proxy errors are not the same complaint as a captcha, even though they feel similar in the moment — a proxy error is the platform explicitly detecting VPN traffic and refusing it outright, rather than just making you prove you're human before letting you through. I ran into this with Prime Video specifically, and the fix that finally worked is written up in Prime Video proxy error rather than repeated here, since it's a different enough problem to deserve its own explanation.
The clearest proof that things had actually improved came on an ordinary evening at the flat, when I opened Peaky Blinders and the opening titles started rolling before I'd even set my coffee down on the side table — no spinner, no prompt asking me to prove I existed, nothing. That's the whole bar now: not perfection, just the absence of friction I'd gotten so used to that I'd stopped noticing how much of it there was.
Choosing a VPN That Won't Interrogate You Every Search
If you're only stopping in a place for a week or two, I wouldn't bother chasing a dedicated IP or overthinking the provider — CyberGhost VPN is a reasonable low-effort option, and their 45-day money-back window gives you plenty of room to test whether it plays nicely with your usual apps before committing further. ExpressVPN is worth it if you're travelling with a partner and a small pile of devices, though it caps out at eight connections at once, which is fine for two people but tight if you're also running a smart TV box and a tablet on the same account.
None of this fixes every headache at once, either. How well an app behaves varies by platform — a captcha fix that works cleanly on a laptop browser doesn't always carry over to a smart TV app or a Fire Stick, so it's worth testing on whatever device you'll actually be using most. If you're relying on a physical travel router to cover a whole hotel room instead of installing an app on every device, that introduces its own separate setup to troubleshoot, which is outside what I'm covering here. Obfuscation and protocol switching can shave a little speed off your connection in exchange for the lower profile, which is a fair trade most days but worth knowing before you're on a call that needs to stay smooth. And none of this is the same project as spoofing your region to unlock a different country's library, or turning on DNS-level filtering to strip ads from your traffic — both are real reasons to want a VPN, just not the one this page is about.
Put together, the fixes that actually mattered were boring: switch protocol first, try an obfuscated server next, and don't discount a dedicated IP if you're staying anywhere longer than a couple of weeks. The captchas are a rare annoyance now instead of a daily one, which is honestly all I was hoping for. If you want to start with the provider that got me there, a longer-term plan with NordVPN is still the one I'd point a fellow remote worker toward first.