# Unable to launch Kibana after upgrade to 7.7.0

**URL:** <https://discuss.elastic.co/t/unable-to-launch-kibana-after-upgrade-to-7-7-0/234654>\
**Category:** Elasticsearch\
**Created:** [May 28, 2020, 5:18am UTC](https://discuss.elastic.co/t/unable-to-launch-kibana-after-upgrade-to-7-7-0/234654 "2020-05-28T05:18:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![skyluke.1987](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@skyluke.1987](https://discuss.elastic.co/u/skyluke.1987)\
**Post date:** [May 28, 2020, 5:18am UTC](https://discuss.elastic.co/t/unable-to-launch-kibana-after-upgrade-to-7-7-0/234654/1 "2020-05-28T05:18:24Z")

</div>

Hi all, yesterday I tried to upgrade my ELKS from 7.1 to 7.7. After the upgrade I am able to run the services and when I check its working and running. Just that I am not able to browse the site.

But there are following errors found:

Filebeat - ERROR instance/beat.go:932 Exiting: 1 error: invalid config: yaml: line 10: mapping values are not allowed in this context

ES:  
[master-node] policy [filebeat-7.1.1] for index [filebeat-7.1.1-2020.05.27] on an error step due to a transitive error, moving back to the failed step [check-rollover-ready] for execution. retry attempt [110]  
[2020-05-28T13:09:30,259][INFO][o.e.x.i.IndexLifecycleRunner] [master-node] policy [heartbeat-7.1.1] for index [heartbeat-7.1.1-2020.05.28] on an error step due to a transitive error, moving back to the failed step [check-rollover-ready] for execution. retry attempt [39]

After I have deleted all the indices the error changed to: [o.e.x.s.a.AuthenticationService] [master-node] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]

Please advise should I remove all the old indices ?

---

<div class="post-metadata">

**Author:** ![skyluke.1987](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@skyluke.1987](https://discuss.elastic.co/u/skyluke.1987)\
**Post date:** [June 5, 2020, 3:55pm UTC](https://discuss.elastic.co/t/unable-to-launch-kibana-after-upgrade-to-7-7-0/234654/2 "2020-06-05T15:55:26Z")

</div>

Does anyone faced this issue after upgrade?

Besides that, I notice that my X-Pack does not work properly too, so I temporary disabled it. What do I need to do to fix it? I suspect that some other modules like Heartbeat-elastic (For Uptime) will need that in order to enable the Alerts system, is that true?

---

<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 3, 2020, 3:55pm UTC](https://discuss.elastic.co/t/unable-to-launch-kibana-after-upgrade-to-7-7-0/234654/3 "2020-07-03T15:55:33Z")

</div>

Closed on July 3, 2020, 3:55pm UTC

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