-
Notifications
You must be signed in to change notification settings - Fork 78
Cannot use Bito CLI version 5.3 from ubuntu #64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @mruiztech Thanks for using Bito CLI and sorry for the issue you are facing. Can you please give us more details on how you installed Bito CLI? Using curl or homebrew? Also can you please share us the logs to further debug this issue on our end? You can find CLI logs in following location: If you dint find any logs in above location then it should be in this location: Thanks! |
Hello! Thanks! |
Hi @mruiztech , Thanks for sharing the logs. from the logs we see that you haven't got any response due a network failure. Can you please try switching your network and try again or maybe try when your network is stable? Please let us know if this issue persists even after a retry. Thanks! |
Hi @macky3099, I review my network, and it's ok. I try again bito CLI and return same error.
Attacht latest bito log. I try curl to token URL showed in log, and can connect with the server with handshake OK
I also tried installing bito cli on another machine on the same network (Fedora OS), and it works fine. thanks! |
Hi @mruiztech Let us check this on our end and we will get back to you on this. Thanks! |
Hi @mruiztech , will it be possible for you to zip the entire .bitoai folder and send it to us? .bitoai folder can be found at this location - Thanks! |
Hi, attach zip. how i send pass? |
I have installed the binary following the instructions manually, using the script to install the latest version (5.3).
The installation is OK:
But when I try to run it, it asks me for an email or a password, and a few seconds after setting it, I get an error.
This is my SO:
The text was updated successfully, but these errors were encountered: