Type or paste your message into the help center search, or browse the families below. Then follow the “To do” steps for its family, in order.
If the problem continues, write to support at contact@fuzevpn.com with the exact message.
Windows: engine, service and network protection
On Windows, FuzeVPN relies on its Windows service, “FuzeVPN — VPN service”, and on the WireGuard or OpenVPN engine. Together, they create the tunnel and its network protection: protection if the connection drops (kill switch), tunnel network and DNS.
Here, one of them did not respond, did not start or stopped before the connection, or an unidentified error occurred. In “Automatic” mode, the OpenVPN error is shown if WireGuard and then OpenVPN fail.
To do
For “… did not confirm the operation within the expected time” or “The … command could not be sent to the local VPN service”: wait until FuzeVPN has checked the VPN status. Then try again if needed. After a timeout, the operation may still finish in the background.
Click “Disconnect” in FuzeVPN and wait for confirmation. Then start the VPN connection again. Disconnecting also removes the internet block that the protection if the connection drops keeps in place after a failure.
If the internet stays blocked, open the “Diagnostics” page from the side menu and click “Diagnostics”. Then, below the results, click “Complete disconnection”.
If the message comes back, quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it. The cross only minimises FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
Try the other protocol: disconnect the VPN, then choose WireGuard or OpenVPN in “Settings → Connection → VPN protocol”. In “Automatic” mode, FuzeVPN switches to OpenVPN once, if WireGuard does not start on your PC.
For “An unknown WireGuard error occurred…”: also try another location or another network. The article on the VPN that won’t connect covers these steps.
Restart Windows, then try again.
For “The response from the local … service was invalid”, “The secure OpenVPN component…”, “The OpenVPN DCO adapter…” or “An unknown WireGuard error occurred…”: if the message still comes back, reinstall FuzeVPN with the installer from the FuzeVPN for Windows page. It also offers “Repair”, and your preferences are kept. Choose the one for your processor, x64 or ARM64, shown in Windows system information.
After reinstalling, FuzeVPN automatically adds this PC as a new device the next time you connect. If your limit is reached, the app asks you to remove one. You can do this from any FuzeVPN app.
For “… error occurred. See the local diagnostic log.”: send the diagnostic report instead. It contains the app’s technical logs.
If the message still comes back, open the “Diagnostics” page from the side menu and click “Diagnostics”. The report is sent if you are signed in to your account. If sending fails, FuzeVPN retries 5 times over 24 hours, and “Try again” sends it again.
Then write to support at contact@fuzevpn.com, with the exact message, its code if shown, and the report ID. Also include the time, the FuzeVPN version if visible, and the location, protocol and network used. If you are not signed in, copy the report text and paste it into your email.
Messages
The OpenVPN command could not be sent to the local VPN service.
Windows app
The OpenVPN DCO adapter could not be used.
Windows app
Windows could not prepare or finalize WireGuard network protection.
Windows app
The DCO adapter is open, but the server could not be configured in the driver.
Windows app
Windows could not prepare the kill switch before the VPN connection.
Windows app
Windows could not complete the network configuration for the OpenVPN tunnel.
Windows app
The WireGuard tunnel service did not reach the active state.
Windows app
Windows could not prepare or finalize OpenVPN network protection.
Windows app
The local WireGuard service did not confirm the operation within the expected time.
Windows app
An unknown OpenVPN error occurred. See the local diagnostic log.
Windows app
An unknown WireGuard error occurred. See the local diagnostic log.
Windows app
The response from the local WireGuard service was invalid.
Windows app
The response from the local OpenVPN service was invalid.
Windows app
Windows could not configure DNS for the OpenVPN tunnel.
Windows app
OpenVPN Core stopped before the network connection was opened.
Windows app
The local OpenVPN service did not confirm the operation within the expected time.
Windows app
The OpenVPN tunnel could not be started.
Windows app
The secure OpenVPN component is unavailable.
Windows app
The WireGuard command could not be sent to the local VPN service.
Windows app
Android: VPN engine, interface and previous session
The Android app could not start or keep the VPN connection. Its WireGuard or OpenVPN engine (the two connection protocols), or Android itself, refused or stopped it.
An internal detail may also be missing, or the error may not be specified. Sometimes a previous connection has not fully stopped yet and blocks the new one.
To do
For “OpenVPN session still active”, “Native tunnel already active”, “OpenVPN identity still in use”, “WireGuard identity already in use” or “WireGuard operation still active”: a previous connection is still active. Disconnect FuzeVPN. As soon as the app shows “Disconnected” and its notification disappears, start a single connection again, with no waiting time required.
For “OpenVPN session still active”, “Native tunnel already active”, “OpenVPN identity still in use”, “WireGuard identity already in use” or “WireGuard operation still active”: the shutdown is confirmed within 15 seconds at most, or the app offers “Retry shutdown”: tap it. With the always-on VPN active, tap “Open Android settings” to turn it off. For details, follow the article on being unable to disconnect.
Try again from the FuzeVPN app: start the connection again.
For “OpenVPN interface…”, “OpenVPN interface creation failed” or “OpenVPN TUN setup failed”: stop any other VPN app on the phone. Then start the connection again from FuzeVPN. Accept Android’s request if it appears.
Close and reopen FuzeVPN, then try again.
Try the other protocol or another location. To change protocol, disconnect the VPN, then choose WireGuard or OpenVPN in “Connection” → “Advanced options” → “Protocol”.
For “OpenVPN engine unavailable”: choose WireGuard. To get OpenVPN back, install FuzeVPN from Google Play or with the APK file from the Download page. To switch from one to the other, uninstall the app first.
Update FuzeVPN: through Google Play, or by installing the new APK over the old one. Our team monitors diagnostics in real time and regularly rolls out fixes.
Restart the phone, then try again.
If the message comes back, copy the code shown below the message (“Diagnostic code: …”) with the “Copy” button. Then run diagnostics: open Account → “Need help?” → “Run diagnostics”.
While signed in to your account, tap “Send the report”, then “Retry sending” if needed. To keep an unsent report, tap “Save report” before closing the app.
Then write to support at contact@fuzevpn.com, with the report reference (“Reference: …”) or the saved report. Add the exact message and the diagnostic code. Also include your device, the FuzeVPN version if visible, the chosen location, the network and the time.
Messages
Invalid VPN account — The native operation is not associated with a valid account identifier.
Android app
Incomplete VPN parameters — The information needed for this VPN operation is incomplete. Try again. If the problem continues, run a diagnostic.
Android app
Invalid device identifier — The device identifier sent to the native engine is missing or invalid.
Android app
Android operation interrupted — An app error interrupted the VPN operation. Try again. If the problem continues, run a diagnostic.
Android app
OpenVPN client interrupted — OpenVPN Core received a terminal client stop.
Android app
OpenVPN restart requested — OpenVPN Core requested a restart of its transport session.
Android app
OpenVPN client setup failed — OpenVPN Core could not initialize the client before the network connection.
Android app
OpenVPN connection interrupted — OpenVPN Core stopped before emitting the CONNECTED event.
Android app
OpenVPN Core ended with an error — The native OpenVPN loop ended with an error and no more specific terminal event.
Android app
OpenVPN identity still in use — A native OpenVPN session is still using this device’s key or certificate.
Android app
Native OpenVPN call interrupted — An app error interrupted OpenVPN. Try connecting again. If the problem continues, run a diagnostic.
Android app
OpenVPN session still active — The native engine still holds the previous OpenVPN session and refuses to create a second one.
Android app
OpenVPN call timed out — A JNI call to OpenVPN Core exceeded its maximum duration.
Android app
OpenVPN service unavailable — Android could not start the OpenVPN foreground service.
Android app
OpenVPN start rejected — The Android service is ready, but OpenVPN Core did not accept starting the profile.
Android app
OpenVPN stopped before connecting — The native OpenVPN loop stopped before CONNECTED, without an explicit Core error.
Android app
Unclassified native VPN error — An undocumented native branch failed. Send the diagnostic code shown below to support.
Android app
OpenVPN interface already open — OpenVPN requested a second interface in the same connection. The tunnel was stopped for safety.
Android app
Could not create OpenVPN interface — Android rejected the network configuration requested by OpenVPN.
Android app
OpenVPN interface interrupted — OpenVPN Core received a request to stop the TUN interface.
Android app
OpenVPN interface creation failed — OpenVPN Core could not obtain the TUN interface from Android VpnService.
Android app
OpenVPN interface disabled — Android or OpenVPN Core disabled the TUN interface during the connection.
Android app
OpenVPN TUN setup failed — OpenVPN Core rejected the network plan before creating the Android interface.
Android app
Native tunnel already active — Android reports that a previous VPN session is still using the interface.
Android app
WireGuard identity already in use — Another operation is still using this account’s WireGuard key.
Android app
WireGuard operation still active — The previous WireGuard operation has not yet released its native service.
Android app
WireGuard start rejected — The WireGuard engine rejected activation of the configuration.
Android app
OpenVPN connection not confirmed — The OpenVPN connection could not be confirmed. It was stopped for safety. Try again.
Android app
Tunnel configuration rejected or incomplete
To open the tunnel, the VPN’s encrypted connection, the app receives a configuration from the server. This is an OpenVPN profile or a WireGuard configuration, with addresses, routes, DNS and encryption.
Here, this configuration is incomplete, invalid or requires a feature the app does not support. The app rejects it, and the connection is not established.
To do
Disconnect the VPN, then start the connection again from the FuzeVPN app: it requests the configuration from the server again. On Windows, disconnecting also unblocks the internet. After a failure, protection if the connection drops (kill switch) keeps the internet blocked until you disconnect.
For the Android messages in this family, with “Always-on VPN” on: open “Settings” → “Network & internet” → “VPN”, then the gear icon next to FuzeVPN. Briefly turn off “Block connections without VPN”, then “Always-on VPN”. Start the connection again in FuzeVPN, then turn them back on.
For “OpenVPN address missing”, “OpenVPN DNS missing” or “OpenVPN routes missing”: also check that no other VPN app is active. Then check that FuzeVPN still has Android’s VPN permission.
Choose another location.
Switch to the other protocol. Disconnect the VPN, then choose WireGuard or OpenVPN: on Windows, in “Settings → Connection → VPN protocol”; on Android, in “Connection” → “Advanced options” → “Protocol”.
Update FuzeVPN, then try again from the app. On Windows, accept the update offered, or run the installer from the FuzeVPN for Windows page. On Android, use Google Play, or install the new APK over the old one.
For “OpenVPN Core rejected the client configuration” or “The received profile is not compatible with OpenVPN DCO”: switch to WireGuard. If the message comes back after the update, run diagnostics straight away, then write to support at contact@fuzevpn.com.
If the message comes back, run diagnostics. On Windows, open the “Diagnostics” page from the side menu, then click “Diagnostics”. On Android, open Account → “Need help?” → “Run diagnostics”.
If you are signed in to your account, Windows sends the report by itself; on Android, tap “Send the report”. If you are not signed in, copy the report text on Windows. On Android, tap “Save report” before closing the app.
Then write to support at contact@fuzevpn.com, with the report reference shown after sending, or the saved or copied report. Add the exact message and its code, if it is shown below the message (Android) or on the “Diagnostics” page (Windows). Also include your device, the FuzeVPN version if visible, the chosen location, the network and the time.
Messages
The OpenVPN profile protection material is invalid.
Windows app
The received OpenVPN profile is invalid on this computer.
Windows app
The WireGuard configuration received from the API is invalid.
Windows app
OpenVPN Core rejected the client configuration.
Windows app
The received profile is not compatible with OpenVPN DCO.
Windows app
Network configuration rejected — The tunnel configuration is incomplete or does not match the authorized addresses. Try again from the app.
Android app
Invalid OpenVPN cipher — The server supplied an encryption algorithm that is not in the allowed list.
Android app
OpenVPN compression rejected — OpenVPN Core rejected the compression mode announced by the profile or server.
Android app
Unsupported OpenVPN authentication — The server or a proxy requests interactive credentials that are not part of this certificate profile.
Android app
Unsupported OpenVPN feature — The profile or server requires a feature missing from this Android client.
Android app
OpenVPN profile rejected — The profile received from the server is incompatible. Recreate this device and try again.
Android app
OpenVPN intermediary transport failed — OpenVPN Core reported a failure of the configured proxy or relay.
Android app
OpenVPN TLS verification missing — The profile does not explicitly require server certificate verification.
Android app
OpenVPN address missing — The server did not provide a usable tunnel address.
Android app
OpenVPN DNS missing — The server did not provide a usable DNS server.
Android app
OpenVPN routes missing — The server did not provide usable tunnel routes.
Android app
Invalid WireGuard configuration — The received WireGuard address, DNS, server key, or routes are invalid.
Android app
Certificates and secure connection
With OpenVPN, the app and the server verify each other’s identity with certificates, during a secure negotiation (TLS). On Windows, diagnostics and the update check also verify the secure connection to the FuzeVPN service.
Here, this verification fails: the certificate is rejected, not recognised, revoked or incompatible, or the negotiation was interrupted.
To do
For the Windows messages in this family, and for “Server certificate rejected”, “OpenVPN TLS alert”, “OpenVPN negotiation rejected” or “OpenVPN TLS negotiation rejected”: check the device’s date and time. Turn on automatic date and time, then try again.
For “The secure connection to the service could not be verified” or “The secure connection negotiation failed…”: an antivirus or firewall may be scanning your HTTPS connections (secure connections to websites). If so, turn off this scanning, then try again.
For “Secure negotiation with the OpenVPN server failed”, “The secure connection negotiation failed…” or “The secure connection to the service could not be verified”: try another network.
For messages that mention “OpenVPN”: choose another location.
For “TLS certificate revoked”: start the connection again from the FuzeVPN app itself. The OpenVPN profile then renews automatically. If the app offers “Retry cleanup”, tap it, then tap “Sign in”.
For messages that mention “OpenVPN”, and for “TLS certificate revoked”: switch to WireGuard in the meantime. Disconnect the VPN, then choose WireGuard: on Windows, in “Settings → Connection → VPN protocol”; on Android, in “Connection” → “Advanced options” → “Protocol”.
Update FuzeVPN, then try again from the app. On Windows, accept the update offered, or run the installer from the FuzeVPN for Windows page. On Android, update through Google Play, or install the new APK over the old one.
For “Unsupported OpenVPN certificate”, “Unsupported OpenVPN signature” or “Incompatible OpenVPN TLS version”: if the message comes back after the update, run diagnostics straight away, then write to support at contact@fuzevpn.com.
For “OpenVPN authentication rejected”, “OpenVPN client certificate rejected”, “OpenVPN client certificate required” or “OpenVPN client certificate not recognized”: run diagnostics straight away, then write to support at contact@fuzevpn.com.
For “TLS certificate revoked”: if the message comes back, remove this device in Account → “Your devices” → “Manage my devices” → “Remove”. Then tap “Sign in”: a new device is created.
For “The secure connection to the service could not be verified”: if the message comes back, remove this device in the “Devices” sidebar menu, with “Remove device”. Sign in again: a new device is created. As a last resort, reinstall FuzeVPN with the installer from the FuzeVPN for Windows page.
If the message comes back, run diagnostics. On Windows, open the “Diagnostics” page in the sidebar menu, then click “Diagnostics”. On Android, open Account → “Need help?” → “Run diagnostics”.
If you are signed in to your account, Windows sends the report automatically; on Android, tap “Send the report”. If you are not signed in, copy the report text on Windows. On Android, tap “Save report” before closing the app.
Then write to support at contact@fuzevpn.com, with the report reference shown after sending, or the saved or copied report. Add the exact message and its code, if it appears below the message (Android) or on the “Diagnostics” page (Windows). Also include your device, the FuzeVPN version if it is visible, the location you chose, the network and the time.
Messages
Secure negotiation with the OpenVPN server failed.
Windows app
The OpenVPN server certificate could not be verified.
Windows app
The secure connection negotiation failed. The cause has not yet been identified.
Windows app
The secure connection to the service could not be verified.
Windows app
Server certificate rejected — The OpenVPN server identity could not be verified.
Android app
OpenVPN authentication rejected — The OpenVPN server rejected the profile authentication.
Android app
OpenVPN client certificate rejected — The server rejected this device certificate. Recreate the device before trying again.
Android app
OpenVPN TLS alert — The server returned a TLS alert outside the certificate and version categories.
Android app
OpenVPN client certificate not recognized — The server does not recognize the authority of this device certificate. The OpenVPN server must be checked.
Android app
Unsupported OpenVPN certificate — The server does not support the secure certificate type used by Android.
Android app
TLS certificate revoked — The certificate presented during connection has been revoked.
Android app
OpenVPN client certificate required — The server requires a client certificate, but OpenVPN Core could not present one.
Android app
OpenVPN negotiation rejected — The server rejected the TLS negotiation. Recreate the profile if the problem persists.
Android app
OpenVPN TLS negotiation rejected — The server interrupted the TLS negotiation before connection.
Android app
Unsupported OpenVPN signature — The server rejected the Android Keystore key’s ECDSA P-256 algorithm.
Android app
Incompatible OpenVPN TLS version — The client and server did not find a common TLS version.
Android app
Device VPN identity and OpenVPN profile
Each device has its own VPN identity: keys created on the device, of which FuzeVPN receives only the public part. For OpenVPN, a certificate and a profile linked to these keys are added.
Here, the app cannot prepare, read or clear this identity. Or the device’s OpenVPN profile is rejected, or no longer matches the one the service knows.
To do
For “Unable to prepare this device’s secure VPN identity” (Windows, when signing in to your account): choose “Quit FuzeVPN” in the “Sign in” window or in the menu of the icon near the clock. The cross only minimises FuzeVPN near the clock. Reopen FuzeVPN, then sign in to your account again.
For “Unable to prepare this device’s secure VPN identity”: if the message comes back, restart the computer, then try again.
For “Invalid OpenVPN identity”, “OpenVPN operation interrupted”, “OpenVPN conflict”, “OpenVPN profile already exists”, “Incomplete OpenVPN removal” or “The revoked OpenVPN profile could not be fully removed”, with “Always-on VPN” turned on: before trying again or repairing the profile, open “Settings” → “Network & internet” → “VPN”, then the gear icon next to FuzeVPN. Briefly turn off “Block connections without VPN”, then “Always-on VPN”. Turn them back on once the connection is repaired in FuzeVPN.
For “OpenVPN conflict”, “OpenVPN profile already exists”, “Invalid OpenVPN identity” or “OpenVPN operation interrupted”: refresh the devices first. Open Account → “Your devices” → “Manage my devices”. Tap “Refresh devices”, or pull the screen down.
For “An OpenVPN profile already exists for this device”, “The local OpenVPN identity could not be read”, “OpenVPN conflict” or “OpenVPN profile already exists”: try again.
For “Incomplete OpenVPN removal” or “The revoked OpenVPN profile could not be fully removed”: tap “Retry cleanup”. Once the cleanup is confirmed, tap “Sign in”: the app creates a new OpenVPN profile.
For “The OpenVPN certificate does not match this device’s local identity”, “The local OpenVPN identity could not be read”, “Invalid OpenVPN identity”, “OpenVPN operation interrupted” or “OpenVPN conflict”: renew this device’s OpenVPN profile. On Windows, click “Renew profile”. On Android, start the connection again from the app: it recreates the identity automatically.
For “Inconsistent OpenVPN identity”: run diagnostics straight away, then write to support at contact@fuzevpn.com.
For messages that mention “OpenVPN”: in the meantime, switch to WireGuard. Disconnect the VPN, then choose WireGuard: on Windows, in “Settings → Connection → VPN protocol”; on Android, in “Connection” → “Advanced options” → “Protocol”.
For messages that mention “OpenVPN”, except “Inconsistent OpenVPN identity”: if the message comes back, remove this device from the app’s device list. Sign in again: a new device is created. As a last resort, reinstall the app.
If the message comes back, run diagnostics. On Windows, open the “Diagnostics” page in the sidebar menu, then click “Diagnostics”. On Android, open Account → “Need help?” → “Run diagnostics”.
If you are signed in to your account, Windows sends the report automatically; on Android, tap “Send the report”. If you are not signed in, copy the report text on Windows. On Android, tap “Save report” before closing the app.
Then write to support at contact@fuzevpn.com, with the report reference shown after sending, or the saved or copied report. Add the exact message and its code, if it appears below the message (Android) or on the “Diagnostics” page (Windows). Also include your device, the FuzeVPN version if it is visible, the location you chose, the network and the time.
Messages
Unable to prepare this device’s secure VPN identity.
Windows app
The OpenVPN certificate does not match this device’s local identity.
Windows app
An OpenVPN profile already exists for this device.
Windows app
The local OpenVPN identity could not be read.
Windows app
Invalid OpenVPN identity — Create a new OpenVPN identity and try again.
Android app
OpenVPN operation interrupted — Create a new OpenVPN identity and try again.
Android app
OpenVPN conflict — The profile changed. Refresh devices and try again.
Android app
OpenVPN profile already exists — An OpenVPN profile already exists for this device.
Android app
Incomplete OpenVPN removal — Android could not remove the entire local OpenVPN identity for this account.
Android app
Inconsistent OpenVPN identity — The certificate does not match this phone’s secure identity. No local profile was replaced.
Android app
The revoked OpenVPN profile could not be fully removed. Retry cleanup.
Android app
Secure device or browser storage (keys and session)
FuzeVPN keeps your WireGuard or OpenVPN connection keys and your session on the device, in a protected space. Private keys stay on the device.
Here, the app could not read, save or clear this data. Or, in the extension, the browser’s storage is temporarily unavailable.
To do
Try the action that failed again.
For “The saved session could not be cleared” (Windows): try signing out of your account again before signing in with another account.
For “Your saved session could not be read” (Windows): try the verification again. Your session stays saved.
For “The VPN is stopped, but session removal is not confirmed” (Android): the VPN is indeed stopped. Retry the cleanup the app offers.
For the other Android messages in this family: unlock the phone, reopen FuzeVPN, then try again. After the phone restarts, FuzeVPN’s encrypted data only becomes accessible once the phone is unlocked.
For “WireGuard identity unavailable” or “Invalid local WireGuard key”: start the connection again from the app. It then renews the device’s identity automatically, without taking up an extra device slot.
For Windows messages that mention “protected storage” or “saved session”: choose “Quit FuzeVPN” in the menu of the icon near the clock; the cross only minimises it near the clock. Reopen FuzeVPN with the same Windows account as usual, then try again.
For Windows messages that mention “protected storage”: if the message comes back, reinstall FuzeVPN with the installer from the FuzeVPN for Windows page, which also offers “Repair”. Your preferences are kept; at the next sign-in, a new device is added automatically.
For the other Android messages in this family: if the message comes back, clear FuzeVPN’s data or reinstall it. After a reinstall, a new device is added automatically at the next sign-in. If the device limit is reached, the app simply asks you to remove one.
For “Local account settings are unavailable” (extension): close and reopen the browser. Check that there is still free space on the disk, then try again. Your saved account is kept.
For messages from the Windows and Android apps: if the message comes back, run diagnostics. On Windows, open the “Diagnostics” page in the sidebar menu, then click “Diagnostics”. On Android, open Account → “Need help?” → “Run diagnostics”.
For “Local account settings are unavailable”: if the message comes back, open “Settings → Support → Diagnostics” in the extension. Then choose “Run diagnostics”.
If you are signed in to your account, send the report: Windows sends it automatically; on Android, tap “Send the report”, and in the extension, “Send report”. If you are not signed in, copy its text on Windows, or choose “Save report” on Android or “Export report” in the extension.
Then write to support at contact@fuzevpn.com, with the report reference shown after sending. If you are not signed in, attach the saved or exported report, or paste its text. Add the exact message and its code, if it appears below the message (Android) or on the “Diagnostics” page (Windows).
Messages
The saved session could not be cleared. Try signing out of your account again.
Windows app
Windows could not open WireGuard’s protected storage.
Windows app
Access to protected storage failed. Restart the app, then contact support if the problem persists.
Windows app
FuzeVPN protected storage cannot be used. Try again.
Windows app
Your saved session could not be read. Try verifying it again.
Windows app
Could not generate OpenVPN CSR — Android Keystore could not create or sign the OpenVPN P-256 CSR.
Android app
Could not generate WireGuard key — Android could not create or read the WireGuard key in secure storage.
Android app
Could not create OpenVPN CSR — The Android Keystore key could not sign the OpenVPN certificate request.
Android app
OpenVPN identity not saved — The OpenVPN certificate or profile could not be saved in encrypted storage.
Android app
Could not create OpenVPN P-256 key — Android Keystore could not create or read the non-exportable P-256 private key.
Android app
Secure read failed — Android Keystore could not decrypt this account’s local data.
Android app
Secure write failed — Android Keystore could not encrypt or save the local data.
Android app
Storage key rejected — The Android bridge blocked a key outside the allowed storage list.
Android app
Invalid local WireGuard key — This account’s encrypted WireGuard key is unreadable or invalid.
Android app
WireGuard identity not saved — Android could not save this account’s encrypted WireGuard identity.
Android app
Your session could not be secured on this device. Try again.
Android app
The VPN is stopped, but session removal is not confirmed. Retry cleanup.
Android app
Setting or favourite not saved or not loaded
A choice could not be saved on the device, or favourites or security settings could not be read. Choices concerned: language, theme, notifications, protocol, server, favourite, launch with Windows, automatic connection, security settings, reports.
Depending on the case, the previous choice comes back, or the new one applies for now and trying again lets you keep it. If the security settings cannot be read, they return to their default values: all turned on.
To do
For “The saved security settings cannot be read…”: the protection if the connection drops (kill switch), DNS protection, WebRTC protection and automatic reconnection are turned on, as by default. To make your choices again, disconnect the VPN. “Kill switch”, “DNS protection” and “WebRTC protection” are in “Settings → Privacy → Security”, and “Automatic reconnection” in “Settings → Connection → Connection”.
For “The VPN protocol could not be saved…” or “The security settings could not be saved”: first click “Disconnect” and wait for confirmation. Then make your choice again. The protocol is set in “Settings → Connection → VPN protocol”, and the protections in “Settings → Privacy → Security”.
For “This choice could not be saved. It may be lost when the app restarts.”: check that you are still signed in to your FuzeVPN account, then make this choice again.
For “Launch with Windows could not be changed”: from your usual Windows session, set “Launch with Windows” again, in “Settings → General → Windows”.
Try again: make the same choice again.
For “…favorite could not be saved…”: add or remove this favourite again. Your list has returned to its last saved state.
For “Favorites could not be loaded” (Android): try again. Once the list has loaded, you can add or remove favourites again.
For “Preference not saved” (Android): your choice applies for now. Try again before closing the app to keep it.
For “This setting could not be saved” (Android, diagnostics reports): try again. Then check the setting shown before sending a report.
For “The language…”, “The theme…”, “The selected server…”, “This favorite…”, “Automatic connection…” or “The security settings…” / “The saved security settings…”: if it fails again, quit FuzeVPN with “Quit FuzeVPN”, in the menu of its icon near the clock, then reopen it. Then check that your choice has been kept.
If the message still comes back, run diagnostics. On Windows, open the “Diagnostics” page in the sidebar menu and click “Diagnostics”: the report is sent if you are signed in to your account. On Android, in Account, tap “Need help?”, “Run diagnostics”, then “Send the report”.
Then write to support at contact@fuzevpn.com, with the exact message, its code if it appears and the report reference. If you are not signed in, attach the report kept with “Save report” on Android, or paste its text on Windows.
Messages
This choice could not be saved. It may be lost when the app restarts. Try again.
Windows app
The notification preference could not be saved.
Windows app
The language could not be saved on this computer.
Windows app
The VPN protocol could not be saved on this computer.
Windows app
This favorite could not be saved on this computer.
Windows app
Launch with Windows could not be changed.
Windows app
The saved security settings cannot be read. Default protections remain enabled.
Windows app
The security settings could not be saved.
Windows app
The selected server could not be saved on this computer.
Windows app
The theme could not be saved on this computer.
Windows app
Automatic connection could not be saved.
Windows app
This setting could not be saved. Try again.
Android app
Favorites could not be loaded. Try again.
Android app
The favorite could not be saved. Try again.
Android app
Preference not saved — Your choice is applied for now, but could not be saved. Try again to keep it after closing the app.
Android app
Windows: update rejected by FuzeVPN’s checks
FuzeVPN checks for an update at startup, and you can check for one in “Settings → Updates”. Before installing it, FuzeVPN checks the response from the update service, the file received and the installed version.
In the file, it verifies the signature in FuzeVPN’s name, the fingerprint, the version, the processor, the size and the download address. Here, a check failed: for most of these messages, the cause is the published file, not your PC.
To do
For “The update signature could not be verified”: first check that the Windows date and time are correct.
For “Windows could not open the installed version of FuzeVPN”: quit FuzeVPN with “Quit FuzeVPN”, in the menu of its icon near the clock, then reopen it. Also check that your antivirus is not blocking FuzeVPN. If it is, report this false positive to it, as explained in the article on installing on Windows.
FuzeVPN won’t install, won’t start or doesn’t get Windows permission
For “This update is not compatible with this computer”: install the Windows updates, then try again. This update may require a more recent version of Windows. Also check that your PC is supported: Windows 10 or 11, x64 or ARM64 processor, not in S mode.
For “The received file is not compatible with this computer’s architecture”: manually install the x64 or ARM64 version that matches your PC, as explained in steps 7 and 8. It is the published file that does not match your processor.
For “The update file exceeds the allowed size”: the size in question is that of the published file, not the free space on your disk.
In “Settings → Updates”, click “Check for updates”, then “Download update” and “Install now”. If the same message comes back, try again later.
If the message comes back, install the latest version manually with the installer from the FuzeVPN for Windows page. It performs the update and keeps your preferences. The Microsoft Store version updates through the Store.
Take the installer for your processor, x64 or ARM64, as shown in the Windows system information. If the installed version is not the right one, uninstall it first. For the portable version, follow the article on updating on Windows.
If the message still comes back, open the “Diagnostics” page in the sidebar menu and click “Diagnostics”. The report is sent if you are signed in to your account.
Then write to support at contact@fuzevpn.com, with the exact message, the time, its code if it appears and the report ID. If you are not signed in, paste the report text into your email. We reply within 72 hours, in your language.
Messages
The update service response is invalid.
Windows app
The download was redirected to an unauthorized address.
Windows app
Windows could not open the installed version of FuzeVPN.
Windows app
The publisher of the received file does not match FuzeVPN.
Windows app
The server returned an empty file.
Windows app
The update file exceeds the allowed size.
Windows app
The downloaded file does not match the announced update.
Windows app
This update is not compatible with this computer.
Windows app
The update download address is invalid.
Windows app
The update signature could not be verified.
Windows app
The SHA-256 of the received file differs from the announced value.
Windows app
The received file is not compatible with this computer’s architecture.
Windows app
The version of the received file differs from the announced version.
Windows app
Windows: diagnostics results
FuzeVPN for Windows diagnostics check the VPN engine, the driver, the VPN certificate, the tunnel, the protections and access to the FuzeVPN service. These lines report a failed check or a measurement that could not be taken.
A protection you have turned off shows “Not run”. The tunnel can work even if the service does not respond.
To do
For “The VPN engine is unavailable…”: quit FuzeVPN with “Quit FuzeVPN”, in the menu of its icon near the clock, then reopen it. If the line comes back, restart Windows.
For “Manually disconnect and reconnect the VPN…” or “The VPN certificate is not confirmed…”: click “Disconnect” and wait for confirmation. Then start the VPN connection again.
For “Check your Internet connection…”: open a website to check that your connection works, disconnecting the VPN first if needed. The tunnel can work even if the FuzeVPN service, called “the API” here, does not respond.
For “This protection is not confirmed…”: the line concerns the protection if the connection drops (kill switch), which is turned on. Its check failed or its result is unknown. Run diagnostics again, then write to support at contact@fuzevpn.com if the line remains.
For “The service returned an HTTP error response…”: wait a moment, then run diagnostics again. If the line still shows an error, note the code shown, then sign in to your account again. Also check that your subscription is active, as explained in the articles on expired sessions and on the subscription required.
FuzeVPN asks me to sign in again: session expiredFuzeVPN asks me for a subscription when I already have one
Wait until no VPN connection or disconnection is in progress, then run diagnostics again.
For “The VPN certificate is not confirmed…”: if you use OpenVPN, also see the article on revoked or expired OpenVPN profiles.
For “The VPN driver needs to be checked…”: write to support at contact@fuzevpn.com with the report ID shown after sending. If you are not signed in, paste the report text instead. After analysis, support may ask you to reinstall FuzeVPN.
If a line remains failed or undetermined, write to support at contact@fuzevpn.com quoting the line and its codes: “Error code”, “HTTP”, “TLS” or “Windows code”. Add the ID of the report sent, or paste its text if you are not signed in to your account. Also include the FuzeVPN version if it is visible.
Messages
The VPN engine is unavailable. Restart the app. Contact support if the problem persists.
Windows app
This measurement is unavailable. Run diagnostics again. If it remains unknown, contact support.
Windows app
Manually disconnect and reconnect the VPN, then run diagnostics again. Contact support if the problem persists.
Windows app
The VPN driver needs to be checked. Contact support before changing it.
Windows app
The received response could not be interpreted. Check the error code.
Windows app
The VPN certificate is not confirmed. Retry the VPN connection, then contact support if the problem persists.
Windows app
Check your Internet connection, then run diagnostics again. The tunnel may work even if the API does not respond.
Windows app
The service returned an HTTP error response. Check the error code.
Windows app
This check failed. Run diagnostics again. Contact support if the problem persists.
Windows app
This protection is not confirmed. Do not assume traffic is blocked. Check the settings and contact support if the problem persists.
Windows app
FuzeVPN service unreachable or unexpected error
The app or extension could not reach the FuzeVPN service, or sent a request that was judged invalid. It may also have received an unexpected or overly slow response, or run into an error the message does not specify.
On Windows, the network or its configuration on the computer can also prevent the app from reaching the service.
To do
Try again, with no waiting period. The Locations section of the site’s home page shows the servers in real time, with their ping.
For “Invalid request”: check what you entered, then try again.
For “The network connection attempt failed”: check that the Internet works without the VPN, by disconnecting the VPN and then opening a website. You can also try another network. Then try again.
For “FuzeVPN cannot use this computer’s network configuration…”: check that the Internet works. Quit FuzeVPN with “Quit FuzeVPN”, in the menu of its icon near the clock, then reopen it and try again.
For “The network connection attempt failed” or “FuzeVPN cannot use this computer’s network configuration…”: if the message comes back, remove this device from your account. As a last resort, reinstall the app with the installer from the FuzeVPN for Windows page.
For “Invalid server response” or “Invalid request” (Android): update the app on Google Play, or install the new APK installation file from the Download page over the old one. To switch from Google Play to the APK, or the other way round, uninstall the app first. Then try again.
If the message comes back, run diagnostics. On Windows, open the “Diagnostics” page in the sidebar menu and click “Diagnostics”. On Android, in Account, tap “Need help?”, “Run diagnostics”, then “Send the report”.
In the extension, open “Settings → Support → Diagnostics”. Click “Run diagnostics”, then “Send report”.
For “An unexpected error occurred” (extension): also export the connection log with “Export connection log”, in the same section. Attach it to your email to support.
Then write to support at contact@fuzevpn.com, with the exact message, its code if it appears and the report reference. If you are not signed in, attach the report kept with “Save report” (Android) or “Export report” (extension), or paste its text (Windows). We reply within 72 hours, in your language.
Messages
The check did not complete. The cause has not yet been identified.
Windows app
The network connection attempt failed. This does not establish whether the service is unavailable.
Windows app
FuzeVPN cannot use this computer’s network configuration to reach the service.
Windows app
Invalid server response — The server returned an unexpected response. Try again later.
Android app
Invalid request — Check the entered information and try again.
Android app
Service unavailable — A server error occurred. Try again later.
Android app
Operation failed — The operation could not be completed. Try again or send the diagnostic code to support.
Android app
The service took too long to respond. Try again.
Browser extension
The service returned an unexpected response.
Browser extension
An unexpected error occurred. Try again.
Browser extension
This operation is no longer available. Try again.
Browser extension