# Random 502 in POST request

**URL:** <https://discuss.konghq.com/t/random-502-in-post-request/7423>\
**Category:** General\
**Created:** [November 10, 2020, 4:11pm UTC](https://discuss.konghq.com/t/random-502-in-post-request/7423 "2020-11-10T16:11:17Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Robert.Kapala](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/robert.kapala/32/1993_2.png) [@Robert.Kapala](https://discuss.konghq.com/u/Robert.Kapala)\
**Post date:** [November 13, 2020, 11:11am UTC](https://discuss.konghq.com/t/random-502-in-post-request/7423/5 "2020-11-13T11:11:09Z")

</div>

Looks like we have the same issue:

> [@502 & Keepalive connection closed, AWS/CloudFront + classic LB + Kong (K8s)](https://discuss.konghq.com/t/502-keepalive-connection-closed-aws-cloudfront-classic-lb-kong-k8s/7397/2):
>
> How can I disable keepalive functionality in Kong? It’s not clear to me from the description whether this will solve your problem, but to your specific question, here’s how to disable the upstream keepalive — note however that this is likely to have a performance impact: [https://docs.konghq.com/2.1.x/configuration/#upstream\_keepalive\_pool\_size](https://docs.konghq.com/2.1.x/configuration/#upstream_keepalive_pool_size) Depending on your upstream’s behavior, you may want to tune the other related options upstream\_keepalive\_max\_requests and upstream\_keepalive\_idle\_ti…

Did not found solution for it. Disabling keepalive feature on Kong did not help.

---

_[View the full topic](https://discuss.konghq.com/t/random-502-in-post-request/7423)._