WebSocket connection to failed problem?
Hi,
I’m encountering a strange issue with Supabase Realtime. Everything was working just fine — the WebSocket connection was successful just a few minutes ago. But suddenly, without changing any code, the connection started failing with the following error:
This also happened yesterday — the connection was completely down for the whole day, and then it started working again without any changes on my side.
Could anyone help me understand what might be going wrong, or if there are any recent changes on the Supabase backend?
Thanks!
2 Replies
There was a change in supabase-js 2.50.1 that broke realtime sockets in chrome. 2.50.2 was just released to fix that.
My realtime is working.
// import { createClient } from 'https://cdn.jsdelivr.net/npm/@supabase/supabase-js@2/+esm';
import { createClient } from 'https://cdn.jsdelivr.net/npm/@supabase/supabase-js@2.50.2/+esm' Thank you so much! 🥺 Your message helped me identify the exact issue — I was indeed using version 2 and updating to 2.50.2 immediately fixed the problem in Chrome. I really appreciate your quick and clear response. You saved me a lot of debugging time! 😆
import { createClient } from 'https://cdn.jsdelivr.net/npm/@supabase/supabase-js@2.50.2/+esm' Thank you so much! 🥺 Your message helped me identify the exact issue — I was indeed using version 2 and updating to 2.50.2 immediately fixed the problem in Chrome. I really appreciate your quick and clear response. You saved me a lot of debugging time! 😆