# X-Pack Monitoring screen error after ES upgrade

**URL:** https://discuss.elastic.co/t/x-pack-monitoring-screen-error-after-es-upgrade/93602
**Category:** Elasticsearch
**Created:** [July 18, 2017, 2:33pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-screen-error-after-es-upgrade/93602 "2017-07-18T14:33:18Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Lean](https://avatars.discourse-cdn.com/v4/letter/l/ac91a4/32.png) [@Lean](https://discuss.elastic.co/u/Lean)
#### Post date: [July 28, 2017, 8:29pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-screen-error-after-es-upgrade/93602/5 "2017-07-28T20:29:30Z")

</div>

Hey Tim,

Yes, I see exactly that, using my authentication info with [http://es-host:9200/\_xpack](http://es-host:9200/_xpack). That's correct.

Unfortunately I cannot go through monitoring tab in kibana page, who gives always that "Monitoring: Error 404 Not Found: undefined" message.

Of course now the version is 5.5.1 and Build: 15405, but the message is still there.

In kibana.log message I see a repetitive message telling me that "License information could not be obtained from Elasticsearch. [security\_exception] missing authentication token for REST request", even though I double checked kibana.yml settings and verified (I guess) user and role info in kibana.

What now? How can I further debug this? Is it really a licensing problem?

Thank you!  
Leandro.

---

_[View the full topic](https://discuss.elastic.co/t/x-pack-monitoring-screen-error-after-es-upgrade/93602)._