Known Issues

This page documents known issues, and solutions.

Linux app split tunneling

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.

Linux CLI not autoconnecting or disconnecting after user logs out of system

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.