# Post 6.3 Upgrade Issue: "Config: Failed to fetch"

**URL:** <https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189>\
**Category:** Kibana\
**Created:** [June 16, 2018, 7:39pm UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189 "2018-06-16T19:39:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrick\_Maroney](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_maroney/32/14352_2.png) [@Patrick\_Maroney](https://discuss.elastic.co/u/Patrick_Maroney)\
**Post date:** [June 16, 2018, 7:39pm UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189/1 "2018-06-16T19:39:13Z")

</div>

Can't save any Configuration changes post 6.3 upgrade. Dead in the water as Kibana does not remember Default index, etc. and can't set/save same.

Sequence

(1) Just did a normal sudo apt-get update and upgrade on Ubuntu.

(2) Had to set server.ssl.enabled to true ("Enabling ssl by only specifying server.ssl.certificate and server.ssl.key is deprecated. Please set server.ssl.enabled to true"})

(3) Had to manually remove /usr/share/kibana/plugins ( sudo rm /usr/share/kibana/plugins -r)

"Multple plugins found with the id "xpack\_main":\n"

---

<div class="post-metadata">

**Author:** ![markdaku](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@markdaku](https://discuss.elastic.co/u/markdaku)\
**Post date:** [June 17, 2018, 7:23am UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189/2 "2018-06-17T07:23:01Z")

</div>

Thanks for the tip.

I also found that after the upgrade to 6.3 that the /usr/share/kibana/optimize/.babelcache.json was owned by root. And this caused the startup to fail. this should be owned by kibana:kibana

---

<div class="post-metadata">

**Author:** ![Patrick\_Maroney](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_maroney/32/14352_2.png) [@Patrick\_Maroney](https://discuss.elastic.co/u/Patrick_Maroney)\
**Post date:** [June 17, 2018, 4:06pm UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189/3 "2018-06-17T16:06:11Z")

</div>

Just to be clear: I'm down here and need some thoughts on how to isolate and solve the "Config:Failed to Fetch" error when I try to change Kibana settings.

Note that I did try a variant of @markdaku 's suggestion and tried:

sudo chown kibana:root /usr/share/kibana -R  
sudo chown elasticsearch:root /usr/share/elasticsearch -R

This had no impact on the issue. Help please -- I know this is an easy one once you know the secret 😉

---

<div class="post-metadata">

**Author:** ![markdaku](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@markdaku](https://discuss.elastic.co/u/markdaku)\
**Post date:** [June 18, 2018, 7:43am UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189/4 "2018-06-18T07:43:24Z")

</div>

On some of my systems I found that the new package needed to be reconfigured during the dpkg install phase. The new version 6.3 wanted to replace a lot of the config files. Which was very annoying.

Try this to force a reconfiguration of the packages. You might find that this will also give you all the files that might be missing. Again this is something that should never happen.

sudo dpkg --configure -a

---

<div class="post-metadata">

**Author:** ![markdaku](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@markdaku](https://discuss.elastic.co/u/markdaku)\
**Post date:** [June 18, 2018, 7:47am UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189/5 "2018-06-18T07:47:12Z")

</div>

Note this reconfigure does not lend itself to automation. It means we have to chuck out the env orchestration for the monitoring tools. Which just further makes it more brittle.

---

<div class="post-metadata">

**Author:** ![Patrick\_Maroney](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_maroney/32/14352_2.png) [@Patrick\_Maroney](https://discuss.elastic.co/u/Patrick_Maroney)\
**Post date:** [June 18, 2018, 4:16pm UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189/6 "2018-06-18T16:16:26Z")

</div>

Evidently a known issue. Only option is to rollback to 6.2.3.

> <https://github.com/elastic/kibana/issues/19957>

---

<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 16, 2018, 4:16pm UTC](https://discuss.elastic.co/t/post-6-3-upgrade-issue-config-failed-to-fetch/136189/7 "2018-07-16T16:16:43Z")

</div>

Closed on July 16, 2018, 4:16pm UTC

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