# How to find the root cause for config update error

**URL:** <https://discuss.konghq.com/t/how-to-find-the-root-cause-for-config-update-error/12041>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [October 31, 2023, 4:30pm UTC](https://discuss.konghq.com/t/how-to-find-the-root-cause-for-config-update-error/12041 "2023-10-31T16:30:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fkbarrett](https://avatars.discourse-cdn.com/v4/letter/f/3ab097/32.png) [@fkbarrett](https://discuss.konghq.com/u/fkbarrett)\
**Post date:** [October 31, 2023, 4:30pm UTC](https://discuss.konghq.com/t/how-to-find-the-root-cause-for-config-update-error/12041/1 "2023-10-31T16:30:23Z")

</div>

We are running Kong with the Ingress Controller, db-less. When we tried upgrading to Kong 3.4, KIC 2.28, we see a “failed posting new config” error (see below). The generic question is: How do we find the root cause when we see such an error? There is no indication for what is wrong.

```auto
level=error msg="could not update kong admin" error="performing update for https://localhost:8444 failed: failed posting new config to /config: got status code 400" subsystem=dataplane-synchronizer

```

---

<div class="post-metadata">

**Author:** ![JohnWilliams](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/johnwilliams/32/4230_2.png) [@JohnWilliams](https://discuss.konghq.com/u/JohnWilliams)\
**Post date:** [November 6, 2023, 4:08pm UTC](https://discuss.konghq.com/t/how-to-find-the-root-cause-for-config-update-error/12041/2 "2023-11-06T16:08:25Z")

</div>

Not sure if its relevant but did you look at the Kubernetes events which can contain information on config failures.

> **[Kubernetes Events - v2.12.x | Kong Docs](https://docs.konghq.com/kubernetes-ingress-controller/latest/references/kubernetes-events/)**
>
> Documentation for Kong, the Cloud Connectivity Company for APIs and Microservices.

---

<div class="post-metadata">

**Author:** ![fkbarrett](https://avatars.discourse-cdn.com/v4/letter/f/3ab097/32.png) [@fkbarrett](https://discuss.konghq.com/u/fkbarrett)\
**Post date:** [November 6, 2023, 10:15pm UTC](https://discuss.konghq.com/t/how-to-find-the-root-cause-for-config-update-error/12041/3 "2023-11-06T22:15:06Z")

</div>

@JohnWilliams Thanks! I check Kubernetes events for other issues but didn’t think to check for a Kong config issue. We’ve rolled back for now, but will try again soon, and will keep this in mind.