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
Incorrect ssl redirect #7158
Comments
I am having a similar issue. The problem lies here:
E.g. if I set kibana to "bind" to |
The |
I'm running into this using a Docker deployment at the moment. By adding an extra Docker host (data.example.com to 0.0.0.0) I can set What would be the disadvantage of a redirect to the same |
I'm also running into this issue using a Docker deployment. I get redirected to https://0.0.0.0:5601 when enabling SSL and binding to 0.0.0.0. Has anyone found a workaround or fix for this yet? |
Would be helpful if Kibana used If you run any sort of load balancer in front of Kibana, such as an AWS ELB, you can't set the host that Kibana will be available at in |
|
If Kibana exposes https://github.com/hapijs/hapi/blob/master/API.md#server.options |
If you try and access kibana from outside of localhost with ssl enabled, say from a virtualBox, it'll try to redirect you to localhost, which results in an error.
To get around this error run kibana with the
--no-ssl
flagThe text was updated successfully, but these errors were encountered: