Package Details: windscribe-cli 1.4_51-1

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: GPL
Submitter: hkuchampudi
Maintainer: salvah22
Last Packager: hkuchampudi
Votes: 94
Popularity: 0.007905
First Submitted: 2017-07-29 18:12 (UTC)
Last Updated: 2019-07-23 05:30 (UTC)

Pinned Comments

hkuchampudi commented on 2018-11-07 04:12 (UTC) (edited on 2021-09-19 17:39 (UTC) by hkuchampudi)

UPDATE 09/19/2021: I (hkuchampudi) am not able to maintain this package any longer. Therefore, I am abandoning it so that someone else who is more interested can maintain it. The GitHub repository has also been archived.

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

IslamMu commented on 2019-05-13 23:22 (UTC)

@hkuchampudi sorry for bothering you bro, i did what you said and downgrade to stunnel 5.49, stealth protocl worked fine, but i gont dns leak issue now :D thank you for helping me

hkuchampudi commented on 2019-05-13 22:21 (UTC)

@IslamMu

The problem is with the stunnel version running on a ditribution, not the distribution itself. If you type stunnel -version on the computers/VMs where stealth is working, they should show that they are running a stunnel version less than 5.50. However, on Arch, the latest version of stunnel is 5.51. Stunnel versions 5.50 and greater will not currently work with windscribe-cli.

IslamMu commented on 2019-05-13 22:04 (UTC)

@hkuchampudi what i will say is weird. but i dont face any problem wth stealthvpn protocol. on ubuntu or mint.

it's work just fine this is why i put my comment here. i opened support ticket and sent my logs before like i did here, and i don't know they will solv i or not.

hkuchampudi commented on 2019-05-13 21:44 (UTC)

@IslamMu

I believe that this is a non-fixable problem from my end. Stunnel 5.50 introduced major, breaking changes to how the stunnel configuration file is parsed. Windscribe must push a new, compliant stunnel configuration file in order to fix this problem. Any distribution that uses stunnel 5.50 or newer will be affected by this issue (e.g. windscribe-cli on Ubuntu 19.04 is affected by this issue as well). Additionally, manual changes cannot be made to the stunnel configuration as the windscribe-cli client will just overwrite those changes when a connection attempt is made.

