-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Auto guess HTTP port number #352
Comments
I had it configured like this briefly but it caused way more issues than it solved. Most users don't run with a proxy, at least for initial setup. You can change the port in use in the config.js |
That's what I did actually. I understand the bad side effect of such a feature request. |
spalger
pushed a commit
to spalger/kibana
that referenced
this issue
Mar 3, 2016
harper-carroll
pushed a commit
to harper-carroll/kibana
that referenced
this issue
Jul 11, 2016
Updates to support Columbo Translation & Passthrough
w33ble
pushed a commit
to w33ble/kibana
that referenced
this issue
Sep 13, 2018
* Refactored render_element * Refactored render_element. Need to fix componentDidUpdate * Refactored render_element. Fixed resetRenderTarget. * Fixed resetRenderTarget. * Added comment to render-to-dom
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @rashidkpc
My elasticsearch cluster is running on http://elasticsearch.mywebsite.com/.
I open Kibana using http://elasticsearch.mywebsite.com/_plugin/kibana/.
Kibana auto guess the website URL which is elasticsearch.mywebsite.com but sadly it add 9200 as port number when connecting to it.
So it tries to send requests to http://elasticsearch.mywebsite.com:9200/ which does not exist.
Could you try to automatically use the same URL and PORT as the browser knows?
Not exactly the same issue as #313 but very close I think.
The text was updated successfully, but these errors were encountered: