Kibana randomly giving 502 bad gateway error

Hi,

I am run EFK stack on Kubernetes for logging. For elasticseach we have 2 data, 1 master and 1 client node. Everything is working fine but i randomly get 502 bad gateway error.

From dashboard:

Discover: Bad Gateway

SearchError: Bad Gateway
    at https://kibana.logging.stakater.com/bundles/kibana.bundle.js:2:579398
    at processQueue (https://kibana.logging.stakater.com/built_assets/dlls/vendors.bundle.dll.js:307:199687)
    at https://kibana.logging.stakater.com/built_assets/dlls/vendors.bundle.dll.js:307:200650
    at Scope.$digest (https://kibana.logging.stakater.com/built_assets/dlls/vendors.bundle.dll.js:307:210412)
    at Scope.$apply (https://kibana.logging.stakater.com/built_assets/dlls/vendors.bundle.dll.js:307:213219)
    at done (https://kibana.logging.stakater.com/built_assets/dlls/vendors.bundle.dll.js:307:132717)
    at completeRequest (https://kibana.logging.stakater.com/built_assets/dlls/vendors.bundle.dll.js:307:136329)
    at XMLHttpRequest.requestLoaded (https://kibana.logging.stakater.com/built_assets/dlls/vendors.bundle.dll.js:307:135225)

Endpoint triggered that is giving error:
https://kibana.logging.stakater.com/elasticsearch/_msearch?rest_total_hits_as_int=true&ignore_throttled=true

I have updated my nginx configuration etc. but still unable to resolve this.

P.s. Let me know if more information is required from my side

Hey @ahmedwaleedmalik, do your Kibana logs contain additional information regarding the error? Also, if you capture a HAR of the request which is causing the 502, it'll help us diagnose further.

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