A VPN profile that connected yesterday can fail today for several reasons: access status, network reachability, a client problem, changed configuration, or a service-side fault. Record the exact error and the first stage that fails before replacing anything. The fact that a saved profile stopped connecting does not identify the cause.

This article walks through the common, non-alarming reasons a profile can stop connecting, so you can recognize what's likely happening instead of guessing. It deliberately stays away from aggressive "fixes," because the right response is almost always calmer than that.

First, identify the failed stage

Start by separating what you observe from what you suspect. Does the profile fail to import, remain on Connecting, report an authentication error, or connect without useful traffic? Each observation leads to different checks. Keep existing settings and note the time, device, client version and network so support can compare the conditions.

With that framing in place, here are the reasons worth checking, without ranking their frequency.

The file you have may be an old copy

An outdated local file is one possibility. Compare the selected client entry with the current profile and any replacement instruction in the Panel. Age alone does not prove that a file is wrong: an unchanged saved profile can remain valid. Download and import a replacement when the supported guide or official support indicates one is needed.

The straightforward resolution is a current file from your own account rather than the one you've been holding onto. When to Re-Download Your VPN Profile covers exactly when refreshing is warranted, and keeping your files tidy in the first place — see How to Keep VPN Profile Files Organized — makes "is this the current one?" easy to answer.

The access behind the profile may have changed

A profile is a way of using access, and that access has its own lifecycle. If an access period has ended, been renewed, or otherwise changed status, the profile's behavior can change with it — a profile connecting is always subject to the state of the access behind it. This is ordinary account activity, not a fault in the file. VPN Profile Renewal and Status Changes explains how those status shifts relate to what you see.

In a team setting, access can also have been updated as part of normal changes — for example, when someone's role or arrangement changes. If your access is managed by someone else, that's a reason to check with them rather than to keep retrying the same file.

The server details may have changed

Sometimes the settings a profile relies on are updated on the provider's side. When that happens, a file you saved earlier may reference details that have since moved, and the older file stops connecting as a result. Again, this isn't a sign of a problem with your device — it's a normal reason a fresh profile from your account will behave differently from an old saved one.

You may be reaching for the wrong profile

If you have more than one profile — across devices, or more than one saved file — it's easy to import one that isn't the one you mean to use. What looks like "the profile stopped working" is sometimes "this is a different profile than I intended." A quick check that you're importing the file you actually mean to use rules this out, and it's another reason a clear naming and storage habit pays off.

Your current network may be limiting the connection

Where you are can matter as much as the file you're using. Some networks apply their own rules to the kinds of connections they allow, so a profile that connects on one network may behave differently on another — not because the profile changed, but because the network did. This is common on managed, public, or venue networks. If a profile connects in one place and not another, the network you're on is worth considering before the file itself. VPN on Hotel Wi-Fi and the VPN Troubleshooting Checklist both cover how network conditions show up.

Your sign-in details may have changed

If your setup involves credentials and those have changed — for instance, after you updated them — a profile that expects the previous details can stop connecting until it's used with the current ones. This is expected behavior, not a malfunction. When credentials are involved, making sure you're using your current ones is part of the picture.

A calm first step

Start with the error, the intended saved profile, current account status, and network readiness. Check any official service notice and ask your administrator when access is managed. A fresh file is appropriate when the profile is missing, outdated, or explicitly replaced; it does not fix an expired entitlement, a captive portal, an unavailable server, or every client error.

If a current file still doesn't connect, the situation is worth raising with the people who provide your access or with Lisar support through the official channels, rather than repeating the same attempt. Knowing where those questions go turns a stall into a quick ask.

The short version

Frequently asked questions

My VPN profile stopped connecting — did I do something wrong? Not necessarily. A failure can involve access, profile, client, network or service availability. Record the exact error, confirm current status and the intended setup, and replace the profile only when there is evidence that the saved copy is no longer valid.

Why would a file that worked before suddenly stop? Details the file relies on can be refreshed on the provider's side after you download it, so an older saved copy can stop matching. Your access status can also change over time. In both cases the file didn't break — it's just no longer current, and a fresh download reflects the updated details.

It connects on one network but not another. Why? Networks can apply their own rules to the connections they allow, so the same profile may behave differently in different places. If a profile connects at home but not on a public or managed network, the network you're on is the more likely factor than the file itself.

Should I tear everything down to fix it? No. Record the error and compare one factor at a time: profile selection, current access, client and network. Use a replacement file when the Panel or official support calls for it. Preserve the useful error details and ask official support if the cause remains unclear.

My access is managed by my team. What should I do? Check in with whoever manages it about the profile's status, since access can be renewed or updated as part of normal changes. Pair that with a fresh file from your own account if you have one, rather than repeatedly retrying an older saved copy.