Package Details: windscribe-v2-bin 2.11.11-1

Git Clone URL: https://aur.archlinux.org/windscribe-v2-bin.git (read-only, click to copy)
Package Base: windscribe-v2-bin
Description: Windscribe GUI tool for Linux
Upstream URL: https://windscribe.com/guides/linux
Keywords: gui vpn windscribe
Licenses: GPL2
Conflicts: windscribe, windscribe-cli
Provides: windscribe
Submitter: blocklisted
Maintainer: tk154
Last Packager: tk154
Votes: 31
Popularity: 0.149097
First Submitted: 2022-01-02 21:01 (UTC)
Last Updated: 2024-09-17 08:29 (UTC)

Pinned Comments

blocklisted commented on 2023-01-06 14:22 (UTC) (edited on 2023-01-06 14:25 (UTC) by blocklisted)

NOTE: It may be necessary to enable systemd-resolved for windscribe to work. It may fail silently without it. NetworkManager also works fine according to some reports.

Latest Comments

1 2 Next › Last »

rkochar commented on 2024-04-03 06:12 (UTC)

If your internet has severe problems because of this package, see this thread

nuc commented on 2024-02-25 13:27 (UTC)

My experience with NetworkManager (on kde) is not so good. Windscribe gui often complains that "something is interfering" with it's network. Often it will not work correctly. Sometimes I will be unable to access local networks unless I enable Windscribe (like access to my printer). After coming back from suspend/sleep state it is also not working correctly. I have to restart the NetworkManager or windscrbe-helper services.

nrozman21 commented on 2024-01-01 20:44 (UTC)

Hello David, it looks like this is the intended behavior when the killswitch is enabled.

daviding commented on 2023-12-26 05:05 (UTC) (edited on 2023-12-26 05:06 (UTC) by daviding)

Installing Windscribe causes a change to the iptables that disables Internet access.

-- begin sample --

[redacted@m5a88-m ~]$ sudo iptables -nvL [sudo] password for redacted :

Chain INPUT (policy ACCEPT 91468 packets, 786M bytes) pkts bytes target prot opt in out source destination
137 16215 windscribe_input 0 -- * * 0.0.0.0/0 0.0.0.0/0 / Windscribe client rule /

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 50418 packets, 4112K bytes) pkts bytes target prot opt in out source destination
584 93914 windscribe_output 0 -- * * 0.0.0.0/0 0.0.0.0/0 / Windscribe client rule /

Chain windscribe_input (1 references) pkts bytes target prot opt in out source destination
0 0 ACCEPT 0 -- lo * 0.0.0.0/0 0.0.0.0/0 / Windscribe client rule / 0 0 ACCEPT 0 -- * * 103.62.48.130 0.0.0.0/0 / Windscribe client rule / 0 0 ACCEPT 0 -- * * 74.80.180.194 0.0.0.0/0 / Windscribe client rule / ...

Chain windscribe_output (1 references) pkts bytes target prot opt in out source destination
0 0 ACCEPT 0 -- * lo 0.0.0.0/0 0.0.0.0/0 / Windscribe client rule / 0 0 ACCEPT 0 -- * * 0.0.0.0/0 103.62.48.130 / Windscribe client rule / 0 0 ACCEPT 0 -- * * 0.0.0.0/0 74.80.180.194 / Windscribe client rule / ...

-- end sample --

I've included the entire iptables response at https://pastebin.com/j0ihFZnr

To regain Internet access, I execute ...

sudo iptables -F

pienapin commented on 2023-11-21 03:11 (UTC)

Why does it need sudo? I am using doas and I deleted the sudo from the dependency list, and it works fine

jmcb commented on 2023-11-04 16:32 (UTC)

Nov 04 16:28:40 hearth systemd[1]: Configuration file /etc/systemd/system/windscribe-helper.service is marked executable. Please remove executable permission bits. Proceeding anyway.

blocklisted commented on 2023-01-06 14:22 (UTC) (edited on 2023-01-06 14:25 (UTC) by blocklisted)

NOTE: It may be necessary to enable systemd-resolved for windscribe to work. It may fail silently without it. NetworkManager also works fine according to some reports.

nrozman21 commented on 2022-12-15 12:04 (UTC)

Please see this package for a beta version of Windscribe: https://aur.archlinux.org/packages/windscribe-beta-bin