Realtime stops working after db reset

[mfairley]

Describe the bug
After a db reset, clients can no longer subscribe to realtime channels. Stopping and starting supabase again seems to fix the issue.

To Reproduce
Steps to reproduce the behavior:

1. Reset the database
2. Try to connect to a channel

Expected behavior
Realtime should work as usual

System information
Rerun the failing command with --create-ticket flag.

• Version of OS: macOS

• Version of CLI: 2.70.5

• Version of Docker: Docker version 29.1.3, build f52814d

• Versions of services:

  SERVICE IMAGE | LOCAL | LINKED
  ------------------------|------------------------|---------------------------
  supabase/postgres | 17.6.1.054 | 17.6.1.054
  supabase/gotrue | v2.184.0 | v2.184.0
  postgrest/postgrest | v14.2 | postgrest/postgrest:v14.2
  supabase/realtime | v2.69.0 | -
  supabase/storage-api | v1.33.2 | v1.33.0
  supabase/edge-runtime | v1.68.4 | -
  supabase/studio | 2025.12.23-sha-f3af2c3 | -
  supabase/postgres-meta | v0.95.1 | -
  supabase/logflare | 1.27.3 | -
  supabase/supavisor | 2.7.4 | -

[7ttp]

hi @mfairley thanks for reporting! 💚

This is an expected behavior.
Realtime needs a few seconds to reinitialize after reset.
Just wait a moment or run supabase stop && supabase start for immediate response

[mfairley]

I find that the issue remains if it happens and requires a full restart. It may be associated with having sessions currently connected to realtime at the time of reset.