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.60
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 Next › Last »

da99 commented on 2018-04-08 01:04

@damien @hkuchampudi

I had the same problem as Damien (ie Python/JSON error). I solved it by removing the directory: /etc/windscribe. (Just to be safe, I renamed it: /etc/windscribe_tmp). Everything works fine now. (I'm on VoidLinux, but this solution should work for Arch too.)

In my case, the file /etc/windscribe/wssession was empty. That file is supposed to be filled with JSON data. Which might explain the Python/JSON error.

UPDATE: Just remove the wssession file. Removing the directory isn't necessary: sudo rm /etc/windscribe/wssession

hkuchampudi commented on 2018-04-05 03:26

Updated package to install the latest v1.1 beta release for Linux

New Features: - City level selection - Stealth mode - Proxy support - IPV6 firewall - LAN traffic firewall bypass - MANY bug fixes - x86 and ARM support

windscribe commented on 2018-04-04 23:23

New version is out (1.1). There are a bunch of new features (City level selection, stealth mode, proxy support, ipv6 firewall, LAN traffic firewall bypass, MANY bug fixes, x86 and ARM support). The binaries are available here: https://windscribe.com/guides/linux

taloa commented on 2018-03-29 07:37

how to fix this? root@localhost:~# windscribe login Traceback (most recent call last): File "windscribe/windscribe.py", line 498, in <module> File "click/core.py", line 722, in call File "click/core.py", line 697, in main File "click/core.py", line 1066, in invoke File "click/core.py", line 895, in invoke File "click/core.py", line 535, in invoke File "windscribe/WSDaemonCLI.py", line 73, in subcommand File "daemonocle/core.py", line 608, in do_action File "windscribe/WindscribeCLI.py", line 663, in login File "windscribe/WindscribeShelve.py", line 35, in init File "json/init.py", line 339, in loads File "json/decoder.py", line 364, in decode File "json/decoder.py", line 382, in raw_decode ValueError: No JSON object could be decoded Failed to execute script windscribe root@localhost:~# </module>

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

@damien

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/windscribe.py", line 60, in <module> File "click/decorators.py", line 115, in decorator File "click/decorators.py", line 89, in _make_command File "windscribe/WSDaemonCLI.py", line 39, in init File "windscribe/WindscribeCLI.py", line 208, in init File "windscribe/WindscribeShelve.py", line 35, in init File "json/init.py", line 339, in loads File "json/decoder.py", line 364, in decode File "json/decoder.py", 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