# After 5.4 upgrade, problems with Dev Tools

**URL:** <https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166>\
**Category:** Elasticsearch\
**Created:** [May 9, 2017, 10:16pm UTC](https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166 "2017-05-09T22:16:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![prodrg](https://avatars.discourse-cdn.com/v4/letter/p/3bc359/32.png) [@prodrg](https://discuss.elastic.co/u/prodrg)\
**Post date:** [May 9, 2017, 10:16pm UTC](https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166/1 "2017-05-09T22:16:50Z")

</div>

Hello everybody,

After upgrading the stack to 5.4 (with X-Pack enabled before and SSL settings), I am receiving the following issue using the console on Kibana:

```
{
  "statusCode": 502,
  "error": "Bad Gateway",
  "message": "unable to verify the first certificate"
}

```

I shall indicate that I'm using the same settings from the 5.3 version and there were no problems with certificates. Why is this problem happening?

---

<div class="post-metadata">

**Author:** ![Benoit-DunandLaisin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benoit-dunandlaisin/32/10726_2.png) [@Benoit-DunandLaisin](https://discuss.elastic.co/u/Benoit-DunandLaisin)\
**Post date:** [May 10, 2017, 12:36pm UTC](https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166/2 "2017-05-10T12:36:00Z")

</div>

Hi, I got the same issue. Still no clue.

---

<div class="post-metadata">

**Author:** ![sergiolr100](https://avatars.discourse-cdn.com/v4/letter/s/9de0a6/32.png) [@sergiolr100](https://discuss.elastic.co/u/sergiolr100)\
**Post date:** [May 17, 2017, 8:46am UTC](https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166/3 "2017-05-17T08:46:43Z")

</div>

Hi all!

Someone could solve this?

Thanks.

---

<div class="post-metadata">

**Author:** ![Benoit-DunandLaisin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benoit-dunandlaisin/32/10726_2.png) [@Benoit-DunandLaisin](https://discuss.elastic.co/u/Benoit-DunandLaisin)\
**Post date:** [May 17, 2017, 2:40pm UTC](https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166/4 "2017-05-17T14:40:59Z")

</div>

Hi, it's a known issue which should be fixed in 5.4.1: [https://github.com/elastic/kibana/issues/10984](https://github.com/elastic/kibana/issues/10984)

Adding this to kibana.yml is the workaround:

```
console.proxyConfig:
    - ssl.verify: false
```

---

<div class="post-metadata">

**Author:** ![prodrg](https://avatars.discourse-cdn.com/v4/letter/p/3bc359/32.png) [@prodrg](https://discuss.elastic.co/u/prodrg)\
**Post date:** [May 17, 2017, 2:46pm UTC](https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166/5 "2017-05-17T14:46:42Z")

</div>

Thanks @Benoit-DunandLaisin. The workaround is doing great.

---

<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:** [June 14, 2017, 2:47pm UTC](https://discuss.elastic.co/t/after-5-4-upgrade-problems-with-dev-tools/85166/6 "2017-06-14T14:47:16Z")

</div>

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