Kibana 4.2 reverse proxy

Elastic Stack Kibana
1

I updated kibana to the newest version and now the paths are relative instead of absolute so my reverse proxy is broken. Is there any way to fix it?

Is like this issue but none fixed it

My previous nginx conf was:

    location /kibanaadmin/ {

    auth_basic "Restricted Access";
    auth_basic_user_file /etc/nginx/htpasswd.users;

    proxy_pass http://localhost:5601;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;

}

But it doesn't work anymore. Is there a fix?

2

The fix is slated for 4.2.1, which is the next bugfix release we are working toward.

1 Like
3

BUT, will be like the older releases? or a variation of the current approach. Just to know, thanks ! :grinning:

Greetings,

CV

4

I get an error with Timelion, maybe it has something to do with the reverse proxy. Is there any way to fix it?

Screenshot from 2015-11-13 12:50:34.png1450×155 16.9 KB

5

Solved adding this to my nginx conf

location /timelion {

    auth_basic "Restricted Access";
    auth_basic_user_file /etc/nginx/htpasswd.users;

    proxy_pass http://localhost:5601/timelion;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;

}
1 Like