# I am unable to run Kibana 8.6.1 from browser

**URL:** <https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [April 2, 2023, 10:42pm UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137 "2023-04-02T22:42:02Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aysh14](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Aysh14](https://discuss.elastic.co/u/Aysh14)\
**Post date:** [April 2, 2023, 10:42pm UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/1 "2023-04-02T22:42:02Z")

</div>

Hi Team,

I am unable to connect to kibana from browser. I have installed Kibana, 8.6.1 . I am getting  
HTTP/1.1 302 Found when I do a curl on the URL from the VM , but unable to get response when I try to access from browser. Request for guidance to solve this one .

---

<div class="post-metadata">

**Author:** ![Aysh14](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Aysh14](https://discuss.elastic.co/u/Aysh14)\
**Post date:** [April 2, 2023, 10:45pm UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/2 "2023-04-02T22:45:19Z")

</div>

@vansh I had seen in the discussion board that you too faced a similar challenge . Can you please guide on how you resolved it . I tried incognito too .

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 4, 2023, 1:39am UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/3 "2023-04-04T01:39:28Z")

</div>

Welcome to our community! 😃

Can you share the full curl and response please?

---

<div class="post-metadata">

**Author:** ![Aysh14](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Aysh14](https://discuss.elastic.co/u/Aysh14)\
**Post date:** [April 4, 2023, 2:37am UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/4 "2023-04-04T02:37:58Z")

</div>

Thank you Mark for the welcome 🙂

If I curl the from the VM where the service is running, I am getting the below message:

curl -v "[https://dnsname/kibana/](https://dnsname/kibana/)"

HTTP/1.1 302 Found  
Location: /login?next=%2F  
x-content-type-options: nosniff  
referrer-policy: no-referrer-when-downgrade  
content-security-policy: script-src 'self' 'unsafe-eval'; worker-src blob: 'self'; style-src 'unsafe-inline' 'self'  
Kbn-name: nameOfKibana  
Kbn-license-sig: some serial number  
Cache-control  
Content  
X-envoy-upsteam-service-time: 9  
Server: istio-envoy

Hey Mark , the above is the response I get on doing curl. Actually I am typing each line same as what output I saw when I ran the command on the VM

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 4, 2023, 2:40am UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/5 "2023-04-04T02:40:06Z")

</div>

Are you using our ECK operator?

---

<div class="post-metadata">

**Author:** ![Aysh14](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Aysh14](https://discuss.elastic.co/u/Aysh14)\
**Post date:** [April 4, 2023, 2:44am UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/6 "2023-04-04T02:44:38Z")

</div>

Yes . Using ECK operator. Operator version 2.6

---

<div class="post-metadata">

**Author:** ![Aysh14](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Aysh14](https://discuss.elastic.co/u/Aysh14)\
**Post date:** [April 4, 2023, 3:00am UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/7 "2023-04-04T03:00:49Z")

</div>

Are there any changes required in the operator yaml ? Also, I am getting error connecting to fleet registry error in Kibana Logs. I am okay with even disabling my fleet. Is this causing an issue in opening kibana through browser ? Please suggest. Thank you in advance.

---

<div class="post-metadata">

**Author:** ![Aysh14](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Aysh14](https://discuss.elastic.co/u/Aysh14)\
**Post date:** [April 4, 2023, 3:50pm UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/8 "2023-04-04T15:50:10Z")

</div>

Please advise

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [April 12, 2023, 5:10am UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/9 "2023-04-12T05:10:38Z")

</div>

Hi,

> [@Aysh14](#):
>
> Server: istio-envoy

I think you are using Istio? I'm definitely not an Isitio expert, but would it be possible to do a test bypassing the Envoy proxy? It would help to understand if you are facing a configuration issue with Envoy.  
We have also [an Istio recipe](https://github.com/elastic/cloud-on-k8s/blob/main/config/recipes/istio-gateway/03-elasticsearch-kibana.yaml#L98), it's not up to date, but I noticed there are some annotations to let the traffic flow between components, maybe that could help.

---

<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:** [May 10, 2023, 5:11am UTC](https://discuss.elastic.co/t/i-am-unable-to-run-kibana-8-6-1-from-browser/329137/10 "2023-05-10T05:11:29Z")

</div>

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