What are known issues with the current version of NymVPN? (June 2025)

Below is a list of known issues currently affecting NymVPN, and what you can do to fix them.

"failtogethealth" error when connecting

Some users are seeing a "failtogethealth" error when attempting to connect.

This is a known issue and the team is actively working on a fix.
In most cases, disconnecting and then reconnecting to NymVPN temporarily resolves the issue.

We appreciate your patience and will update this article once the issue is resolved.

Daemon & Startup Issues

NymVPN doesn’t connect after reboot or first-time setup

On some Linux, macOS, and Windows devices, NymVPN may fail to connect after the device is restarted or during first-time setup. This is often due to the system daemon not starting automatically. If this occurs, restarting the daemon manually usually restores connectivity.

• Linux
  Run: sudo systemctl restart nym-vpnd.service
• macOS
  Open Activity Monitor, search for "Nym", and find the Nym-VPN-Helper process. Quit this process, then reopen the app and reconnect as you normally would.
• Windows
  1. Open the start menu
  2. Type services.msc and select the Services system console (should be the top search result).
  3. In the Services Console, find NymVPN Service right click and select Restart.
  NymVPN should now be able to connect connect successfully.

We’re actively working on improving daemon reliability across platforms.

Network Issues 

We are currently working on improving our NymVPN network services, but you may encounter the following issues: 

• "What's my IP Address" services show a different location than the one selected in NymVPN

Each NymVPN server's location is inferred based on its IP address by our IP geolocation system. The actual location may slightly differ from what is displayed in the app, but this is continuously being improved. You can visit our help article on "How is server location determined by NymVPN" to understand more about geolocation and how this works on NymVPN.

• When trying to connect to the same entry/exit gateway I receive the following error: "NymVPN won't use the same gateway for entry and exit. Reconnect or choose different locations."

To safeguard your privacy, NymVPN does not allow your traffic to be routed through the same entry and exit gateways to protect privacy against possible surveillance threats. However, in locations with few gateways, the random gateway selection made by NymVPN may result in the same gateway being selected twice, which triggers this error message. Try reconnecting or selecting a different set of entry/exit locations.

• NymVPN disconnects after 1–2 hours of use

Some users report losing connection after 1 to 2 hours of continuous use, even though the app initially connected successfully. This may occur without warning, and users often notice only when internet traffic stops. We are actively investigating this issue to improve long-term connection stability.

• NymVPN is causing high CPU/Battery usage

You may notice increased battery consumption and higher CPU usage when NymVPN is connected. Our team is aware of this and is actively working on optimizations to reduce battery and processing demands. Please note that the Anonymous mode (mixnet) consumes more data and resources, which may contribute to higher battery usage. 

• The Anonymous mode (mixnet) is slow

The Anonymous mode prioritizes privacy over speed, which makes it unsuitable for high-bandwidth and low-latency activities like browsing and streaming. Consider using this mode for latency-tolerant apps and traffic like messengers, email, and crypto wallets.

• NymVPN cannot connect due to the error "Could not authenticate and start up the gateway connection - gateway returned an error response: provided request timestamp is in the future."

You need to sync your device's clock or make sure that you are using the correct timezone settings when attempting to connect to NymVPN.

• Connection gets stuck on "Connecting"

On Windows and some other desktop platforms, the app may occasionally get stuck in a "Connecting" state without displaying an error message. If this happens, try restarting the app or selecting different gateway locations. We are actively investigating the cause of this behavior.

Some users may also see a vague "no connection" or "connectivity" error when attempting to connect. Restarting the app or trying a different server combination may temporarily resolve this.

• Slow speeds or app/website incompatibility in VPN mode

Some users may experience reduced speeds or difficulty using certain websites or apps when connected in Wireguard mode. We're actively monitoring and optimizing performance and compatibility.

Bandwidth & Usage

• Monthly bandwidth limit warning despite low usage

Some users report seeing a “monthly bandwidth exceeded” warning even if they haven’t used 2 TB of data. This is due to how bandwidth is tracked using cryptographic tickets. Learn more here.

Platform-Specific Issues

Linux 

• Daemon error when connecting / Red dot on the top left of the NymVPN app

This is due to daemon service not running, e.g. exited because of an error, crashed or it is not installed. Please uninstall NymVPN manually and reinstall it after removing all its files. See How to uninstall NymVPN on any Linux distribution for more tips.

• Daemon not connected error when using Flatpak or AppImage on Fedora and similar distributions

The Flatpak and AppImage packages include only the client app. To use the app successfully, you must also install the daemon using one of the other available installation methods (such as from a .deb, AUR, or via the raw binary available in the GH repository releases.). Without the daemon running, the app will not connect.

Flatpak users should also be aware of a known limitation: if the daemon is restarted while the app is still open, the app may not reconnect due to Flatpak’s sandboxing. Fully restarting the app will resolve this.

• App opens with blank screen

On some Linux systems (like Fedora or OpenSUSE Tumbleweed), the NymVPN app may open with a blank window due to a Tauri-related issue. If the app logs show the error:

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

then this is a known problem. There is currently no fix upstream, and it is outside of our control. The recommended workaround is to use an alternative client - either your system package (e.g. .deb or AUR) or the Flatpak version, which is not affected.

Android

• VPN disconnects when device is idle

On some Android devices — including those running GrapheneOS — NymVPN may disconnect after the device is locked or during regular use. The app may appear connected, but traffic may not reach the internet. We're actively investigating this issue.

Windows 

• Firewall-related connection issues

Some users report connection problems due to Windows firewall interference. This is under active review.

• Daemon error when connecting / Red dot on the top left of the NymVPN app

This is due to the daemon not installing correctly. Please uninstall NymVPN manually and reinstall it after removing all its files. You can visit our help article on Why do I experience a "daemon not connected" error on Windows?

Cross-Platform Compatibility

• Certain websites not loading in Anonymous mode

Some users on MacOS, Windows, and Linux report that specific websites (e.g., DuckDuckGo, UPS) may not load properly when using the mixnet. We're investigating improvements for compatibility.

If you encounter any errors or bugs not listed above, please submit a ticket by clicking the Get in Touch button and choosing the option that best describes your issue.