Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

The orchestrator-client 3.0 can't work with https API URL #996

Closed
billmask opened this issue Oct 18, 2019 · 0 comments
Closed

The orchestrator-client 3.0 can't work with https API URL #996

billmask opened this issue Oct 18, 2019 · 0 comments

Comments

@billmask
Copy link

billmask commented Oct 18, 2019

Hello there,

I have enabled UseSSL: true in my configuration and restarted orchestrator. Everything runs fine except for orchestrator-client that uses the curl. The tool tries to access the API http address and orchestrator refuses so I get an error:

$ sudo orchestrator-client -c clusters

orchestrator-client[26110]: Cannot access orchestrator at https://orchestrator:<redacted>@localhost:3000/api.  Check ORCHESTRATOR_API is configured correctly and orchestrator is running

Not even changing the API url to https helped.
I don't see how this client wrapper would work with orchestrator https enabled.
After looking at #971, #981, #796 and #874 I think this is not being addressed anywhere here.

I kindly ask help on it, although if this is a legitimate issue, I can provide possible fix in the script.
Thanks in advance.
Marcelo

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

No branches or pull requests

1 participant