-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Console: Client request error: self signed certificate in certificate chain #7128
Comments
This is a guess but it looks like the proxy being uses by Console will need to set |
I'm not super familiar with Console, but I believe this can be solved with |
@Bargs yeah, the config is the better way to go here. |
@Bargs @ycombinator thanks for your comments I've tried both from https://www.elastic.co/guide/en/sense/current/installing.html
and got
and also from https://www.elastic.co/guide/en/kibana/5.0/securing_console.html
and got same result
disabling validation (rejectUnauthorized: false) is not a solution, of course we do want to enforce cert chain validation, not disable it. cacert.pem in use is a RootCA certificate generated as per our Shield documentation, there is no-self-signed certs in this configuration. |
also setting
doesn't help |
@nellicus apologies, it looks like the sense documentation hasn't been updated for 5.0 yet. Anywhere you see So could you try
And let us know how that works? |
@Bargs yes that did the trick! thank you |
@Bargs did we finally added this documentation to the x-pack documentation? i do see this in the old sense configuration, not sure if we ended up exporting this to the x-pack one. |
Unable to use Console when using Own Root CA
Kibana version
Kibana config
Root CA cert
generated as per docs
Request from curl
Console browser output and debug log when requesting
Kibana verbose logs
Dev tools
request
response
Query String Parameters
The text was updated successfully, but these errors were encountered: