-
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
server.basePath results in 404 #6665
Comments
Here is some more information...
Why does '/kibana4/app/kibana' return a 404? Nathan |
@nreese this is because the basepath should be removed by the proxy before requests are sent to Kibana. This is generally called "request rewriting" and any number of posts should exist to show you how to set that up for your proxy. |
Can you please clarify how this works? I am really stuck and can not find On Mon, Mar 28, 2016 at 2:45 PM, Spencer notifications@github.com wrote:
|
Same issue here. And I find this config by nginx could work: https://discuss.elastic.co/t/4-3-0-how-to-configure-your-nginx-balancer-and-apache-reverse-proxy/37351/5 |
I eventually figured it out and posted an answer to Stack overflow using On Tue, Apr 12, 2016 at 8:51 AM, Feng Yu notifications@github.com wrote:
|
Please add sufficient example with server.basepth. Lot of users are struggling because of lack of documentation. |
My recommendation would be to re-word the verbiage for the Enables you to specify a path to mount Kibana at if you are running behind On Thu, Apr 14, 2016 at 4:19 AM, abhijit notifications@github.com wrote:
|
This is ridiculous. Setting the basepath should actually change the basepath for kibana and should not require any reverse proxy rewriting. This kind of behavior is pretty 101 in webapps. |
I think there's some confusion here. |
I'm aware of what basePath is and I'm using it behind a reverse proxy. |
Me too. I also am aware of what basePath is and I'm using it behind a reverse proxy. Please... |
It would probably be trivial for us to support this, but we can't just change the way basePath works at this point. What do you think about #9522? |
I agree, I just stumbled across this same exact issue. creates a lot of extra work for no reason. If you updating the basepath it should change it. Having different URL's makes it difficult to trouble shoot. |
I got this working on this system:
|
>⚠️ Synthetic failures are not related to any EUI changes and are likely already failing on main. Please ignore the failing CI status when reviewing. ## [`77.0.0`](https://github.com/elastic/eui/tree/v77.0.0) **Bug fixes** - Fixed named `EuiBadge` colors to reflect custom theme overrides ([#6659](elastic/eui#6659)) - Fixed user-defined SCSS variables failing to override variables defined in Amsterdam typography overrides. ([#6665](elastic/eui#6665)) - Fixed bold `EuiCode` tokens to actually be bold ([#6666](elastic/eui#6666)) **Breaking changes** - Success- and accent-colored `EuiBadge`s and `EuiButton`s have had their fill colors tinted slightly on light mode to be more readable ([#6659](elastic/eui#6659)) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jon <jon@elastic.co>
I am running kibana 4.4.1 on RHEL 7.2
Everything works when the kibana.yml file does not contain the setting
server.basePath
. However, when basePath is set toserver.basePath: "/kibana4"
all HTTP requests result in 404s. For example http://x.x.x.x:5601/kibana4 results in a 404 and http://x.x.x.x:5601 gets redirected to http://x.x.x.x:5601/kibana4/app/kibana which also results to a 404.Am I using server.basePath correctly? Why all the 404s?
The text was updated successfully, but these errors were encountered: