Nakama-dotnet: Error reading message from client, read tcp ... i/o timeout

Client Libraries
,
1 
nakama    | {"level":"info","ts":"2023-06-27T03:39:22.365Z","caller":"server/session_ws.go:80","msg":"New WebSocket session connected","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46","format":0}
nakama    | {"level":"debug","ts":"2023-06-27T03:39:22.366Z","caller":"server/tracker.go:907","msg":"Processing presence event","joins":1,"leaves":0}
nakama    | {"level":"debug","ts":"2023-06-27T03:39:24.297Z","caller":"server/pipeline.go:65","msg":"Received *rtapi.Envelope_MatchmakerAdd message","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46","cid":"1","message":{"MatchmakerAdd":{"min_count":2,"max_count":2,"query":"*","string_properties":{"region":"europe"},"numeric_properties":{"rank":8}}}}
nakama    | {"level":"debug","ts":"2023-06-27T03:39:24.304Z","caller":"server/session_ws.go:395","msg":"Sending *rtapi.Envelope_MatchmakerTicket message","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46","envelope":"cid:\"1\"  matchmaker_ticket:{ticket:\"eb7e745e-3bc3-48ba-9cd3-dab6d6d343a8\"}"}

About 15 seconds later…
Errors:

nakama    | {"level":"debug","ts":"2023-06-27T03:39:47.374Z","caller":"server/session_ws.go:204","msg":"Error reading message from client","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46","error":"read tcp 172.18.0.3:7350->172.18.0.1:53996: i/o timeout"}
nakama    | {"level":"info","ts":"2023-06-27T03:39:47.375Z","caller":"server/session_ws.go:438","msg":"Cleaning up closed client connection","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46"}
nakama    | {"level":"info","ts":"2023-06-27T03:39:47.377Z","caller":"server/session_ws.go:446","msg":"Cleaned up closed connection matchmaker","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46"}
nakama    | {"level":"info","ts":"2023-06-27T03:39:47.377Z","caller":"server/session_ws.go:450","msg":"Cleaned up closed connection tracker","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46"}
nakama    | {"level":"debug","ts":"2023-06-27T03:39:47.378Z","caller":"server/tracker.go:907","msg":"Processing presence event","joins":0,"leaves":1}
nakama    | {"level":"info","ts":"2023-06-27T03:39:47.378Z","caller":"server/session_ws.go:454","msg":"Cleaned up closed connection status registry","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46"}
nakama    | {"level":"info","ts":"2023-06-27T03:39:47.379Z","caller":"server/session_ws.go:458","msg":"Cleaned up closed connection session registry","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46"}
nakama    | {"level":"info","ts":"2023-06-27T03:39:47.379Z","caller":"server/session_ws.go:517","msg":"Closed client connection","uid":"123c4200-e1ad-4b65-9e57-d29ed6ace97a","sid":"34850fff-149c-11ee-b686-7106fdcb5b46"}
nakama    | {"level":"info","ts":"2023-06-27T03:55:32.739Z","caller":"server/session_ws.go:80","msg":"New WebSocket session connected","uid":"abcb152f-6e55-4b40-8ec5-398f50f11229","sid":"76e86fba-149e-11ee-b686-7106fdcb5b46","format":0}
nakama    | {"level":"debug","ts":"2023-06-27T03:55:32.740Z","caller":"server/tracker.go:907","msg":"Processing presence event","joins":1,"leaves":0}
2

Hello @xiaodong-ji,

These logs do not indicate an error on the server but rather that the socket connection was mishandled by the client or suffered from a network issue.