Pallab•3mo ago

Connection reset by peer

Ever since upgrading to v2.71.9 and henceforth, I am seeing many connection reset errors like the following. Is there some configuration that I can tweak to mitigate this?

get user from zitadel, error: rpc error: code = Unavailable desc = error reading from server: read tcp 10.230.54.27:55668->34.233.181.143:443: read: connection reset by peer "}

get user from zitadel, error: rpc error: code = Unavailable desc = error reading from server: read tcp 10.230.54.27:55668->34.233.181.143:443: read: connection reset by peer "}

Thanks.

3 Replies

FFO•3mo ago

Do you see this in our cloud service or your own deployment?

PallabOP•3mo ago

It's a self-hosted deployment running on AWS EKS and uses Postgres RDS.

FFO•3mo ago

Perfect, thanks for sharing. I guess your app is calling the grpc api from zitadel in that case. Do you see some logs on zitadels side at this time? One should not often see this error, since it means the http server from zitadel was not reachable. Which only would happen in a restart/panic. Can it be that the LB has a connectivity issue to the zitadel pod?

Connection reset by peer

Did you find this page helpful?