You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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:
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
The text was updated successfully, but these errors were encountered: