SupabaseS
Supabase•11mo ago
Yotta

Realtime self-hosted signature_error

Installed Supabase via docker. Expecting everything to work out of the box and everything does except Realtime. When I expect the logs I get signature_error. When I try to inspect something from Realtime > Inspector - it returns me a gain an error "Failed to connect to the channel transactions: This may be due to restrictive RLS policies. Check your role and try again." I disabled the RLS for the table and allowed it Realtime messages. Debugging the logs of the realtime container I get...
14:32:31.923 request_id=GCC5Qp1LoXrkPHYAACnh [info] HEAD /api/tenants/realtime-dev/health
14:32:31.923 request_id=GCC5Qp1LoXrkPHYAACnh [info] Sent 403 in 964µs
14:32:37.019 request_id=GCC5Q80Va_vy8RgAACnx [info] HEAD /api/tenants/realtime-dev/health
14:32:37.020 request_id=GCC5Q80Va_vy8RgAACnx [info] Sent 403 in 755µs
14:32:37.885 project=realtime-dev external_id=realtime-dev [error] ErrorConnectingToWebsocket: {:error, :signature_error}

AI tools even worsened it as bugged the database config file. Do you have any idea why this could happen?
Was this page helpful?