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

Specify app base path for reverse proxies #5171

Closed
camerondavison opened this Issue Oct 22, 2015 · 15 comments

Comments

Projects
None yet
@camerondavison

camerondavison commented Oct 22, 2015

I have been using kibana 4.1.2 and all of the links are relative so they work great behind a reverse proxy. I think because of 2ed9f35 . This looks like it is broken in 4.2

My personal belief is that using relative urls is pretty likely to create subtle bugs that are not often found. I think it would be better to do 1 of two things.

  • Implement something like http://flask.pocoo.org/snippets/35/ where you read a X-Script-Name header that apache/nginx can send
  • add a configuration parameter such as appPath where you can specify the path such as '/kibana' or something.

@camerondavison camerondavison changed the title from allow specific app base path for kibana 4.2 for reverse proxies to allow specific app base path for 4.2 for reverse proxies Oct 22, 2015

@rashidkpc rashidkpc changed the title from allow specific app base path for 4.2 for reverse proxies to Specify app base path for reverse proxies Oct 26, 2015

@duylong

This comment has been minimized.

duylong commented Oct 29, 2015

Same problem. I do not use reverse proxies (kibana 4 + passenger), a solution with a configuration parameter is better.

@damm

This comment has been minimized.

damm commented Oct 31, 2015

I added a comment in #5230 it's fairly easy with nginx; might require more rewrite magic with Apache.

@nabheet

This comment has been minimized.

nabheet commented Nov 3, 2015

👍

@camerondavison

This comment has been minimized.

camerondavison commented Nov 18, 2015

So bunches of people are opening dupe issues for this one, is this issue in the roadmap? I think most people who are using https:// probably do not have a certificate just for kibana, so therefore cannot run it under the ROOT (/) path.

@spalger

This comment has been minimized.

Member

spalger commented Nov 18, 2015

@a86c6f7964 we actually fixed this in #5337

This pr will ship with 4.2.2 shortly

@spalger spalger closed this Nov 18, 2015

@dfr0

This comment has been minimized.

dfr0 commented Nov 19, 2015

My problems continue, i configured a reverse proxy for kibana on apache but i have another error.

My proxy configuration:

<LocationMatch /bundles>
ProxyPass http://****:5601/bundles
ProxyPassReverse http://**
_:5601/bundles
Order Deny,Allow
Deny from all
Allow from all
AuthType Basic
AuthUserFile /etc/
_/htpasswd.controlusers
Require valid-user
AuthName "
**** log Server"

<LocationMatch /app/kibana>
ProxyPass http://_:5601/app/kibana
ProxyPassReverse http://
_
_:5601/app/kibana
Order Deny,Allow
Deny from all
Allow from all
AuthType Basic
AuthUserFile /etc/
__/htpasswd.controlusers
Require valid-user
AuthName "_
** log Server"

<Proxy http://****:9200/>
Order Deny,Allow
Deny from all
Allow from ******
AuthType Basic
AuthName "
* ELS Server"
AuthUserFile /etc/okn/htpasswd.controlusers
Require valid-user

image

image

Only happens with the kibana 4.2 version

@relgames

This comment has been minimized.

relgames commented Feb 15, 2016

Hi, the issue is still not fixed in Kibana 4.4.0
It tries to load resources from /bundles, ignoring server.basePath
Also, Dashboard links point to /#/dashboard

Should I open new issue?

@davidDalsace

This comment has been minimized.

davidDalsace commented Mar 3, 2016

Same probleme for me with Kibana 4.4.0 .
The "server.basePath" setting in kibana/config/kibana.yml helps to bind a gateway,
(I've set it like server.basePath: "/myGateWay?URL=http://localhost:5601"

but I'm stuck with the same error .. It looks like it tries to get info from elasticSearch by building this kind of path :

http://myServer:8080/myGateWay?URL=http://localhost:5601/elasticsearch/_mget
Where it should rather get
http://myServer:8080/myGateWay?URL=http://localhost:9200/elasticsearch/_mget

I was expecting it would use the elasticsearch.url setting, but it doesn't...

@abhijitdeka

This comment has been minimized.

abhijitdeka commented Mar 8, 2016

Hi,
This issue is still reproducible.(Kibana 4.4.1) I tried specifying server.basepath="/analytics" .Now the kibana server on 5601 port http://localhost:5601 redirects me to http://5601/app/kibana and gives 404 error. I can see other people also able to reproduce the same issue.

Should we reopen this issue?

@carlosvega

This comment has been minimized.

carlosvega commented Mar 10, 2016

+1

It happened to me with both 4.4.0 and 4.4.1, not working at all.

@gabfusi

This comment has been minimized.

gabfusi commented Mar 19, 2016

+1

same here with 4.4.2!

@nicknameforever

This comment has been minimized.

nicknameforever commented May 10, 2016

+1 in 4.4.x

Is there any workaround?

@fuzziness

This comment has been minimized.

fuzziness commented May 12, 2016

+1 in 4.5.0

@yalok

This comment has been minimized.

yalok commented May 18, 2016

I found a workaround here: #5230
It was already mentioned above though. But I didn't notice it at first look.

@MarkBramnik

This comment has been minimized.

MarkBramnik commented Jul 5, 2016

+1 in 4.5.1 - really important for us. The workaround pointed by yalok will work, however what if proxy is "responsible" for other products as well, throwing this logic to proxy server is not a real solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment