Package Details: windscribe-cli 1.4_51-1

Git Clone URL: (read-only, click to copy)
Package Base: windscribe-cli
Description: Port of Windscribe's command line interface
Upstream URL:
Keywords: CLI VPN Windscribe
Licenses: GPL
Submitter: hkuchampudi
Maintainer: hkuchampudi
Last Packager: hkuchampudi
Votes: 92
Popularity: 0.27
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 ( Alternatively you can post to the official subreddit (

If you have found an issue with the packaging, please open an issue on GitHub ( with clear steps to reproduce the error and any relevant logs. Thanks!

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

jimdunn commented on 2018-02-20 19:55

@hkuchampudi, thank you for such a great script!!!

damien commented on 2018-01-21 00:26

Surprisingly the windscribe log didn't show any errors. I've actually found that I had a lot of bad sectors on my main drive so I've reinstalled Arch on another drive and things seem to be working well again, so I'm assuming that was the problem. Thanks for replying and sorry about the noise.

hkuchampudi commented on 2018-01-12 23:55


Hmmm... I have never experienced this problem with my setup. So, to be clear, are you saying that when you run sudo systemctl start windscribe.service systemd is showing an error when you check the status of the service? Just guessing based on the error you posted, it sounds like you are getting a malformed JSON response when the windscribe service tries to authenticate with windscribe servers. Have you checked your windscribe log; what does it say?

damien commented on 2018-01-10 13:59

Hi, I'm not sure when this started but I haven't been able to start the windscribe service for a while. I am getting this error when I try to manually start it in the terminal:

Traceback (most recent call last): File "windscribe/", line 60, in <module> File "click/", line 115, in decorator File "click/", line 89, in _make_command File "windscribe/", line 39, in init File "windscribe/", line 208, in init File "windscribe/", line 35, in init File "json/", line 339, in loads File "json/", line 364, in decode File "json/", line 382, in raw_decode ValueError: No JSON object could be decoded Failed to execute script windscribe</module>

Is anyone else having this issue?

damien commented on 2017-11-17 15:01

Hi hkuchampudi, your change seems to work great now. Thanks!

hkuchampudi commented on 2017-11-17 14:33

In the latest update, I have modified the windscribe-cli systemd service to include 'ExecStop=/usr/bin/windscribe stop' to shutdown the windscribe daemon. This should ensure that the service shuts down and should prevent system hang-ups on shutdown and reboot

hkuchampudi commented on 2017-11-16 23:16


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:

Description=Windscribe VPN CLI Service

ExecStart=/usr/bin/windscribe start
ExecStop=/usr/bin/windscribe stop


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!