Package Details: windscribe-cli 1.4_51-1

Git Clone URL: https://aur.archlinux.org/windscribe-cli.git (read-only)
Package Base: windscribe-cli
Description: Port of Windscribe's command line interface
Upstream URL: https://windscribe.com/
Keywords: CLI VPN Windscribe
Licenses: GPL
Submitter: hkuchampudi
Maintainer: hkuchampudi
Last Packager: hkuchampudi
Votes: 80
Popularity: 1.50
First Submitted: 2017-07-29 18:12
Last Updated: 2019-07-23 05:30

Pinned Comments

hkuchampudi commented on 2018-11-07 04:12

Note: I am only the packager of this application. If you are experiencing issues with the application itself (that do not stem from how the application is packaged), please submit a support request to Windscribe directly (https://windscribe.com/support). Alternatively you can post to the official subreddit (https://www.reddit.com/r/Windscribe/).

If you have found an issue with the packaging, please open an issue on GitHub (https://github.com/hkuchampudi/Windscribe/issues) with clear steps to reproduce the error and any relevant logs. Thanks!

Latest Comments

« First ‹ Previous 1 2 3 4 5

hkuchampudi commented on 2017-11-16 23:16

@damien

Yes, I have run into this issue before; it looks like the binary doesn't want to play nice with systemd. I have been planning on committing some changes to the systemd service file, but have not gotten around to it.

Namely, I am going to change the contents of '/etc/systemd/system/windscribe.service' to the following:

[Unit]
Description=Windscribe VPN CLI Service
After=syslog.target network.target remote-fs.target nss-lookup.target

[Service]
Type=simple
ExecStart=/usr/bin/windscribe start
ExecStop=/usr/bin/windscribe stop
Restart=on-failure
KillMode=control-group
SuccessExitStatus=SIGKILL
PIDFile=/etc/windscribe/windscribe.pid

[Install]
WantedBy=multi-user.target

If you want to give this a try and report back, that would help me out. After making the changes to the windscribe.service file you will need to run 'sudo systemctl daemon-reload'

damien commented on 2017-11-16 13:36

Hi, does anyone else have problems stopping the Windscribe service? It's annoying because when I shut down or reboot, systemd will wait 1m30s trying to stop this service. Also, when I run "systemctl stop windscribe.service" it takes a while and when I check the status I see:

$ systemctl status windscribe.service
● windscribe.service - Windscribe VPN CLI Service
Loaded: loaded (/etc/systemd/system/windscribe.service; enabled; vendor preset: disabled)
Active: failed (Result: timeout) since Thu 2017-11-16 14:32:04 CET; 4s ago
Process: 15480 ExecStart=/usr/bin/windscribe start (code=killed, signal=KILL)
Main PID: 15480 (code=killed, signal=KILL)

Nov 16 14:30:23 zal systemd[1]: Started Windscribe VPN CLI Service.
Nov 16 14:30:25 zal windscribe[15475]: Starting windscribe ... OK
Nov 16 14:30:34 zal systemd[1]: Stopping Windscribe VPN CLI Service...
Nov 16 14:32:04 zal systemd[1]: windscribe.service: State 'stop-sigterm' timed out. Killing.
Nov 16 14:32:04 zal systemd[1]: windscribe.service: Killing process 15480 (windscribe) with signal SIGKILL.
Nov 16 14:32:04 zal systemd[1]: windscribe.service: Main process exited, code=killed, status=9/KILL
Nov 16 14:32:04 zal systemd[1]: windscribe.service: Failed with result 'timeout'.
Nov 16 14:32:04 zal systemd[1]: Stopped Windscribe VPN CLI Service.


Any ideas? Looks like Windscribe doesn't respond when being stopped nicely so systemd eventually just uses SIGKILL? Nobody else is experiencing this?

hkuchampudi commented on 2017-09-17 22:07

@manyak Looking at your log, it looks like there is a problem starting with line 80 (and repeated in lines 83, 90, and 93) which talks about a connection error. I believe that this error only appears when there is some networking issue and the computer cannot connect to the specified host. I would double check your Internet connection and firewall rules to make sure that your computer can connect to the host over the specified port. I just tried connecting to the Germany endpoint and I am having no issues on my end.

EDIT: Also, I don't believe you are on a PRO plan based on your log. Make sure that you have not used-up all of your allocated bandwidth for the month.

bdodroid commented on 2017-08-16 14:57

@hkuchampudi Not sure if it was the reboot or if windscribe's servers where having problems like you suggested but it's working now.

Thanks for your help!

hkuchampudi commented on 2017-08-15 16:43

@bdodroid There could be a couple reasons. From time to time Windscribe servers experience problems and it is impossible to connect to the servers. Also check your firewall rules to make sure that VPN traffic is being permitted over the specified protocol and port. If it is not a configuration error on your end, I would say wait a while and try connecting again. All else fails, you can send your debug log to Windscribe and open a support ticket (https://windscribe.com/guides/linux).

Additionally, take a look at your log by using `windscribe viewlog` to identify where it may be failing.

bdodroid commented on 2017-08-15 16:15

Everything runs fine until I try to connect, then I get a "Failed to connect" message and it exits. Any ideas what could be stopping the connection?

It gets my account info just fine.

My Linux version: Linux 4.12.4-1-ARCH x86_64 GNU/Linux

hkuchampudi commented on 2017-08-01 20:35

@f4bio Thanks for letting me know, I forgot to add this when I was refactoring the PKGBUILD. Everything should work now.

f4bio commented on 2017-08-01 20:20

you have to create `/etc/windscribe` directory somewhere in your the PKGBUILD too, otherwise it won't start (`IOError: [Errno 2] No such file or directory: '/etc/windscribe/wssession'`)