top of page

VPN Connected but No Internet? How to Diagnose a Travel Router VPN That Stopped Working

Writer: C. Monte Raynor
C. Monte Raynor
Sep 9
7 min read

Updated: 3 days ago

Your Personal VPN worked yesterday.


Today, your travel router says the VPN is connected, but you have no internet.


Or maybe websites load for a few minutes and then stop.


Maybe the connection keeps dropping.


Maybe everything on the router looks normal, but you simply can't get usable traffic through the system.


The immediate reaction is usually:


Something is wrong with my VPN.


Maybe.


But after setting up and supporting Personal VPN systems for more than three years, one of the biggest things I've learned is that the symptom doesn't necessarily tell you what actually failed.


A Personal VPN isn't just two routers.


It's a system.


You have an internet connection at your home location.


You have equipment at that location.


You have the internet connection wherever you're traveling.


You have your travel router.


And you have the VPN connection tying those two locations together.


All of those pieces have to continue working together.


So if your VPN says connected but you have no internet, the first thing I would recommend is not immediately changing settings.


The first question is:


What actually failed?


Before You Change Anything, Diagnose the Problem


I think about Personal VPN troubleshooting the same way I think about going to the doctor.


You tell the doctor:


“My knee hurts.”


That's a symptom.


It isn't a diagnosis.


The doctor still has to determine what is causing the pain before deciding how to treat it.


“VPN connected but no internet” works the same way.


Connected is a status.


Working is the outcome you actually care about.


A VPN tunnel may appear to be connected while traffic isn't moving normally through the system.


Or the VPN itself may be perfectly fine and the actual problem may exist somewhere else.


That's why randomly changing settings can make the situation worse.


You can take one problem and turn it into two.


Before treating the problem, isolate it.


Here are five places I would start looking conceptually.


1. Is the Problem Where You Are or Back Home?


This is one of the first distinctions I make when troubleshooting a Personal VPN.


Let's say you're traveling in Mexico, Colombia, Thailand, Spain, or anywhere else.


Yesterday everything worked.


Today your travel router connects, but your Personal VPN doesn't work normally.


It's easy to assume the problem is sitting on the table in front of you.


But what if the problem is thousands of miles away?


Maybe the internet is down at your home location.


Maybe there was a power outage.


Maybe the internet went down and came back, but some part of the home-side Personal VPN system didn't return to its normal state.


Maybe the equipment itself is offline.


If the problem exists at the home location, changing things on your travel router may accomplish absolutely nothing.


Worse, you may change something that was working correctly.


That's why I start with a simple conceptual question:


Is this a local problem or a remote problem?


Your Personal VPN has two sides, and you need to determine which side deserves your attention before you begin making changes.


If you want a better understanding of how those two sides fit together, start with my guide to Personal VPNs for remote work abroad and how the complete setup actually works.


2. Did Your Internet Provider Fix the Internet but Change Something Your VPN Needed?


Here's another problem I've seen.


The internet goes down at your home location.


Someone calls the internet provider.


The provider troubleshoots the connection and resets equipment as part of getting the service back online.


The normal household internet starts working again.


From the provider's perspective, the problem is solved.


But your Personal VPN no longer works the same way it did before.


Why?


Because a Personal VPN is part of a larger network.


Depending on how a particular system is designed, changes to the internet equipment at the home location can affect other pieces downstream.


I'm intentionally not going to turn this article into a list of settings to change.


That's exactly the kind of situation where you need to understand the original design before altering anything.


The important lesson is this:


Restoring internet service does not necessarily mean the entire Personal VPN system has been restored.


The internet provider may have successfully fixed its part of the problem while unintentionally changing something another part of your system relied on.


That can happen after an outage, a power event, equipment replacement, a reset, or other service work.


3. What If the VPN Says Connected but the Internet Still Doesn't Work?


This is one of the more confusing failure states.


Your router says the VPN is connected.


The indicator is green.


The VPN tunnel appears to be established.


But websites won't load.


Or everything is extremely slow.


Or the connection works for a little while, stops, reconnects, and then stops again.


This is why I don't consider connected and working to mean the same thing.


A connected status tells me that two pieces of equipment were able to establish some level of communication.


It doesn't automatically tell me that the connection is stable.


It doesn't tell me that traffic is flowing normally.


And it definitely doesn't tell me why the experience is breaking down.


I've dealt with situations where the routers were functioning, the internet connections were functioning, and the VPN could establish itself successfully.


Yet the overall connection still wasn't usable.


The eventual problem wasn't necessarily the VPN hardware at all.


It was somewhere upstream in the internet service.


And that's an important distinction.


If you immediately assume:


VPN connected but no internet = broken VPN router


you can spend a lot of time troubleshooting the wrong thing.


This also applies if your VPN keeps disconnecting.


Repeated VPN disconnects may look like a router problem from your side even when the underlying instability exists somewhere else in the path.


The better question is:


What part of the system is failing to deliver a stable outcome?


4. Can Your Travel Router Still Find the Home Side?


Here's another way a Personal VPN can fail even when the internet itself is working.


Think about the contacts in your phone.


You tap someone's name because your phone knows what number is associated with that person.


Now imagine that person changes their phone number.


Their phone works.


Your phone works.


But your contact information is outdated.


You try to call them and can't reach them.


A Personal VPN can have a conceptually similar problem.


Your travel-side equipment has to know how to find the equipment at your home location.


There are situations where the information used to find that location is no longer current.


Now you can have:


  • working internet at home;

  • working internet where you're traveling;

  • functioning routers on both sides;


and still not establish the connection you expect.


That doesn't necessarily mean either router is broken.


It may mean one side no longer has the correct information needed to locate the other.


I cover one specific version of this problem in more detail in my article on Dynamic DNS and Personal VPN setups.


The important point here isn't to start changing Dynamic DNS settings yourself.


The important point is recognizing that reachability is another part of the system that can fail.


5. Sometimes the Travel Router Really Is Dead


Not every Personal VPN problem requires a complicated explanation.


Sometimes hardware fails.


I've seen power-related incidents while people were traveling where equipment was damaged.


I've seen situations where the travel router simply stopped functioning normally.


And when that happens, the bigger problem often isn't just the failed router.


It's the fact that the person has no backup.


Now a technical issue becomes a logistical problem.


You're in another country.


Your Personal VPN depends on a specific piece of hardware.


The hardware fails.


Now you need to find replacement equipment, get it to your location, configure it correctly, and restore the system.


Potentially while you're also trying to work.


That's why redundancy matters.


If one small piece of equipment is critical to something important in your life, ask:


What happens if this box dies?


If you're still deciding which travel-router hardware belongs in your Personal VPN, I've written separately about GL.iNet travel routers for remote work and what you actually need.


Why Random VPN Troubleshooting Advice Can Make Things Worse


One of the biggest mistakes I see people make is searching for a symptom online and immediately changing whatever setting appears in the first answer.


The problem is that two Personal VPN systems that look identical from the outside may not be configured the same way underneath.


Different systems can have different:


  • internet providers;

  • router models;

  • network environments;

  • connection methods;

  • configuration choices;

  • firmware versions;

  • backup arrangements;

  • support assumptions.


So a setting that solves one person's problem may create another problem in your system.


This is especially true when someone inherited a Personal VPN that was configured by somebody else.


Before changing anything, you need to understand the system you actually have.


That's why diagnosis comes first.


“VPN Connected” Is a Status. “Working” Is the Goal.


If you remember only one thing from this article, make it this:


Connected does not necessarily mean working.


Your travel router can say connected.


Your VPN interface can show green.


A tunnel can establish successfully.


And the complete system can still fail to deliver the result you need.


That's why I look beyond the status indicator.


I want to know:


Is the internet working where you are?


Is the home location online?


Did anything recently change?


Is the connection stable?


Can the two sides still find each other?


Is the hardware healthy?


Only after answering those questions would I start thinking about what actually needs to be repaired or changed.


Installation Is Day One


This is also why I don't think of a Personal VPN as something you install once and forget about forever.


Installation is Day One.


What matters just as much is what happens later.


What happens when you change internet providers?


What happens when someone resets equipment?


What happens when you move?


What happens when you add equipment?


What happens after a power outage?


What happens when your travel router dies?


What happens when everything says connected but nothing seems to work?


And most importantly:


What is your plan when you can't figure out the answer yourself?


If you're comfortable building, diagnosing, and maintaining your own Personal VPN system, that's perfectly reasonable.


But if this is technology you're going to depend on while traveling or living abroad, ongoing support matters just as much as the original installation.


Work With No Borders


That's part of the reason I built Work With No Borders around more than simply installing Personal VPN equipment.


The goal is to help Freedom Seekers understand and maintain the system they're depending on after installation day.


That includes continuing education, post-installation support, help when the setup changes, and troubleshooting when a problem isn't immediately obvious.


Because getting your Personal VPN working the first day is one thing.


Knowing what to do months later when something changes is something completely different.


If you're planning to depend on a Personal VPN while traveling or living abroad and you don't want to manage every part of that system by yourself, learn more about the Work With No Borders Bundle.


And if your VPN currently says connected but you're staring at a browser with no internet, remember:


Don't start by changing things.


Start by figuring out what actually failed.

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page