After a period of inactivity, the connected real-time socket stops sending updates.

I'm currently facing a critical issue with the Appwrite Realtime socket, which is related with this issue is still open.

The problem arises when there's a period of inactivity on the real-time socket. During this time, the socket stops sending any data. It behaves as if the connection has dropped, but it doesn't actually close the connection. The socket appears to be active but doesn't transmit any information.

However, when the socket eventually drops after this period of inactivity, it reconnects and starts functioning properly again.

that issue is slightly different.

Are you connecting to Appwrite Cloud?

self-hosted appwrite: 1.5.3 sdk-for-web: 14.0.0

I've seem some issues like this one recently but in cloud. Not sure if both are related or have the same root cause

Do i need it convert it an GH issue ?

I also experience this thing in flutter and connecting to appwrite cloud

that is why in my case that every screen that has fetching items, I have always refresh icon button here so it is treat as the alternative way to refresh the realtime connection.

your problem is probably different

do you have anything in front of Appwrite? Like Cloudflare? or a reverse proxy?

Thanks @xue we have resolved that. I appreciate you reporting this 🙂

sorry i didn’t want to share here 😅 it was my fault, unrelated and deleted, you got the point so no problem 😅

while im reporting this issue and recording this video, i didn’t have anything in front of appwrite. i was using realtime socket directly, now i have Cloudflare but its the same.

cloudflare would definitely cause problems. cloudflare kills idle websocket connections after a minute

so with cloudflare disabled. what do the realtime container logs show?

I too I'm having this issue in flutter SDK, sometimes the realtime does not update.

There is no any cloudfare relating to my project

We made several tests and the result ends up being the same with or without cloudflare. In fact from what we have seen cloudflare killing the connection reduced the issue 😅

actually Cloudflare fixed it unwillingly in web app because its killing the socket after a minute then browser can reconnect it 😄 however whenever socket starts idling and not disconnected, this is our main issue 🙂 if something kills the socket when it starts for idling, gonna be a solution because im sure that it will be reconnected it again.

Hmm. What's in the realtime docker logs?

And what kind of load do you have?

And how long has the realtime container been running?

What about users that are not behind any cloudfare that are still experiencing this issue?

Are you experiencing it?

Yes, I am