Connection errors with --no-verify-ssl option for Gazer v0.2.36

Question

Connection errors with --no-verify-ssl option for Gazer v0.2.36

Closed this issue 4 years ago · 8 comments

gzr returns the connection error with --no-verify-ssl option is specified.

ERROR: Connection Failed.
Did you specify the --no-ssl option for an ssl secured server?

Answer 1 · 2020-04-07T18:59:27.000Z

I believe that this is the generic failure message, and can often not be related at all to anything ssl. Paste a command that you're attempting, and we can help debug.

Answer 2 · 2020-05-20T19:59:53.000Z

facing the same problem here

the command I'm trying is:
gzr dashboard cat 1 --host meuvarejo360.cloud.looker.com --client_id id --client_secret secret

Answer 3 · 2020-05-20T20:18:45.000Z

tried putting the access config on ~/.netrc but the problem persists

is there a way to troubleshoot this?

Answer 4 · 2020-05-21T19:41:30.000Z

@biswanath-palo Are you on a GCP instance (*.cloud.looker.com), by any chance?

I'm able to replicate the issue on a GCP-hosted instance, but its working fine on an AWS-hosted instance.

Answer 5 · 2020-05-21T19:46:41.000Z

yes, I'm on a GCP instance

Answer 6 · 2020-05-21T19:59:47.000Z

I've confirmed the issue on a 2nd GCP-hosted instance... so definitely look like to be a compatibility issue with the new GCP instances.

@drstrangelooker fyi.

Answer 7 · 2020-05-21T20:15:20.000Z

Found a fix. GCP instances clients need to add the following to the command line, because the API listens on a different port than AWS instances.

--port 443

Answer 8 · 2020-06-02T16:41:00.000Z

I'm going to add this not only to the README but also to the error message.