-
Notifications
You must be signed in to change notification settings - Fork 126
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
cli is asking for oAuth #39
Comments
See #39 commit_hash:79124763823633fe9f496b62db084ac4c72fcfb6
Hello. This is bug in CLI, it will be fixed in the next release.
This is expected: PERFORATOR_SECURE=false disabled TLS, so CLI tried to open plaintext connection to TLS-only endpoint.
It was a mistake in docs. I've fixed it. Thank you for the report! |
Release v0.0.4 is finally aviailable. |
thank you! |
still cant make it work. Am i doing smth wrong ?
|
looks like it doesnt like protocol in the env var and needs a port. could you please tell what is wrong here ?
|
Yes. In fact,
This is also true (but we are going to add defaults here).
Which CA has issued certificate for the endpoint? Looking at our code, it seems that we're doing pretty weird thing here. If you use internal CA whose root is installed system-wide, please try adding |
i issued the cert using acme and used this cert/key in perforator installation. may be i miss smth ?
now i added ca to the system and now seeing this
thanks |
Do you have https server on |
yes it's a https server (actually http as ingress controller terminates tls and traffic goes to port 80 of the perforator proxy service), i'm just following the guide https://perforator.tech/docs/en/guides/cli/install trying to make cli work. |
Yes, just try with |
no it doesnt work
|
Hello, i built cli v0.0.3 but it doesn't work with my perforator i deployed on k8s
if i set PEFORATOR_SECURE to false
also please note that looks like PERFORATOR_URL env var is ignored https://perforator.tech/docs/en/howto/cli/install and PERFORATOR_EDPOINT is required instead.
Thanks
The text was updated successfully, but these errors were encountered: