# Elasticsearch 5.x Kibana

**URL:** <https://discuss.elastic.co/t/elasticsearch-5-x-kibana/74521>\
**Category:** Kibana\
**Created:** [February 9, 2017, 3:20pm UTC](https://discuss.elastic.co/t/elasticsearch-5-x-kibana/74521 "2017-02-09T15:20:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sina309](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sina309/32/15020_2.png) [@sina309](https://discuss.elastic.co/u/sina309)\
**Post date:** [February 9, 2017, 3:20pm UTC](https://discuss.elastic.co/t/elasticsearch-5-x-kibana/74521/1 "2017-02-09T15:20:00Z")

</div>

somehow can't access the Elasticsearch 5.X with Kibana or Cerebro. There is an Authentification error message in different forms:

Kibana:  
You are not authorized to access Monitoring. To use Monitoring, you need the privileges granted by both the `kibana_user` and `monitoring_user` roles.

Cerebro:

> [error] p.c.s.n.PlayDefaultUpstreamHandler - Cannot invoke the action  
> play.api.libs.json.JsResultException: JsResultException(errors:List((,List(ValidationError(List('routing\_table' is undefined on object: {"error":{"root\_cause":[{"type":"security\_exception","reason":"missing  
> authentication token for REST request [/\_cluster/state/master\_node,routing\_table,routing\_nodes,blocks]","header":{"WWW-Authenticate":"Basic realm="security" charset="UTF-8""}}],"type":"security\_excepti  
> on","reason":"missing authentication token for REST request [/\_cluster/state/master\_node,routing\_table,routing\_nodes,blocks]","header":{"WWW-Authenticate":"Basic realm="security" charset="UTF-8""}},"status":401}),WrappedArray())))))

What might be the issue?

Best Regards

---

<div class="post-metadata">

**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\
**Post date:** [February 9, 2017, 6:51pm UTC](https://discuss.elastic.co/t/elasticsearch-5-x-kibana/74521/2 "2017-02-09T18:51:49Z")

</div>

Do you have the x-pack plugin installed in both Elasticsearch and Kibana?

What does Kibana log when it starts up? Any Authentication Exceptions in the log?

What user are you logging in to Kibana with? You should be able to log in as the default superuser `elastic` with password `changeme` unless you've already changed that.

Regards,  
Lee

---

<div class="post-metadata">

**Author:** ![sina309](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sina309/32/15020_2.png) [@sina309](https://discuss.elastic.co/u/sina309)\
**Post date:** [February 10, 2017, 6:17am UTC](https://discuss.elastic.co/t/elasticsearch-5-x-kibana/74521/3 "2017-02-10T06:17:39Z")

</div>

Yes, x-pack is installed on both ES 5.2 and Kibana 5.1.2. I was using `kibana` instead of `elastic`. Now it is working. But why do I get the following exception in Cerebro?

 ![](https://us1.discourse-cdn.com/elastic/original/2X/e/e7e17282558cee355304b10b2f3c852bef61b421.png)

Cerebro configuration looks like this:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/a/adbb159209599bc3f0ac831f3f362af398ea4c19.png)

---

<div class="post-metadata">

**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\
**Post date:** [February 10, 2017, 2:28pm UTC](https://discuss.elastic.co/t/elasticsearch-5-x-kibana/74521/4 "2017-02-10T14:28:25Z")

</div>

Sorry, I have no idea what Cerebro is.

The only thing I can think of trying is adding the authentication to the host URL like;

`host = "http://elastic:changeme@localhost:9200"`

Other than that, you could ask in the x-pack channel. It's more of an Elasticsearch security plugin issue than Kibana.

---

<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:** [March 10, 2017, 2:28pm UTC](https://discuss.elastic.co/t/elasticsearch-5-x-kibana/74521/5 "2017-03-10T14:28:30Z")

</div>

Closed on March 10, 2017, 2:28pm UTC

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