-
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
ERR_TOO_MANY_REDIRECTS #9226
Comments
The problem is gone uninstalling x-pack . |
Looks that x-pack was not properly installed on elasticsearch too. |
Thanks for submitting. Yes, you are right, XPack needs to be installed on both Kibana and ES. |
Hi, nginx-->kibana(over docker swarm)-->elasticsearch (over docker swarm) here is my vhost: `
} |
Btw, those are the docker images that I am using: docker.elastic.co/kibana/kibana:5.1.1 |
Installing in a Debian from Elastic Repos with latest version happens the same. This is kibana log: |
Having the same issue. I have x-pack installed on both Kibana and ES. If I remove the x-pack it works fine. |
I found this thread when having this issue and then I remembered the fix ( for my system anyway ). I am running all this in docker container so, again, perhaps completely irrelevant but I need to increase the |
@matarrese or anyone else |
Was running into something similar. It turned out our problem had to do with not using the correct user as the configuration file was read from /etc/kibana/kibana.yml, but we put the config file on /opt/kibana/config/kibana.yml. |
Thanks @bbenning for the hint. I think i got it solved on our server. Kibana is running in Docker behind a nginx-reverse proxy in this scenario:
My "solution" was to mount the config file
and to comment out the default user credentials:
And the redirect loop was gone. |
Hello, My setup is: apache and kibana are on the same server but elasticsearch is on another server. After the x-pack installation, I got an ERR_TOO_MANY_REDIRECTS. error message. Here, you can find my apache config:
My /etc/kibana/kibana.yml:
Do you know where is the problem ? |
Hello, Why do not show error message when credentials are not correct ? |
This has been resolved as of 5.6.0 |
Just hit this with 6.1.1.
Incognito worked. Had to remove the cookie / SID from Chrome. Haven't fixed Safari, because it appears I can't clear the cookies just for the specific domain. |
I hit this issue nearly once a week now, would be nice if this could get some attention. Deleting the SID cookie clears it up immediately. I feel bad for any user that has to discover this on their own. |
Same, this issue is very common for us, and clearing the SID cookie solves the issue. Not sure if it's relevant, but we use both a SAML realm hooked up to Okta (for engineers) and a native realm (for services) to authenticate. For the SAML realm, we don't have Single Logout configured, and I wonder if that's maybe causing it, but I haven't tried it yet. That might be the next thing I try. |
I'm seeing the same thing here with SAML (Okta) setup with x-pack - every week or two, I'll need to delete the cookie for the kibana instance and then it works again. Anyone aware of a more permanent fix? |
Any plans on fixing this issue? It happens 100% of time time I sign in to Kibana via Okta, and it's frustrating to have to clear the cookies and open a new tab. |
Liebe Kunden, Freunde und Spammer,
wir sind derzeit im Urlaub.
Ab Montag, 7.1.2019 sind wir wieder wie gewohnt für euch/Sie da.
Wir wünschen Ihnen einen guten Start ins neue Jahr!
Liebe Grüße
Oliver Köhler
|
@elastic/kibana-security |
Anyone experiencing this with SAML, if you could share your kibana logs with |
Steps to reproduce:
It seems like the Kibana authentication logic cannot handle the case when there is already an existing session for a user. |
Hey @mgartner, would you be able to set |
@kobelb we're experiencing this with SAML running on v6.3.1 (I work with @mgartner). I'll work on getting some logs with On the ElasticSearch side of things. The documents used to store the sessions in the The issue above results in Kibana not clearing an invalid |
@kobelb what's a good email to send you the logs? |
@kobelb here are the Kibana when this issue occurred. I've included 2min before and after the issue happened. |
@kobelb any updates? |
@dmlittle would you mind confirming that if the user clears their cookies, and tries to login again that they're able to successfully login? I'm seeing the following error in your Kibana logs:
This is occurring because we're trying to use the access token stored in the user's session (persisted using a cookie) to authenticate the user, and we're getting back an unexpected error, so we aren't proceeding to use the SAML payload provided by the IdP to authenticate the end-user. |
@kobelb yes clearing the |
Thanks for the confirmation @dmlittle, i'll work on resolving the issue that you're seeing. |
@kobelb I just hit this with 7.0.0-rc2-37e4e7a4. Single kibana going to single elasticsearch, native realm only. I do set the |
@jpcarey if you could share your Kibana logs with |
If running into this check your server.basePath settings
led to
but …
I had nginx redirecting
in nginx So Basically, Kibana is doing the rewriting for nginx now, which simplifies the nginx config quite a bit. ERR_TOO_MANY_REDIRECTS happened when I tried to set |
This issue hasn't had any activity in quite some time, so I'm looking for feedback - has anyone encountered this in a recent version of Kibana? Maybe anything since 7.5.0? We've made a number of improvements to session handling in the 7.x timeframe, so it's possible this is no longer a problem |
@legrego we're still on 7.3.1 but the issue seems to be resolved on this version |
I'm going to consider this resolved since we've had no recent reports or feedback since we've improved the authentication flow. If anyone is still experiencing this, please do not hesitate to open a new issue with your specific error scenario. Thanks all for your patience and help as we worked through this! |
I'm suddenly experiencing this issue.. with 7.4.2 :( restarting fixes it, but the error comes back after a while
|
Is there a configuration fix for this?
|
Experienced ERR_TOO_MANY_REDIRECTS while running Kibana behind the Nginx reverse proxy. Solution: https://serverfault.com/a/1142129/486965 (corrected Nginx configuration) |
Kibana version:5
Elasticsearch version:5
Server OS version:debian
Browser version:wget
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Description of the problem including expected versus actual behavior:
Hi, if I try to connect to kibana with wget to localhost:5601, or from a browser I get the same problem:
Provide logs and/or server output (if relevant):
matarrese@instance-2-elasticsearch:~$ wget http://localhost:5601/
--2016-11-27 21:21:43-- http://localhost:5601/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:5601... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:5601... connected.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
--2016-11-27 21:21:43-- http://localhost:5601/login?next=%2F
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: / [following]
--2016-11-27 21:21:43-- http://localhost:5601/
Reusing existing connection to localhost:5601.
HTTP request sent, awaiting response... 302 Found
Location: /login?next=%2F [following]
20 redirections exceeded.
The text was updated successfully, but these errors were encountered: