Open candroid-man opened 1 month ago
Please give our new Linux standalone CLI app, available in the v2.11.11 release, a spin and let us know if it fulfills your requirements. Cheers!
@bernerdad I am unable to login to my account with the CLI tool:
candroid_man@nobara:~$ windscribe-cli login "WindscribeUserName" "w4RLfYsC^7bw6DC1$m^E"
Login is in progress. Use 'windscribe-cli status' to check for status.
candroid_man@nobara:~$ windscribe-cli status
Internet connectivity: available
Login state: Error: Incorrect username, password, or 2FA code
Firewall state: Off
Connect state: Disconnected
candroid_man@nobara:~$
I also tried it without quotes:
candroid_man@nobara:~$ windscribe-cli login WindscribeUserName w4RLfYsC^7bw6DC1$m^E
Login is in progress. Use 'windscribe-cli status' to check for status.
candroid_man@nobara:~$ windscribe-cli status
Internet connectivity: available
Login state: Error: Incorrect username, password, or 2FA code
Firewall state: Off
Connect state: Disconnected
candroid_man@nobara:~$
I do not have 2FA enabled, my actual password is randomly generated similarly to the example password above
Also I think it's awesome that a CLI tool is available now! Now it would be even better if the GUI and the CLI tool worked together. So whenever you download the package from https://windscribe.com/download/ it would give you a package with the GUI and CLI tool bundled together, and the GUI just controls the CLI in the background. So that way if you connect to Windscribe using the CLI tool, and you open the GUI app, it will reflect what the current status of your connection is and the user could then use the GUI tool to disconnect for example.
If your password has special characters similar to the example password, you probably have to enclose the password in quotes to prevent the shell from interpreting it. In the above example the $m part would likely have been treated as a shell variable.
The GUI app does indeed come with a CLI client (though the GUI app must be running, since in this configuration the CLI controls the GUI in the background, rather than the other way around). It's also named windscribe-cli and behaves much the same as the standalone.
As shown above I tried both with and without quotes.
Sorry, missed a word! I meant to say single quotes
. That is, "$m" is still evaluated by the shell, but '$m' is literal.
I'd like to be able to close the app and let it run in the background without any extra dependencies. Typically this is done by having the backend of the desktop app work off of the CLI using a daemon, rather than relying on the GUI itself to handle the connection. This would also make the CLI much more robust and powerful. So for example, if I wanted to connect to the tunnel with the CLI, I would do:
And then if you decide to open the GUI, it would show you are connected to Glinda:
IVPN Example
This is what the IVPN CLI utility looks like, to give you an idea of what this would look like:
IVPN gives you everything you could possibly need in the CLI utility, because the GUI is just that, a GUI for the CLI.