You should file a support ticket with Windscribe so they are aware of this. If you absolutely need to use stunnel, you can always download stunnel 5.49 (the last known working version) from the official stunnel archive (ftp://ftp.stunnel.org/stunnel/archive/5.x/), build it from source, and then install it.

IslamMu commented on 2019-05-13 18:15 (UTC)

I can't connect to vpn through stealth protocol, seems like some error on the package. please update and fix it because in my country udp and tcp blocked by dpi.

this what i got when i try to connect: windscribe connect Connecting to Romania Bucharest No Vampires (stealth:443) Firewall Enabled Failed to connect

logs:

2019-05-13 20:10:22,139 [INFO] Starting new HTTPS connection (1): api.windscribe.com 2019-05-13 20:10:22,695 [DEBUG] "GET /Session?client_auth_hash=9b41a5b301f63ae17bec26cd8b22d880&session_auth_hash=15766876-3-1557675242-8cacbed530ec9d092696-d9849d6359170378a3e4&time=1557771022 HTTP/1.1" 200 None 2019-05-13 20:10:22,703 [INFO] Loading Account 2019-05-13 20:10:22,812 [INFO] command "protocol" done 2019-05-13 20:10:34,651 [INFO] Daemon: got command: "connect" 2019-05-13 20:10:34,652 [INFO] Daemon: connect arg: None 2019-05-13 20:10:34,652 [INFO] CACHED - GET AssetsServerList 2019-05-13 20:10:34,669 [INFO] Chosen connection "ro" not in chosen nodes, using parent location 2019-05-13 20:10:34,670 [INFO] Chosen node: {u'group': u'Bucharest - No Vampires', u'weight': 1, u'ip': u'185.217.68.194', u'hostname': u'ro-003.whiskergalaxy.com', u'ip2': u'185.217.68.195', u'ip3': u'185.217.68.196', u'tz': u'Europe/Bucharest', u'type': u'normal', u'gps': u'44.44,26.10'} 2019-05-13 20:10:34,671 [INFO] Connecting to Romania Bucharest No Vampires (stealth:443) 2019-05-13 20:10:34,684 [INFO] Starting new HTTPS connection (1): api.windscribe.com 2019-05-13 20:10:35,325 [DEBUG] "GET /MyIp?client_auth_hash=6854e66c7dc171201b1c6275cefe40ef&time=1557771034 HTTP/1.1" 200 None 2019-05-13 20:10:35,376 [INFO] Stunnel on port 58631 2019-05-13 20:10:35,377 [INFO] Writing Stunnel config 2019-05-13 20:10:35,388 [INFO] Writing OpenVPN config 2019-05-13 20:10:35,389 [INFO] Stunnel command: /usr/bin/stunnel /etc/stunnel/stunnel.conf 2019-05-13 20:10:35,492 [INFO] Stunnel route command: ip route add 185.217.68.196/32 via 192.168.1.1 2019-05-13 20:10:35,560 [INFO] OPENVPN: unable to connect to management interface 2019-05-13 20:10:35,641 [INFO] Firewall: removing rule for ip 78.108.38.226 2019-05-13 20:10:36,115 [INFO] Firewall: removing rule for ip 78.108.38.226 2019-05-13 20:10:36,151 [INFO] Firewall disabled 2019-05-13 20:10:36,181 [INFO] ------------ IPTABLES ------------- 2019-05-13 20:10:36,182 [INFO] Chain OUTPUT (policy ACCEPT) target prot opt source destination
ufw-before-logging-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-before-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-after-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-after-logging-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-reject-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-track-output all -- 0.0.0.0/0 0.0.0.0/0

2019-05-13 20:10:36,183 [INFO] ------------ IPTABLES END ------------- 2019-05-13 20:10:36,431 [INFO] applying hosts file entries for domains: {'assets.windscribe.com': '104.20.123.38', 'api.windscribe.com': '104.20.122.38'} 2019-05-13 20:10:36,623 [INFO] Firewall enabled 2019-05-13 20:10:36,655 [INFO] ------------ IPTABLES ------------- 2019-05-13 20:10:36,658 [INFO] Chain OUTPUT (policy DROP) target prot opt source destination
ufw-before-logging-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-before-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-after-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-after-logging-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-reject-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-track-output all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 104.20.123.38
ACCEPT all -- 0.0.0.0/0 104.20.122.38
ACCEPT all -- 0.0.0.0/0 104.27.162.70
ACCEPT all -- 0.0.0.0/0 104.27.163.70
ACCEPT all -- 0.0.0.0/0 104.27.166.172
ACCEPT all -- 0.0.0.0/0 104.27.167.172
ACCEPT all -- 0.0.0.0/0 104.28.16.90
ACCEPT all -- 0.0.0.0/0 104.28.17.90
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 127.0.0.1
ACCEPT all -- 0.0.0.0/0 185.217.68.196

2019-05-13 20:10:36,658 [INFO] ------------ IPTABLES END ------------- 2019-05-13 20:10:36,659 [INFO] Write ServerCredentials 2019-05-13 20:10:36,694 [INFO] openvpn exec path: /usr/bin/openvpn on port: unix 2019-05-13 20:10:36,696 [INFO] OPENVPN: unable to connect to management interface 2019-05-13 20:10:36,696 [INFO] running openvpn command: /usr/bin/openvpn --verb 4 --daemon --management /etc/windscribe/openvpn.sock unix --management-hold --config /etc/windscribe/client.ovpn --log /var/log/windscribe/ovpn_log.txt --up /etc/windscribe/update-resolv.sh --down /etc/windscribe/update-resolv.sh 2019-05-13 20:10:36,797 [INFO] OPENVPN: unable to connect to management interface 2019-05-13 20:10:36,798 [INFO] OPENVPN HOLD Release State: None delaycount 0 2019-05-13 20:10:37,800 [INFO] OPENVPN HOLD Release State: HOLD delaycount 1 2019-05-13 20:10:38,802 [INFO] OPENVPN: Hold Release sent 2019-05-13 20:10:39,805 [INFO] OPENVPN State: None 2019-05-13 20:10:40,057 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:40,308 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:40,560 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:40,811 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:41,063 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:41,314 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:41,566 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:41,817 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:42,069 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:42,320 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:42,572 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:42,823 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:43,075 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:43,326 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:43,578 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:43,829 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:44,081 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:44,332 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:44,584 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:44,835 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:45,087 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:45,338 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:45,590 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:45,841 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:46,093 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:46,344 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:46,595 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:46,847 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:47,098 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:47,349 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:47,601 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:47,853 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:48,104 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:48,355 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:48,607 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:48,858 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:49,109 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:49,361 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:49,612 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:49,864 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:50,115 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:50,367 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:50,618 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:50,870 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:51,121 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:51,373 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:51,624 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:51,876 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:52,127 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:52,378 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:52,630 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:52,881 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:53,133 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:53,384 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:53,636 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:53,887 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:54,139 [INFO] OPENVPN State: None 2019-05-13 20:10:54,391 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:54,642 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:54,894 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:55,145 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:55,397 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:55,648 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:55,900 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:56,151 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:56,403 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:56,656 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:56,908 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:57,159 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:57,411 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:57,662 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:57,914 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:58,165 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:58,416 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:58,668 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:58,919 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:59,171 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:59,423 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:59,674 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:10:59,926 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:11:00,177 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:11:00,429 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:11:00,680 [INFO] OPENVPN State: RECONNECTING 2019-05-13 20:11:00,681 [INFO] OPENVPN: RECONNECTING took too long, aborting 2019-05-13 20:11:00,682 [INFO] CONNECT: openvpn failed, retrying: False 2019-05-13 20:11:00,712 [INFO] ------------ IPTABLES ------------- 2019-05-13 20:11:00,713 [INFO] Chain OUTPUT (policy DROP) target prot opt source destination
ufw-before-logging-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-before-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-after-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-after-logging-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-reject-output all -- 0.0.0.0/0 0.0.0.0/0
ufw-track-output all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 104.20.123.38
ACCEPT all -- 0.0.0.0/0 104.20.122.38
ACCEPT all -- 0.0.0.0/0 104.27.162.70
ACCEPT all -- 0.0.0.0/0 104.27.163.70
ACCEPT all -- 0.0.0.0/0 104.27.166.172
ACCEPT all -- 0.0.0.0/0 104.27.167.172
ACCEPT all -- 0.0.0.0/0 104.28.16.90
ACCEPT all -- 0.0.0.0/0 104.28.17.90
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 127.0.0.1
ACCEPT all -- 0.0.0.0/0 185.217.68.196

2019-05-13 20:11:00,714 [INFO] ------------ IPTABLES END ------------- 2019-05-13 20:11:00,714 [INFO] Failed to connect 2019-05-13 20:11:00,715 [INFO] ------------ OPEN VPN Log START ------------- 2019-05-13 20:11:00,715 [INFO] Mon May 13 20:10:36 2019 WARNING: file '/etc/windscribe/credentials.txt' is group or others accessible Mon May 13 20:10:36 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019 Mon May 13 20:10:36 2019 library versions: OpenSSL 1.1.1b 26 Feb 2019, LZO 2.10 Mon May 13 20:10:38 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 13 20:10:38 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Mon May 13 20:10:38 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Mon May 13 20:10:38 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:58631 Mon May 13 20:10:38 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:58631 [nonblock] Mon May 13 20:10:38 2019 TCP: connect to [AF_INET]127.0.0.1:58631 failed: Connection refused Mon May 13 20:10:38 2019 SIGUSR1[connection failed(soft),init_instance] received, process restarting Mon May 13 20:10:43 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 13 20:10:43 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:58631 Mon May 13 20:10:43 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:58631 [nonblock] Mon May 13 20:10:43 2019 TCP: connect to [AF_INET]127.0.0.1:58631 failed: Connection refused Mon May 13 20:10:43 2019 SIGUSR1[connection failed(soft),init_instance] received, process restarting Mon May 13 20:10:48 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 13 20:10:48 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:58631 Mon May 13 20:10:48 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:58631 [nonblock] Mon May 13 20:10:48 2019 TCP: connect to [AF_INET]127.0.0.1:58631 failed: Connection refused Mon May 13 20:10:48 2019 SIGUSR1[connection failed(soft),init_instance] received, process restarting Mon May 13 20:10:53 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 13 20:10:53 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:58631 Mon May 13 20:10:53 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:58631 [nonblock] Mon May 13 20:10:53 2019 TCP: connect to [AF_INET]127.0.0.1:58631 failed: Connection refused Mon May 13 20:10:53 2019 SIGUSR1[connection failed(soft),init_instance] received, process restarting Mon May 13 20:10:58 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 13 20:10:58 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:58631 Mon May 13 20:10:58 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:58631 [nonblock] Mon May 13 20:10:58 2019 TCP: connect to [AF_INET]127.0.0.1:58631 failed: Connection refused Mon May 13 20:10:58 2019 SIGUSR1[connection failed(soft),init_instance] received, process restarting Mon May 13 20:11:00 2019 SIGINT[hard,init_instance] received, process exiting

2019-05-13 20:11:00,716 [INFO] ------------ OPEN VPN Log END ------------- 2019-05-13 20:11:00,744 [INFO] command "connect" done

aleksz commented on 2019-05-13 01:47 (UTC)

I'm unable to reproduce the issue on a clean, properly configured VM installation of Arch. https://bit.ly/2LD1rW6

haroonjee_99 commented on 2019-04-18 19:14 (UTC)

sudo systemctl enable windscribe

this command should be run once before using windscribe.

found out about it today and thought other users should know about it as well.

Agafron commented on 2018-12-19 20:21 (UTC)

@hkuchampudi I find problem, it`s linux-lqx kernel

sudo iptables -L

iptables: No chain/target/match by that name.

but in another kernel its work ok, thanks!!

hkuchampudi commented on 2018-12-19 19:44 (UTC)

@Agafron It seems like you are missing your OUTPUT chain? I am not sure why this would happen because the OUTPUT chain is built-in to the filter table by default. When you do sudo iptables -L what chains do you see? Have you made modifications to your iptables? What are you running windscribe-cli on?

Agafron commented on 2018-12-19 18:46 (UTC) (edited on 2018-12-19 18:47 (UTC) by Agafron)

@hkuchampudi windscribe viewlog say Firewall: removing rule for ip 0.0.0.0; Firewall disabled; Command '['iptables -nL OUTPUT']' returned non-zero exit status 1, iptables -nL OUTPUT say No chain/target/match by that name.

<quote>you might have been talking to Gary?</quote>
Igor M

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