-
Notifications
You must be signed in to change notification settings - Fork 122
Known Issues
This page documents known issues, and solutions.
Sometimes picking the app from the pre-populated list does not work. This list is populated from the .desktop files on your system, and they may point to a shell script or a launcher. This happens most frequently with Firefox on various distros (Fedora, Mint, others). In this case, the script or launcher would be split tunneled rather than the actual app, which would appear to have no effect.
If this happens, find out the actual binary that is running when the application is run, e.g. with ps aux | grep firefox. This may tell you that firefox is actually /usr/lib/firefox/firefox-bin. You can then use the + icon in Split Tunneling / Apps and add this path manually.
For security reasons, the pure CLI windscribe service runs as an user service. This means, by default, if the user is not logged in, the windscribe service will also not start, and thus will not connect to VPN even if autoconnect is enabled. If you want to start user services at boot and have them continue to run after the user logs out, you can enable user linger with loginctl enable-linger (or loginctl enable-linger <user>, as root). Autoconnect also did not work correctly in this scenario before version 2.13.3, so makes sure you have a version later than this one.
If you have the "Unlock Streaming" feature enabled in your Windscribe account, we do some magic on the backend to make streaming work. As a part of this, we may resolve addresses that you connect to, which leads sites like browserleaks.com/ipleak.net etc to detect it as a DNS server, even if you configured a custom one.
This is not a DNS leak as it occurred at the VPN server, and is expected behaviour when you enable the feature. If you really don't like it, you can disable "Unlock Streaming" from your account.
Due to an OS bug, when the split tunneling extension is started, macOS may interrupt existing TCP connections on the system. This causes TCP-based VPN protocols to break (TCP, Stealth). To work around this, disable split tunneling or use another protocol. This was fixed in macOS Sonoma (14.x).
The 'unlock streaming' feature of your Windscribe account will prevent HTTP/3 from working while the VPN is connected. This feature is enabled by default, so please turn it off in your account settings on the website if you require HTTP/3 to work while connected.
The Windscribe firewall uses OS-provided frameworks (WFP on Windows, PF on macOS, nftables on Linux) to block undesirable traffic and prevent leaks. If you have other programs with administrative privileges which may override Windscribe's rules, you may cause leaks to occur. For example, installing docker on Linux will enable rules which allow container traffic to bypass the firewall.
Some applications will aggressively reinstate its rules if modified, and we don't want to get into a loop where we are trying to assert our rules while another app asserts theirs. As such, before reporting a leak, please ensure that you have disabled any applications in your environment which may touch the firewall.