Realtime Subscriptions Timeout in Docker
I am new to supabase realtime connection. Recently I had hit a rly strange issue.
TL;DR:
NestJS backend apps use realtime for simple broadcasting (no database changes). When I ran and tested locally on my Mac, it works flawlessly. Same code inside Docker , getting subscription timeout errors. I tried with two of my colleagues , one is working and another one is having the same issue as Docker.
I tried
ping supabase wss (anonKey) inside docker using wscat - Success
both supabase db url and service role key are working
timezone is also correct
using realtime backend to supabase and frontend to supabase using custom channel ID
Has anyone encountered this kind of issue ? Is there a known issue ?
any advice would be hugely appreciated.
Environment Details
* Framework: NestJS
* Platform: Server-side Node.js application
* Host OS: macOS
* Docker Environment: Node.js on Linux (Alpine base image)
* Library Versions: Using @supabase/supabase-js, which depends on @supabase/realtime-js@2.15.4 (confirmed from logs).
TL;DR:
NestJS backend apps use realtime for simple broadcasting (no database changes). When I ran and tested locally on my Mac, it works flawlessly. Same code inside Docker , getting subscription timeout errors. I tried with two of my colleagues , one is working and another one is having the same issue as Docker.
I tried
ping supabase wss (anonKey) inside docker using wscat - Success
both supabase db url and service role key are working
timezone is also correct
using realtime backend to supabase and frontend to supabase using custom channel ID
Has anyone encountered this kind of issue ? Is there a known issue ?
any advice would be hugely appreciated.
Environment Details
* Framework: NestJS
* Platform: Server-side Node.js application
* Host OS: macOS
* Docker Environment: Node.js on Linux (Alpine base image)
* Library Versions: Using @supabase/supabase-js, which depends on @supabase/realtime-js@2.15.4 (confirmed from logs).
