Skip to content

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

Open
mruiztech opened this issue Apr 25, 2025 · 7 comments
Open

Cannot use Bito CLI version 5.3 from ubuntu #64

mruiztech opened this issue Apr 25, 2025 · 7 comments

Comments

@mruiztech
Copy link

I have installed the binary following the instructions manually, using the script to install the latest version (5.3).

The installation is OK:

<▸> ~ bito --version
Bito CLI Version 5.3

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.

<▸> ~ bito          

Error: Sorry, Bito is not reachable due to a network or server issue. Please try again.

This is my SO:

OS: Ubuntu 22.04.5 LTS x86_64 
Kernel: 5.15.0-138-generic 
@macky3099
Copy link
Collaborator

macky3099 commented Apr 25, 2025

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:
/var/log/bito/bitocli.log

If you dint find any logs in above location then it should be in this location:
/Users/your-username/.bitoai/etc/logs/bitocli.log
Please let us know if you have any questions.

Thanks!

@mruiztech
Copy link
Author

Hello!
I install it with curl
sudo curl https://alpha.bito.ai/downloads/cli/install.sh -fsSL | bash

bitocli.log

Thanks!

@macky3099
Copy link
Collaborator

macky3099 commented Apr 26, 2025

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!

@mruiztech
Copy link
Author

mruiztech commented Apr 26, 2025

Hi @macky3099,

I review my network, and it's ok. I try again bito CLI and return same error.

<▸> ~ ping google.es                                                                                                                    
PING google.es (142.250.200.131) 56(84) bytes of data.
64 bytes from mad41s14-in-f3.1e100.net (142.250.200.131): icmp_seq=1 ttl=117 time=28.7 ms
64 bytes from mad41s14-in-f3.1e100.net (142.250.200.131): icmp_seq=2 ttl=117 time=23.8 ms
64 bytes from mad41s14-in-f3.1e100.net (142.250.200.131): icmp_seq=3 ttl=117 time=28.9 ms
64 bytes from mad41s14-in-f3.1e100.net (142.250.200.131): icmp_seq=4 ttl=117 time=23.8 ms
^C
--- google.es ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3015ms
rtt min/avg/max/mdev = 23.798/26.296/28.890/2.495 ms
<▸> ~ ping bitoai.com
PING bitoai.com (47.100.163.169) 56(84) bytes of data.
64 bytes from 47.100.163.169 (47.100.163.169): icmp_seq=1 ttl=43 time=229 ms
64 bytes from 47.100.163.169 (47.100.163.169): icmp_seq=2 ttl=43 time=240 ms
64 bytes from 47.100.163.169 (47.100.163.169): icmp_seq=3 ttl=43 time=227 ms
64 bytes from 47.100.163.169 (47.100.163.169): icmp_seq=4 ttl=43 time=225 ms
^C
--- bitoai.com ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4005ms
rtt min/avg/max/mdev = 225.385/230.306/239.723/5.591 ms
<▸> ~ 
<▪> ~ bito          

Error: Sorry, Bito is not reachable due to a network or server issue. Please try again.
<▪> ~ date           
Sat Apr 26 08:39:53 AM CEST 2025
<▸> ~ ping github.com              
PING github.com (140.82.121.3) 56(84) bytes of data.
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=1 ttl=52 time=59.3 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=2 ttl=52 time=57.8 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=3 ttl=52 time=56.2 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=4 ttl=52 time=55.5 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=5 ttl=52 time=53.0 ms
^C
--- github.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 52.993/56.363/59.256/2.126 ms
<▸> ~ 
<▪> ~ bito

Error: Sorry, Bito is not reachable due to a network or server issue. Please try again.
<▪> ~ date
Sat Apr 26 08:40:51 AM CEST 2025

Attacht latest bito log.

bitocli.log

I try curl to token URL showed in log, and can connect with the server with handshake OK

<▪> /v/l/bito curl -v https://mgmtapi.bito.ai/api/token                 
*   Trying 3.136.224.194:443...
* Connected to mgmtapi.bito.ai (3.136.224.194) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; O=Bito Inc.; CN=*.bito.ai
*  start date: Feb 17 00:00:00 2025 GMT
*  expire date: Mar 20 23:59:59 2026 GMT
*  subjectAltName: host "mgmtapi.bito.ai" matched cert's "*.bito.ai"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Organization Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x557b658499f0)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET /api/token HTTP/2
> Host: mgmtapi.bito.ai
> user-agent: curl/7.81.0
> accept: */*
> 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 405 
< date: Sat, 26 Apr 2025 06:45:57 GMT
< content-type: application/problem+json
< vary: Origin
< vary: Access-Control-Request-Method
< vary: Access-Control-Request-Headers
< access-control-allow-methods: GET,POST,DELETE,PUT,OPTIONS
< access-control-allow-headers: *
< access-control-allow-credentials: true
< access-control-max-age: 180
< access-control-expose-headers: token
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< content-security-policy: default-src 'self'
< x-frame-options: DENY
< x-content-type-options: nosniff
< referrer-policy: no-referrer
< permissions-policy: geolocation=(), microphone=(), camera=()
< allow: POST
< x-xss-protection: 0
< cache-control: no-cache, no-store, max-age=0, must-revalidate
< pragma: no-cache
< expires: 0
< 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #0 to host mgmtapi.bito.ai left intact
{"type":"about:blank","title":"Method Not Allowed","status":405,"detail":"Method 'GET' is not supported.","instance":"/api/token"}%  
<▸> /v/l/bito ping mgmtapi.bito.ai                     
PING production-mgmt-api-1636165474.us-east-2.elb.amazonaws.com (3.23.24.120) 56(84) bytes of data.
^C
--- production-mgmt-api-1636165474.us-east-2.elb.amazonaws.com ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13304ms

I also tried installing bito cli on another machine on the same network (Fedora OS), and it works fine.

thanks!

@macky3099
Copy link
Collaborator

Hi @mruiztech
Thank you so much for cooperating with us.

Let us check this on our end and we will get back to you on this. Thanks!

@macky3099
Copy link
Collaborator

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 - /Users/your-username/.bitoai

Thanks!

@mruiztech
Copy link
Author

mruiztech commented May 2, 2025

Hi, attach zip.
Thanks!

bitoai-config.zip

how i send pass?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants