You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably caused by a cookie that is too large. It doesn't occur if you're using a local account. But with SSO I've seen this. Even if you set MAX_HEADER_LENGTH to 8192, the cookie can cause a problem with the ws:// connection.
A temporary fix in this case is to let Kong remove the cookie with a request-transformer.
Issue: WebSocket Connection Failure in Self-Hosted Supabase on EC2
Description
When attempting to connect to Supabase Realtime through a self-hosted instance on EC2, the WebSocket connection fails.
Environment
Steps to Reproduce
Expected Behavior
Additional Context
Questions
The text was updated successfully, but these errors were encountered: