blog

Website Works With a VPN but Not Without? Here's Why

Your site or app only loads with a VPN on? It's usually a DNS cache, an internet provider block or a firewall rule. How to find which one and fix it.

6 min readFixesDomainsOutages

Your site won't load. You turn on a VPN, and suddenly it works. Turn the VPN off, and it's broken again. Or a user writes that your app is down, while it works fine for you.

This is confusing, but it's also a strong clue. A VPN changes only a few things about how you reach a site, so the list of possible causes is short. This guide explains each one, how to recognize it and what to do, with real cases from Supabase and Cloudflare.

What a VPN actually changes

When you open a site, two things happen:

  1. A DNS lookup. Your device asks a DNS server, usually your internet provider's, for the site's address (its IP).
  2. The connection. Your device connects to that address over your provider's network.

A VPN changes both. It usually sends DNS lookups to its own servers, and it routes your traffic through a server in another place, often another country. So when "VPN on" works and "VPN off" doesn't, the problem is almost always one of these:

  • an old DNS answer remembered by your device or your provider;
  • a block by your internet provider or your country, on your site or on a service it uses;
  • a rule on your own site (a firewall or country block) that rejects your address;
  • something on your device or network, like an antivirus, a work network or a browser extension.

Step 1: Is it only you?

Before fixing anything, find out who's affected:

  • Open the site on your phone with Wi-Fi turned off, over mobile data. That's a different provider and a different DNS server.
  • Run our free checkup. It opens your site from our server, outside your network, and shows whether it answers.
  • Ask someone in another city or country to try.

If the site works everywhere except on your own connection, start with DNS. If it fails for everyone in one country or on one provider, it's likely a block. If it fails for everyone everywhere, it isn't a VPN question at all: see how to check if a website is down.

Cause 1: An old DNS answer (very common after a domain change)

This is the usual cause when you've just connected a custom domain or changed DNS records.

DNS answers are cached. Your provider's DNS server, your operating system and your browser all remember the answer for a while. As Julia Evans explains in DNS "propagation" is actually caches expiring, DNS changes aren't pushed out to the world: you're waiting for old cached answers to expire. Each record has a TTL that says how long it may be cached, but some resolvers keep answers longer. Resolvers can also remember that a name didn't exist, if you looked it up before you added the record.

A VPN uses different DNS servers, which may never have cached the old answer. That's why it works there and not on your own connection.

Fix it on your side:

  1. Flush your computer's DNS cache. On Windows, open Command Prompt and run:
ipconfig /flushdns

On a Mac, open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  1. Clear Chrome's own cache of DNS answers. Go to chrome://net-internals/#dns and click Clear host cache.
  2. Try a public DNS server. Change your computer's or router's DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). If the site starts working, your provider's DNS server still has the old answer.
  3. Restart your router if other devices on the same Wi-Fi have the same problem.

Your visitors may have the same old answers cached. Nothing on your side can clear their caches, but the problem disappears by itself once those answers expire. If the domain still fails on every network after a day, the records themselves are probably wrong. For apps built with Lovable, our guide on a Lovable custom domain not working walks through the records step by step.

Cause 2: Your internet provider or country blocks the service

Sometimes the block isn't aimed at you at all. Platforms like Supabase and Cloudflare serve many customers from shared addresses and domains. When an authority orders a block because of one project, every other project on the same domain or address can go down with it in that country.

This has happened several times recently. In its post Navigating regional network blocks, Supabase describes three blocks of supabase.co:

  • UAE: from September 2, 2025, for about 18 days, by the providers Etisalat and Du.
  • Yemen: from February 2, 2026, lifted on February 10.
  • India: from February 24 to March 3, 2026, by certain providers, under a government order.

Supabase writes that VPNs kept working in all three cases, because the blocks only apply inside the country's network and encrypted traffic to a server outside gets around them.

Cloudflare-hosted sites have had the same problem in Spain. TorrentFreak reported that the football league LaLiga obtained a court order to block Cloudflare IP addresses used for pirated streams. Because those addresses are shared, Cloudflare said the blocks reached large areas of the internet in Spain, affecting sites that had nothing to do with piracy.

How to recognize it:

  • It fails for many users in one country or on one provider, and works with a VPN.
  • If only your backend is blocked, your page loads, but sign-in and data don't. The browser console often shows errors like Failed to fetch or ERR_CONNECTION_TIMED_OUT for requests to your-project.supabase.co. See Supabase "Failed to fetch" error for how to read those.
  • The provider's status page may show an incident for that region. Check our Supabase status and Cloudflare status pages.

What you can do:

  • For yourself: a VPN or a different DNS server (if the block works through DNS) gets you working again.
  • For your users: you can't ask everyone to install a VPN. For Supabase, its blog post recommended custom domains as a workaround during the India block. Supabase's custom domains docs describe this as a paid add-on for projects on a paid plan: your API is served from your own address, such as api.example.com, and the original Supabase address keeps working too.
  • Keep users informed. Say what's going on and that you're working on it. A simple status page helps here.

Cause 3: Your own site blocks the address

If your site sits behind a firewall or security service, a rule there may be rejecting your visitors:

  • a country block you (or a template) turned on;
  • a rate limit that blocked your address after many reloads or test requests;
  • a bot or security check that dislikes your provider's addresses.

With a VPN, you come from a different address and country, so the rule doesn't match. The signs: you see a block page, an "Access denied" message or a 403 error instead of a timeout, and only some users are affected.

Fix: open the security or firewall section of your hosting or CDN dashboard and look at recent blocked requests. Check whether your address or country appears, and loosen or remove the rule that matched.

Cause 4: Something on your device or network

If the site fails only on one device or one network:

  • Try another browser and a private window, which turns off most extensions.
  • Pause antivirus "web protection" briefly, if you have it, and try again.
  • Work, school or public Wi-Fi often filters sites. Try mobile data.
  • Check the system date and time. A wrong clock can make every secure site fail with certificate errors.

Quick reference

What you seeMost likely causeFirst thing to try
New custom domain works only with a VPNOld DNS answer cachedFlush DNS, try 1.1.1.1
Page loads, data and sign-in fail without a VPNBackend blocked in your countryCheck Supabase status, console errors
Many users in one country affectedProvider or country blockCheck provider status, consider a custom backend domain
"Access denied" or 403 pageYour own firewall ruleReview blocked requests in your dashboard
Only one device or networkLocal setting or filterOther browser, mobile data

Know when your users can't reach you

The hard part of these problems is that you often don't see them: the site works on your connection while users somewhere else get errors. Checking your site from outside your own network, and keeping an eye on the status of the services your app depends on, means you hear about it before your inbox fills up.

FAQ

Why does a website work with a VPN but not without it?
A VPN changes two things: which DNS server looks up the site's address, and which network and country your traffic comes from. So the cause is almost always an old DNS answer cached on your side, a block by your internet provider, or a firewall rule that blocks your address or country.
My app's page loads, but data and sign-in only work with a VPN. Why?
Then the block or failure is on a different address than your site: usually your backend, such as supabase.co. In 2025 and 2026 Supabase reported regional blocks of supabase.co in the UAE, Yemen and India, where apps loaded but their data requests failed and VPNs kept working.
I just connected a custom domain and it only works on a VPN. Is it broken?
Probably not. Your computer or your provider's DNS server still remembers the old answer for that domain. It goes away once the cached answer expires. Flushing your DNS cache or switching to a public DNS server usually fixes it on your side right away.
Should I tell my users to use a VPN?
Only as a temporary workaround. If a provider or country blocks a service your app depends on, look for a lasting fix, such as serving the backend from your own domain, and keep users informed while it lasts.

Fixed it? Run a free Pingbuddy checkup on your live site. It shows whether your site answers and how fast, when your SSL certificate and domain expire, whether your Supabase project is paused and whether secret keys are visible in your public code.

Run free checkup →