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
Kibana 4.2.0 cannot be proxied under a directory any more #5230
Comments
Probably a double of #5171? Just saw that now. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
+1 |
This is fairly easy with nginx.
|
I admit it would be nice to set the route so Kibana 4 knows where it's mounted; but sometimes that's unrealistic. Kibana 4 is designed as a server; with that they are expecting to control the routes. We are deploying it where it is not dedicated. I kind of expect the rough edges. |
Thanks for the workaround; I just don't really like it for my use case as we have another web app running under / and I wouldn't want them to interfere. With the previous version this was possible, so it's a regression, in my opinion :) |
@BernhardBln actually in this case I originally had it /kibana and now forced it to be at /app/kibana It's kind of rough when you have / owned by something else and you deploy something like ES or Kibana and you want to be able to reverse proxy easily. Reverse Proxy and ES Plugins is still a problem for me. |
+1 |
worked with apache2. (please rewrite host 'proxy-dest.exaple.com')
access to 'kibana.example.com' by browser.
Let me know if you know of any better way. |
Using a vhost, all you really need are two lines in your vhost config. You shouldn't need to worry about /bundles/ and /app/kibana.
And then going to http://kibana.example.com/ should just work. That's the way i'm having to do it at the moment until this directory issue is fixed. |
@PSiAU the problem is when Kibana is not the only thing deployed. I have Sensu, Grafana, Kibana and a few other plaintext locations on a single domain/path. Thankfully the locations picked are unused by anything else :) |
I hear you @damm. I do exactly the same thing and run everything on a single domain so I don't need separate SSL certs for each app's domain. I presumed (maybe incorrectly) that @kouki-o was dedicating kibana.domainname as a short term solution to the directory problem, as i've had to do. |
+1 |
same problem here |
+1 |
1 similar comment
+1 |
+1 |
@schmorgs it's hardcoded in Kibana so you'd have to handle it with rewrites... :/ |
+1 |
@damm I don't have any rewrites in my config and it works just fine. |
My problems continue, i configured a reverse proxy for kibana on apache but i have another error. My proxy configuration: <LocationMatch /bundles> <LocationMatch /app/kibana> <Proxy http://*******:9200/> Only happens with the kibana 4.2 version due to the new routes |
@dfr0 ProxyRequests Off ProxyPass /app/kibana http://localhost:5601/app/kibana ProxyPass /bundles http://localhost:5601/bundles ProxyPass /elasticsearch http://localhost:9200 |
Sure, I don't know that elasticsearch needs your own proxy or location, i discovered that some hours ago with the chrome development tools, f*** But the status options don't work, do you've the same problem with this??? Thanx for everything. |
@dfr0 maybe you should start a new thread for "status options" issue, i have no idea what's that about |
@dfr0 You'll need to more entries in your proxy config to cater for the status page as well :
If you use the Chrome's "Inspect Element" option and select the "Console" tab, you can see the URL's that Kibana is trying to connect to, and if one of the URL prefixes isn't in your Apache reverse proxy setting, just add it and bounce Apache. |
:D Thx so much, i don't saw the console tab, i only are seeing on the network tab. |
Work correctly thx. |
my nginx balancer stopped working with kibana.
now it doesn't anymore. |
Unfortunately, I can confirm that server.basePath: "/kibana" in kibana.yml doesn't work as expected. Visiting http://myserver.com/kibana/ results in an HTTP 200 with only the JSON error text about 404 Not Found. This is with Kibana 4.3.1 (from official tarball) on CentOS 7.2. If I don't set server.basePath, Kibana works as expected. It just takes over the root context of my HAProxy however. This remains a show-stopper for our proxied, multi-app deployment. |
@guydavis it sounds like your proxy is not removing |
@guydavis , i got it to work again. explained my config here: https://discuss.elastic.co/t/4-3-0-how-to-configure-your-nginx-balancer-and-apache-reverse-proxy/37351/2?u=yodog |
I'm facing the same issue. I have a nginx setup for multiple app. I'm not able to make kibana work under a subfolder /kibana What is the configuration for nginx when we use server.Path? |
I was able to get both kibana 4.3.1 and ES plugins working through Nginx, using the detail @damm posted on 10/30/2015, and a separate location directive to handle the plugins. I had to add "elasticsearch" as a path in the location directive for Kibana, as my logs revealed requests directed to that path, and without it i would not get any information in my Kibana screens). The second directive handles the ES plugins i use (particularly "hq"). The "kopf" plugin doesnt connect unless I have the "/" path in the directive. Here's nginx location directives: location ~ (/app/kibana|/bundles/|/kibana4|/status|/plugins|/elasticsearch) { location ~ (/|/_plugin) { I listen on port 443 and access Kibana and ES plugins as: Hope this helps somebody, cuz its a bear trying to get all this stuff working again every time Elastic decides to change direction. |
@ksou1 you dont need separate locations if you follow the instructions posted here: https://discuss.elastic.co/t/4-3-0-how-to-configure-your-nginx-balancer-and-apache-reverse-proxy/37351/2?u=yodog |
Setting kibana.yml's |
I am on Kibana 4.5.3, when setting
As already pointed out I'm also guessing the |
I tried everything from this thread - but only @ksou1's solution worked for me. |
I add /elasticsearch , it's ok |
@linzhaolover can you explain the reason for the 'Upgrade $http_upgrade' bit? |
@damm's suggestion nearly worked for me. I just needed to add /elasticsearch to the regex too. I'm also using http2, so this works better for me:
|
My updated location for kibana 5.2.2 is this:
I didn't find any issues so far so this seems to be enough for the current version. Or could it be that I am missing something? |
most of all solutions provided here isn't taking into account cases like additional services on a same server behind reverse proxy and thus doesn't work properly for example solution with
as you might see regular expression will match this case another problem with |
@t3chn0m4g3 You don't need the re-write rule if you set
The difference is explained here: https://www.nginx.com/resources/admin-guide/reverse-proxy/ |
BernhardBln commentedOct 29, 2015
We were playing around with Kibana 4.1 which we proxied under /kibana/* - that worked quite well.
Now, the Kibana app is under /app/kibana and tries to load resources via their absolute url, e.g.
/bundles/kibana.bundle.js
.Could that be referenced relatively? Then proxying would still work...
The text was updated successfully, but these errors were encountered: