S

Supabase•4y ago

Tobi

Error RealtimeChannels - occurred when joining realtime table=eq id

I updated to v2 today, changed the syntax of the realtime subscriptions, deactivated RLS policies and now I get the following websocket error if I subscribe to a RealtimeChannel:

event: "phx_reply" payload: response: {reason: "error occurred when joining realtime:public:<table-name>"} reason: "error occurred when joining realtime:public:<table-name>" status: "error" ref: "1" topic: "realtime:public:<table-name>"event: "phx_reply" payload: response: {reason: "error occurred when joining realtime:public:<table-name>"} reason: "error occurred when joining realtime:public:<table-name>" status: "error" ref: "1" topic: "realtime:public:<table-name>"

Any ideas what could cause this? I also found this bug report on github but I do not understand it: https://github.com/supabase/realtime/issues/217

I also created a stackoverflow post:
https://stackoverflow.com/questions/74175531/supabase-realtime-error-occurred-when-joining-realtimepublictable-name

GitHub

error occurred when joining with user token · Issue #217 · supabas...

Bug report Have secure channels turned on with JWT and this has been working fine for some time (sending the JWT in as param apikey). However, following a recent update to the realtime server proje...

Stack Overflow

Supabase realtime "error occurred when joining realtime:public:"

I upgraded from Supabase-Js v1 to v2. After doing so, my previously working realtime subscription all fail and create the following error:
Question
What does this error message mean? Why does the e...