# Kibana infinite loop with elastic operator on Kubernetes

**URL:** <https://discuss.elastic.co/t/kibana-infinite-loop-with-elastic-operator-on-kubernetes/246145>\
**Category:** Kibana\
**Created:** [August 24, 2020, 3:15pm UTC](https://discuss.elastic.co/t/kibana-infinite-loop-with-elastic-operator-on-kubernetes/246145 "2020-08-24T15:15:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pup\_seba](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pup_seba/32/42988_2.png) [@pup\_seba](https://discuss.elastic.co/u/pup_seba)\
**Post date:** [August 24, 2020, 3:15pm UTC](https://discuss.elastic.co/t/kibana-infinite-loop-with-elastic-operator-on-kubernetes/246145/1 "2020-08-24T15:15:25Z")

</div>

Hi,

So I'm facing this issue that seems to be around for a long time and dealt with in different manners, yet, I don't see a way to deal with it when using ECK. Any ideas on how to fix the kibana "infinite loop" (302) when trying to access it?

- ECK 1.2
- Elastic Stack 7.8.1  
This error happens even with a curl from within kibana pod `curl http://localhost:5601/personalized-path -L`  
This is the kibana relevant configuration for this issue:

```auto
spec:
  config:
    server.basePath: "/personalized-path"
    server.rewriteBasePath: false
    xpack.security.secureCookies: false
  http:
    tls:
      selfSignedCertificate:
        disabled: true

```

I've tried different combinations of rewriteBasePath and secureCookies, but no luck with those.

Also relevant, this kibana is behind a proxy that uses https, so lab users will be connecting to "[https://someurl/personalized-path/](https://someurl/personalized-path/)" which will get redirected to the proper k8s service and then get to the kibana service on http.

Thank you!

---

<div class="post-metadata">

**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\
**Post date:** [August 24, 2020, 5:29pm UTC](https://discuss.elastic.co/t/kibana-infinite-loop-with-elastic-operator-on-kubernetes/246145/2 "2020-08-24T17:29:48Z")

</div>

This sounds like an issue with the proxy settings and their interaction with the Kibana settings. What are your proxy settings?

---

<div class="post-metadata">

**Author:** ![pup\_seba](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pup_seba/32/42988_2.png) [@pup\_seba](https://discuss.elastic.co/u/pup_seba)\
**Post date:** [August 24, 2020, 6:24pm UTC](https://discuss.elastic.co/t/kibana-infinite-loop-with-elastic-operator-on-kubernetes/246145/3 "2020-08-24T18:24:07Z")

</div>

Hi!

The issue happens with a curl from the container itself like "curl [http://localhost:5601/personalized-path/login](http://localhost:5601/personalized-path/login) -L". That would leave the proxy out of the equation (at least for now 🙂 ).

This is fixed now, but I'm still not being able to make it work as intended but I'll close this topic and open a new one.

The configuration that worked is the same as shown above, only that the rewrite has to be `true` and the curl, needs to hit the path like this "/personalized-path/login"

Thank you wylie!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 21, 2020, 6:24pm UTC](https://discuss.elastic.co/t/kibana-infinite-loop-with-elastic-operator-on-kubernetes/246145/4 "2020-09-21T18:24:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.