looker-open-source / gzr

A Command Line Tool for Looker Content Management
MIT License
120 stars 37 forks source link

Unable to connect with v0.3.10 #218

Closed ogarza closed 10 months ago

ogarza commented 10 months ago

I'm trying to connect to a looker hosted instance and I keep getting:

ERROR: Connection Failed. Did you specify the --no-ssl option for an ssl secured server? You may need to use --port=443 in some cases as well

I have Ruby v3.0.2p107 installed on ubuntu 22.04 LTS The version of the looker-sdk gem is 0.1.6

It seems no matter what, the host is set to 'localhost'

oscar@u-vm-2:~$ gzr user me host=https://myhostnamehere.cloud.looker.com/ --client-id=abc123 --client-secret=qbc123 --debug --port=443
{"debug"=>true, "host"=>"localhost", "port"=>"443", "ssl"=>true, "verify_ssl"=>true, "timeout"=>60, "force"=>false, "token_file"=>false, "client_id"=>"abc123", "client_secret"=>"abc123", "fields"=>"id,email,last_name,first_name,personal_folder_id,home_folder_id", "plain"=>false, "csv"=>false}
using options ["debug=>true", "host=>localhost", "port=>443", "ssl=>true", "verify_ssl=>true", "timeout=>60", "force=>false", "token_file=>false", "client_id=>abc123", "fields=>id,email,last_name,first_name,personal_folder_id,home_folder_id", "plain=>false", "csv=>false"]
logout
ERROR: Connection Failed.
Did you specify the --no-ssl option for an ssl secured server?
You may need to use --port=443 in some cases as well.
ogarza commented 10 months ago

oh wow, I forgot the -- before host... I get the same error though

drstrangelooker commented 10 months ago

--host=myhostnamehere.cloud.looker.com, no https://../ parts.

Cheers. Mike

ogarza commented 10 months ago

Actually, the issue was with the versions, removing the https:// from the hostname:

I am able to connect with: ruby v 3.1.2p20 looker-sdk v 0.1.2 gazer v 0.2.58

the same command fails with the other versions

drstrangelooker commented 10 months ago

Can you send me the command and the response with the https removed so I can see?

Thanks.

ogarza commented 10 months ago

I apologize again... I removed the https:// part but forgot to add the -- again...

It is working correctly in both machines.

Thank you so much

drstrangelooker commented 10 months ago

No problem. Glad everything is working.