TCP Out of Order in Kibana

kibana version: 7.6.1

I have a proxy server(IIS) in front of Kibana server.
Bad Gateway 502 errors are often seen in browsers.
Error logs are not accumulated in kibana and elasticsearch.

So when I run 'tcpdump', the proxy sends a request, and the kibana disconnects the request.
like this.....

The current Kibana log level is verbose, and the request is not recorded at all.
(Confirmation with 'X-ARR-LOG-ID')

In general, if the order of requests in TCP communication is incorrect, correcting the order by communicating with each other.
Why is kibana disconnecting immediately?

Can i fix this?

That shouldn't be a problem. Maybe there is another underlying problem there.

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