Tls errors in the temporal logs

Hi Everyone,
We see this error in our frontend, matching, history services. grpc_health_probe health checks looks serving. Workflows look good in UI. Any ideas how to fix this.
“msg”:“matching client encountered error”,“service”:“history”,“error”:“last connection error: connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake"”,“service-error-type”:“serviceerror.Unavailable”,“logging-call-at”:“metricClient.go:259”,“stacktrace”:"*zapLogger)

The error message appears to relate to incorrectly configured mTLS certs. Are you able to share the complete stacktrace by any chance?

Errors stopped by itself but we observed the opensearch had a huge latency at same time. Do you happen to know if its related?