FAQ 简体中文 繁体中文 English

• Local extension data may be corrupted.
• You may be entering the wrong password type.
• Your browser may have cleared the extension storage.

Try signing in again first. If the problem continues, clear the extension data and add it again, or switch to the latest 5UF VPN app.

The compatibility password is kept for old protocols and legacy compatibility mode. It may be different from your normal app login password. Please follow the information shown in your account panel.

In that case, you usually need to enter your compatibility password, not your normal app login password.

• When signing in to the account: usually use your normal account password.
• When a password prompt appears again after selecting a server: usually use the compatibility password.

To support certain legacy VPN dialing protocols, 5UF VPN previously introduced a Compatibility Password.

The Compatibility Password is mainly used for:

• L2TP

• PPTP

• IKEv2

• “Super VPN” servers in the browser extension (Note: not during the first login, but when selecting a server and being prompted to enter the password again.)

These legacy protocols have technical limitations:

• The password must be stored in plaintext on the server side

• Special characters are not supported

• Encryption standards are outdated

Because of these constraints, a separate Compatibility Password was required.

What is the regular account password?

The latest 5UF VPN APP now uses a modern password encryption mechanism that meets current industry security standards:

• Passwords are securely encrypted and stored

• Full character set supported (including special characters)

• Not directly tied to VPN dialing authentication

• No plaintext storage required

In the new client, VPN authentication is handled through upgraded secure mechanisms and is independent from the old Compatibility Password.

Why are we phasing out the Compatibility Password?

Due to the technical limitations of legacy protocols:

• Passwords must be stored in plaintext (security risk)

• No support for special characters

• Weaker encryption design

For security reasons, we have decided to gradually discontinue support for Compatibility Passwords and legacy protocols.

Can existing users still use the Compatibility Password?

Yes, existing users can continue using it for now.

However:

• If you change your account password

• The new password will become your regular account password

• The old Compatibility Password will not automatically sync

• The two passwords will become different

This is why we strongly recommend migrating to the latest client.

Our Recommendation

We strongly recommend all users:

• Switch to the latest version of the 5UF VPN client

• Stop using legacy apps

• Stop using legacy protocols (L2TP / PPTP / IKEv2, etc.)

Legacy protocol support and Compatibility Password functionality will be discontinued in future updates.

The new client provides:

• Stronger encryption

• Higher security standards

• More stable connections

If you have any questions, please contact our support team via the in-app ticket system.

If the Chrome extension asks for username and password again after you select a server, do not enter your normal app login password directly.

In this case, you should usually enter your compatibility password to verify the server again.

Recommended steps:

1. Enter your account username first.
2. If the popup is a server verification window, enter your compatibility password.
3. After verification succeeds, the extension will usually continue the connection.

Why does this happen?

The old Chrome extension workflow relied on older extension network APIs to handle authentication and request interception. In newer Chrome versions, extension permissions and interception behavior have changed, so the old method may no longer complete authentication automatically in some cases. That is why a verification popup may appear and require manual confirmation.

According to Chrome's official documentation:

• In Manifest V3, webRequestBlocking is no longer available to most extensions: Chrome webRequest API
• Chrome's migration guide also explains that blocking request listeners should be replaced with the newer declarative model: Replace blocking web request listeners
• Authentication handling (onAuthRequired) also depends on related extension permissions: Handling authentication

Please note:

• This browser extension method is only a legacy compatibility solution and is not recommended as your main long-term setup.
• For better stability, we recommend using the latest 5UF VPN app.
• If the verification popup keeps appearing, make sure you are entering the compatibility password, not your normal app login password.