# Having issue bringing accessing Kibana UI

**URL:** https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545
**Category:** Kibana
**Created:** [June 19, 2019, 9:14pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545 "2019-06-19T21:14:09Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![chowdary1110](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@chowdary1110](https://discuss.elastic.co/u/chowdary1110)
#### Post date: [June 19, 2019, 9:14pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/1 "2019-06-19T21:14:09Z")

</div>

I installed 7.1.1 version of Kibana,Elastic search and tried binging Kibana up with the required changes. I am fairly new the the installation on elastic search stack. Not sure if I am missing anything.

I see port listening and logs doesn't have any errors when I start Kibana. I am not able to access the url though. When I did check for verbose curl  
curl [http://localhost:5601](http://localhost:5601) (Doesn't give any output)  
curl -v -L [http://localhost:5601](http://localhost:5601) (Below is the end snippet which I thought would be helpful to debug)

Loading Kibana

## Please upgrade your browser

This Kibana installation has strict security requirements enabled that your current browser does not meet.

// Since this script tag does not contain a nonce, this code will not run

// in browsers that support content security policy(CSP). This is

// intentional as we check for the existence of **kbnCspNotEnforced** in

// bo

---

<div class="post-metadata">

### Author: ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)
#### Post date: [June 19, 2019, 9:26pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/2 "2019-06-19T21:26:31Z")

</div>

Yes, we've introduced a [content security policy](https://en.wikipedia.org/wiki/Content_Security_Policy) in Kibana to prevent common security attacks. Because curl isn't a browser that supports content security policy, you got this error message. If you try accessing Kibana in a modern browser, things should load up just fine. 🙂

---

<div class="post-metadata">

### Author: ![yogeswararao](https://avatars.discourse-cdn.com/v4/letter/y/85e7bf/32.png) [@yogeswararao](https://discuss.elastic.co/u/yogeswararao)
#### Post date: [June 19, 2019, 9:45pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/3 "2019-06-19T21:45:32Z")

</div>

Hi Lukas,

what do you mean modern browser ? we tried it in the same url in Google chrome browser , IE is not working. could you please share some documentation do need to update any settings either kibana or ES side ?

Regards,  
Yogesh

---

<div class="post-metadata">

### Author: ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)
#### Post date: [June 19, 2019, 11:14pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/4 "2019-06-19T23:14:35Z")

</div>

When you load up Kibana in the browser, do you get the same error message as above? (Please upgrade your browser)

---

<div class="post-metadata">

### Author: ![chowdary1110](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@chowdary1110](https://discuss.elastic.co/u/chowdary1110)
#### Post date: [June 19, 2019, 11:51pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/5 "2019-06-19T23:51:40Z")

</div>

Nope. I am not getting any results in the browser and am seeing continuous loading screen. The snippet I posted is from a curl call on the machine.

---

<div class="post-metadata">

### Author: ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)
#### Post date: [June 20, 2019, 3:32pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/6 "2019-06-20T15:32:04Z")

</div>

Are you getting any browser console errors? Have you enabled verbose logging on the Kibana server to see if there is anything helpful there?

---

<div class="post-metadata">

### Author: ![chowdary1110](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@chowdary1110](https://discuss.elastic.co/u/chowdary1110)
#### Post date: [June 20, 2019, 4:25pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/7 "2019-06-20T16:25:12Z")

</div>

Hi Lukas,  
I enabled verbose logging and I see Kibana is up on [http://localhost:5601](http://localhost:5601) and also log is getting rotated as well. No errors were noticed in the logs. I used default Kibana.yml just enabling basic properties. Should I post the log?

---

<div class="post-metadata">

### Author: ![chowdary1110](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@chowdary1110](https://discuss.elastic.co/u/chowdary1110)
#### Post date: [June 20, 2019, 4:26pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/8 "2019-06-20T16:26:54Z")

</div>

After loading for certain time on browser, I see a generic message that it cannot reach to the url and this might be because of a firewall issue, etc.

---

<div class="post-metadata">

### Author: ![chowdary1110](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@chowdary1110](https://discuss.elastic.co/u/chowdary1110)
#### Post date: [June 20, 2019, 5:12pm UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/9 "2019-06-20T17:12:14Z")

</div>

Hi Lukas,

Below is from Kibana log.

{"type":"log","@timestamp":"2019-06-19T05:53:45Z","tags":["debug","server"],"pid":1844,"message":"starting server"}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","http","server"],"pid":1844,"message":"starting http server"}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","http","server"],"pid":1844,"message":"http server running at [http://localhost:5601](http://localhost:5601)"}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","plugins-service"],"pid":1844,"message":"Starting plugins service"}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","config"],"pid":1844,"message":"Marking config path as handled: plugins"}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","plugins-discovery"],"pid":1844,"message":"Discovering plugins..."}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","plugins-discovery"],"pid":1844,"message":"Scanning "/src/plugins" for plugin sub-directories..."}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","plugins-discovery"],"pid":1844,"message":"Scanning "/plugins" for plugin sub-directories..."}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","plugins-discovery"],"pid":1844,"message":"Scanning "/kibana-extra" for plugin sub-directories..."}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","plugins-service"],"pid":1844,"message":"Discovered 0 plugins."}  
{"type":"log","@timestamp":"2019-06-19T05:53:46Z","tags":["debug","legacy-service"],"pid":1844,"message":"starting legacy service"}  
{"type":"log","@timestamp":"2019-06-19T05:53:47Z","tags":["debug","config"],"pid":1844,"message":"Marking config path as handled: server"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/node\_modules/x-pack","message":"Found plugin at /usr/share/kibana/node\_modules/x-pack"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["debug","legacy-proxy"],"pid":1844,"message":""getConnections" has been called."}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/apm\_oss","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/apm\_oss"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/console","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/console"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/elasticsearch","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/elasticsearch"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/inspector\_views","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/inspector\_views"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/interpreter","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/interpreter"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/kbn\_doc\_views","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/kbn\_doc\_views"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/input\_control\_vis","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/input\_control\_vis"}  
{"type":"log","@timestamp":"2019-06-19T05:54:04Z","tags":["plugin","debug"],"pid":1844,"path":"/usr/share/kibana/src/legacy/core\_plugins/kbn\_vislib\_vis\_types","message":"Found plugin at /usr/share/kibana/src/legacy/core\_plugins/kbn\_vislib\_vis\_types"}

---

<div class="post-metadata">

### Author: ![chowdary1110](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@chowdary1110](https://discuss.elastic.co/u/chowdary1110)
#### Post date: [June 21, 2019, 5:50am UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/10 "2019-06-21T05:50:36Z")

</div>

Hi Lukas,  
I was able to bring Kibana Up. Kibana is always up but it was firewall that was blocking the UI access. Sorry for troubling you and thanks for the quick reply.

---

<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: [July 19, 2019, 5:50am UTC](https://discuss.elastic.co/t/having-issue-bringing-accessing-kibana-ui/186545/11 "2019-07-19T05:50:37Z")

</div>

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