Skip to content

OpenVPN Connect authentication failed after password change: 4 fixes to try

By Updated 10 min read

Some links on TechInfoTime are affiliate links: if you sign up or buy through them we may earn a commission, at no extra cost to you. We recommend a tool only where it fits the problem, and say who should skip it.

On this page (10 sections)
  1. The short version
  2. What you need
  3. Why authentication fails after a password change
  4. Fix 1: Update the saved credentials in OpenVPN Connect
  5. Fix 2: Clear cached credentials by re-importing the profile
  6. Fix 3: Update the referenced password file
  7. Fix 4: Check server-side password sync and certificates
  8. Common mistakes
  9. If you manage your own VPN, a simpler alternative exists
  10. Questions people still ask

In short: The error usually means OpenVPN Connect is still sending your old password, or the server has not received the new one. Update the saved credentials in the app, clear cached profiles, check any auth-user-pass password file, then confirm the server-side sync.

Part of our guide on secure hacked google account

At a glance
Most common causeOld saved credentials being reused
First fix to tryUpdate credentials in profile settings
Password file lineSecond line of auth-user-pass file
Full reset timeAbout 5 minutes
Tunnel rebuild needed?Rarely – re-import profile instead
Server sync delayMinutes on some directory setups

The short version

  • Most authentication failures after a password change are stored credentials being replayed, not a broken tunnel
  • Update the username and password inside OpenVPN Connect's profile settings first
  • Delete and re-import the profile to clear cached credentials the settings screen does not show
  • If your profile uses an auth-user-pass file, edit that file's second line to the new password
  • Server-side password changes can lag or need an admin to push them – verify before blaming your device

What you need

This is a software fix, so the shopping list is short. Gather these before you start and you can work through all four fixes in one sitting without stopping to hunt for files or passwords.

  • Your new password, confirmed by logging in to the account portal or asking your VPN admin
  • The .ovpn profile file your organisation or server admin gave you, kept somewhere you can reach
  • Access to the device where OpenVPN Connect is installed
  • For self-hosted servers: SSH access or the server admin's contact details
  • A plain text editor such as Notepad, TextEdit or VS Code if a password file is involved

Why authentication fails after a password change

openvpn connect authentication failed after password change - What you need
What you need

When you change a password, every place that stored the old one becomes a suspect. OpenVPN Connect keeps credentials in three possible spots: inside the app's saved profile, in a cached copy of the profile on your device, and in a separate password file if your .ovpn configuration points to one. Any of these can keep sending the old password long after you have forgotten it exists.

The server side can fail too. If your organisation authenticates against a central directory, the new password may take minutes to propagate, or an administrator may need to trigger a sync. In that window, a perfectly correct login still fails, which convinces people the app is broken when it is not.

There is a third failure mode people overlook: the profile itself. Some servers issue credentials tied to a certificate, and after a password change the server may expect a re-issued profile. That is rare, but it explains why re-importing the profile so often fixes the problem outright. We go through spoofed emails after password change step by step elsewhere on the site.

Where old passwords hide after a change
LocationWho controls itTypical symptom
Saved credentials in the appYouFails instantly on every connection attempt
Cached profile on the deviceThe appFails even after you retype the password
auth-user-pass fileYou or your adminFails only for profiles using that file
Server-side directoryYour VPN adminFails on every device, not just yours

Fix 1: Update the saved credentials in OpenVPN Connect

Start with the obvious one, because it solves most cases. Open OpenVPN Connect, find your profile in the list and open its settings or edit screen. Depending on your version, this is a pencil icon on desktop or a long-press menu on mobile.

Type the new username and password carefully, save, then attempt the connection. If your admin has enabled the saved-credentials option, the app stores what you enter; if not, it will prompt you at each connection, which is your chance to enter the fresh password correctly.

If the connection still fails, do not keep retyping. A cached profile underneath the visible one may be holding the old credentials, and no amount of retyping will touch it. Move on to the next fix. There is more on password manager autofill fails on bank site in a separate guide.

  1. Open OpenVPN Connect and select the failing profile
  2. Open the profile's edit or settings menu
  3. Replace the stored username and password with the new ones
  4. Save and reconnect once
  5. If it fails again, do not retry endlessly – go to Fix 2

Fix 2: Clear cached credentials by re-importing the profile

openvpn connect authentication failed after password change - Why authentication fails after a password change
Why authentication fails after a password change

OpenVPN Connect caches part of each profile on the device, and that cache can outlive the credentials you see in the settings screen. Deleting the profile from the app and importing the .ovpn file again clears it. You are not rebuilding the tunnel or asking your admin for anything new – the same file, a clean start.

On desktop, remove the profile from the sidebar, then drag the .ovpn file back in or use the import option. On mobile, delete the profile and re-import from your files. When the app asks for credentials during import, enter the new password.

This fix also covers the case where your organisation re-issued the profile after the password change. If your admin sent a new .ovpn file, import that version instead of the old one – the old file may reference a revoked credential set. The other half of this decision is avast login problems.

  1. Delete the failing profile from OpenVPN Connect
  2. Locate the .ovpn file you were originally given
  3. Import it again through the app's import option
  4. Enter the new username and password when prompted
  5. Connect once and confirm it holds for a few minutes

Fix 3: Update the referenced password file

Some .ovpn profiles include a line reading auth-user-pass followed by a file path. When that line is present, OpenVPN does not prompt you at all – it reads the username from the first line of that file and the password from the second. Change your password anywhere else and this file keeps feeding the old one to the server on every attempt.

Open the file in a plain text editor. You will see two lines: username on top, password beneath. Replace the second line with your new password, save, and reconnect. Do not add spaces, quotes or a trailing newline character beyond what was already there.

Check the path too. If the profile was created on another machine, the path may point to a location that does not exist on yours, which produces the same authentication-failed message. If the file is missing, either recreate it with the same two-line format or remove the filename from the auth-user-pass line so the app prompts you instead. It helps to understand importance of 2fa security before going further.

  1. Open the .ovpn file in a text editor and find the auth-user-pass line
  2. Note the file path listed after it
  3. Open that file and replace the second line with the new password
  4. Save without extra spaces or quotes
  5. Reconnect and confirm authentication succeeds

Fix 4: Check server-side password sync and certificates

Phone screen showing the OpenVPN Connect profile edit screen
Phone screen showing the OpenVPN Connect profile edit screen

If every device fails with the new password, the problem is on the server, not in your app. Password changes made in a central directory can take several minutes to reach the VPN server, and some setups need an administrator to run a sync manually. Ask your admin to confirm the new password is live and check the server log for your username – the log will say whether it saw an authentication attempt at all.

Certificates are the other server-side suspect. If your VPN uses certificate-based authentication alongside passwords, a password change on the server can be paired with a certificate reissue. An expired or revoked client certificate produces an authentication failure that looks identical to a wrong password.

While you are talking to the admin, ask whether the profile needs reissuing. A fresh .ovpn file with current certificates, imported per Fix 2, resolves the stubborn cases where credentials, cache and password file were all already correct. It helps to understand rootkit removal for Windows before going further.

What the failure pattern tells you
PatternLikely locationFix
Fails on one device onlyYour deviceFixes 1-3
Fails on all devicesServer sideFix 4, admin needed
Fails only for one profileThat profile or its fileFixes 2-3
Log shows no attemptClient not sending credentialsFixes 1-2

Common mistakes

These are the detours that turn a five-minute fix into an afternoon. Each one comes from a real pattern in support threads, and each has a simple correction.

  • Retrying the same cached profile a dozen times -> re-import the profile once instead, per Fix 2
  • Editing the .ovpn file when the password lives in the referenced password file -> edit the file on the auth-user-pass line, per Fix 3
  • Adding quotes or spaces around the new password in a text file -> passwords in auth-user-pass files are taken literally, character for character
  • Rebuilding the whole tunnel from scratch -> unnecessary in almost every case; re-import the existing profile first
  • Blaming the app when every device fails -> check server-side sync before touching your device again
  • Storing the new password in a plaintext file on a shared computer -> use the app's prompt instead, and delete the file

If you manage your own VPN, a simpler alternative exists

Everything above assumes you run or inherit a self-hosted VPN, which means you own the credential plumbing. That control is worth having for company resources, but for personal privacy on public Wi-Fi it is a lot of maintenance for little gain: every password change, certificate reissue and server update lands on you.

A consumer service such as NordVPN removes that layer entirely. There is no .ovpn file to re-import and no password file to edit – the app handles authentication with your account login, and a password change is simply a sign-in. It does not connect you to a private company network, which is the honest limitation; it exists for privacy and public Wi-Fi security, not remote access to your own servers.

For many readers the right answer is both: keep the self-hosted tunnel for work, and use a consumer app for coffee-shop and hotel Wi-Fi. If you only needed the VPN for privacy in the first place, switching may delete this entire class of problem from your life.

What works
  • No profile files or password files to maintain
  • Password changes work with a simple sign-in
  • Kill switch and app-level security handled for you
What to watch
  • Does not reach private company networks
  • Monthly cost versus a free self-hosted setup
  • You depend on the provider's server network

Questions people still ask

Why does OpenVPN Connect still fail after I enter the new password?

The app may be reading credentials from a cached profile or a referenced password file rather than what you type. Delete and re-import the profile, and if the .ovpn file contains an auth-user-pass line with a filename, update that file's second line with the new password.

Where is the auth-user-pass password file located?

The path is written on the auth-user-pass line inside your .ovpn profile. Open the profile in a text editor and read the path after the keyword. If the path is missing or points nowhere on your machine, remove the filename so the app prompts you instead.

Do I need to recreate the whole VPN tunnel after a password change?

Almost never. Re-importing the same .ovpn profile and updating credentials is enough in the vast majority of cases. A full rebuild is only needed if the server admin reissued certificates or the profile itself was revoked.

How long does server-side password sync take?

It varies by setup. Some directory-backed servers pick up a password change within minutes; others require an administrator to run a sync manually. If the new password fails on every device, ask your admin to check the sync status and the server log.

Is it safe to store my VPN password in a text file?

It is a real risk on shared or stolen devices, since the file is readable by anything with access to your disk. Prefer the app's credential prompt where possible, restrict file permissions if you must use one, and switch to certificate or multi-factor authentication when you can.

Can I keep both a work VPN and a consumer VPN on the same device?

Yes, in most cases. Connect to them one at a time rather than stacking tunnels, since two active VPNs on the same adapter conflict. Many people use the work tunnel for company resources and a consumer app for general public Wi-Fi privacy.

I have lost count of the times a stubborn auth failure turned out to be a two-line password file nobody remembered creating.

Daniel Brooks Editor

Daniel Brooks writes TechInfoTime's guides to Windows, Mac and phone problems, online privacy and security, and the apps and AI tools worth using, working through each fix step by step on the settings real people have.

More in Security & Antivirus