| Git Clone URL: | https://aur.archlinux.org/windscribe-cli.git (read-only, click to copy) |
|---|---|
| Package Base: | windscribe-cli |
| Description: | Port of Windscribe's command line interface |
| Upstream URL: | https://windscribe.com/ |
| Keywords: | CLI VPN Windscribe |
| Licenses: | |
| 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 |
New features
À la carte location support (future feature)
Fixed bugs
iptables command output to debug log
Whitelist Windscribe API IPs in the firewall
Better handling of AUTH_FAILED
Reconnect after sleep mode
Malformed json in wssession
Don’t make needless API calls when disconnected
https://blog.windscribe.com/windscribe-linux-1-2-changelog-75f9d57291e3
We just pushed out an update that addresses the bugs mentioned here, and a few other ones. The changelog is on our blog.
@windscribe Yes, it occurs in "Windscribe CLI client v1.1 BETA". The steps to reproduce:
sudoedit /etc/windscribe/wssession (Remove all content. Write as an empty file.)
sudo windscribe start # error: The same stack trace as the previous windscribe 1.0 binary.
sudo rm /etc/windscribe/wssession
sudo windscribe start # It works.
(Thanks for your attention and putting up with my cynical, bitter attitude of the world. I did forget to mention the Windscribe has been great and keeps getting better.)
@da99 - We totally DO care about Linux users, that's why this app exists. Does this issue occur in the latest version (1.1)?
@hkuchampudi
After re-naming /etc/windscribe, I ran "sudo windscribe start". (I haven't used windscribe as a service. I'm on VoidLinux.) The binary re-created the /etc/windscribe directory with the proper JSON wssession file. The files were all owned by root:root (readable by all, editable only by root).
I suspect this is a bug in the windscribe binary and not in your package. Probably their server gave an error at one point and the file was not properly written.
I'm not going to report the error to Windscribe. I doubt they will care about Linux users. Their more profitable customers will probably be non-programmers on Windows, Macs, and Android.
Thank you for all your hard work. It's not easy maintaining anything, especially software that runs on all sorts of exotic systems.
@da99 Thanks for doing some additional investigation. After testing what you said, the error that you and @damien received does seem to stem from an empty wssession file. However I am unable to naturally reproduce this issue on my installation of Arch or a clean installation of Antergos Linux.
In order to replicate an empty wssession file, I first installed the windscribe-cli package using yaourt. After the installation process is complete, the directory /etc/windscribe should be present but empty. Next, I started the windscribe service using sudo systemctl start windscribe (which in turn executes /usr/bin/windscribe start). After starting the service, there are now 4 files in the /etc/windscribe directory: windscribed, windscribe.pid, wsout, wssession. At this point, the contents of wssession should be an empty JSON: {}. After starting the service, I am successfully able to login and use windscribe. After logging in, wssession fills up with metadata.
Next, in order to test the issue, I manually deleted the contents of wssession so that is is now an empty file. Next I restarted the service using sudo systemctl restart windscribe. At this point, checking the status of the service shows that it has failed and checking the system log shows the same error cited by @damien. This error persists until I either delete the wssession file and restart the service or delete the entire /etc/windscribe folder and restart the service. At this point the windscribe binary simply recreates the /etc/windscribe directory and the 4 files mentioned previously with wssession containing an empty JSON: {}. At this point, I am again able to login and use windscribe.
After you renamed the /etc/windscribe directory did you rerun windscribe start? Did the binary recreate the /etc/windscribe directory with the proper empty JSON in the wssession file? Did the windscribe daemon have the correct permissions to edit the files in the /etc/windscribe directory?
@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.
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
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
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>
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!