RealtimeClient.js:153 WebSocket connection to 'ws://localhost:54321/realtime/v1/websocket?apikey=xx
Hi, I have upgraded to 2.33.9 and im running this locally - this is an important distinction because when I push to vercel and connect to supabase.com, we dont have this issue.
Where Im running a real time connection on a page I get repetitive errors in my browser console (Ive checked 3 browsers and incognito) and I keep getting RealtimeClient.js:153 WebSocket connection to 'ws://localhost:54321/realtime/v1/websocket?apikey=xx. Supabase has been started and is running without issues. Any idea what is causing this please, I can ping curl -I "http://localhost:54321/realtime/v1/api/ping" and it returns a 200. I didnt have this problem before. I have this policy set in my realtime settings for select:
alter policy "Users can receive memorial broadcasts"
on "realtime"."messages"
to anon, authenticated
using (
true
);
I also see this but dont see exactly the same issue: https://github.com/orgs/supabase/discussions/29260
Where Im running a real time connection on a page I get repetitive errors in my browser console (Ive checked 3 browsers and incognito) and I keep getting RealtimeClient.js:153 WebSocket connection to 'ws://localhost:54321/realtime/v1/websocket?apikey=xx. Supabase has been started and is running without issues. Any idea what is causing this please, I can ping curl -I "http://localhost:54321/realtime/v1/api/ping" and it returns a 200. I didnt have this problem before. I have this policy set in my realtime settings for select:
alter policy "Users can receive memorial broadcasts"
on "realtime"."messages"
to anon, authenticated
using (
true
);
I also see this but dont see exactly the same issue: https://github.com/orgs/supabase/discussions/29260
GitHub
Timestamp Latest Update 17th June 2025 Early access to new API keys launched, available on all projects. Please give them a try and raise any issues in this discussion for the team to fix or addres...
