kibana-authentication-proxy icon indicating copy to clipboard operation
kibana-authentication-proxy copied to clipboard

Published 20 hours ago • verified publisher icon fangli

kibana shows blank page with error

Open maxhyjal opened this issue 10 years ago • 12 comments

After following the installation procedure and starting nodejs app. It prompted me to enter the password(using basic auth). But after I enter the correct password, I'm getting a blank page with Cannot GET / error.

Is there some step I'm not aware of during the configurations?

Thanks!

maxhyjal avatar Nov 04 '14 01:11 maxhyjal

I'm running into the same issue using Basic Auth. The blank page with Cannot GET/ - error is displayed in Chrome. IE displays a site saying that it run into a 404-error. Authorization is working as it should, because entering the wrong password leads to a blank page saying "unauthorized".

Would be nice if some could get this fixed or even tell me and maxhyjal what we're doing wrong.

bof64665 avatar Nov 05 '14 07:11 bof64665

Same problem here.

mungeol avatar Nov 07 '14 00:11 mungeol

So I got the same error. The problem lies in the newest version of kibana. If you chose not to update the built in kibana, the authentication works perfectly fine.

Blendwolf avatar Nov 12 '14 02:11 Blendwolf

Same problem here. Any fix besides not update kibana?

johnnybraga avatar Nov 21 '14 14:11 johnnybraga

Any updates?

ghost avatar Dec 01 '14 11:12 ghost

are you guys using this against ES 1.4.x?

faxm0dem avatar Dec 01 '14 15:12 faxm0dem

Got the same issues, someone fixed it ?

spyzzz avatar Dec 02 '14 16:12 spyzzz

There are no updates made to face this issue. For me it worked not to update the kibana version. So the solution from blendwolf seems to be the only one.

bof64665 avatar Dec 14 '14 17:12 bof64665

Confirmed here as well. Any workaround for Kibana 4 would be appreciated!

izhan avatar Dec 15 '14 02:12 izhan

Looks like the fix is not in master yet, I just git clone https://github.com/izhan/kibana-authentication-proxy.git and got this commit: commit 304b944b354f158a18cc584055df635cbb4f5b26 Author: Irvin Zhan <[email protected]> Date: Thu Dec 18 09:23:07 2014 -0500 configure to allow for google oauth and didn't get GET / error

noamgal avatar Jan 07 '15 16:01 noamgal

ah yes, my fork you mentioned used a reverse proxy built in express to workaround this. there are a few more commits that aren't pushed up to that fork that addresses some issues with it. i can push it up when i have a chance.

we ultimately switched to a simple nginx proxy. the fork had some issues due to a bug in kibana parsing, though that issue might have been fixed in kibana master already.

izhan avatar Jan 07 '15 17:01 izhan

@izhan support for Kibana 4 is unlikely to be possible on a reverse proxy like this. Kibana 4 requires its own web tier as explained here: https://github.com/elasticsearch/kibana/issues/1628#issuecomment-58611294

@fangli may I suggest a small explanation in the Readme like this one: https://github.com/hmalphettes/kibana-proxy/commit/f3e9d254dea35ddb15d5e34ae2eb7e5cc9293c24

hmalphettes avatar Feb 12 '15 06:02 hmalphettes