Realtime DB subscription doesn't work with new Custom Domain URL

[0xPT]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

After adding custom domain and utilizing it in my project, realtime no longer works with a 403 unauthorized error. WebSocket connection to 'MY_CUSTOM_DOMAIN_URL' failed: Error during WebSocket handshake: Unexpected response code: 403

To Reproduce

1. Setup project using default Supabase domain
2. Set tables to realtime
3. Upgrade to custom domain according to docs
4. Set new table to realtime
5. None of the tables connect properly

Expected behavior

Realtime to continue working. If I use the old domain in createClient(), the old domain still works with realtime.

System information

• OS: macOS
• Browser: Chrome
• Version of supabase-js: ^2.32.0
• Version of Node.js: 16.14.0

Additional context

Like I said, if I use the default Supabase domain it continues to work, but as soon as I change the URL to the new Supabase domain (which works for Auth and other services), realtime doesn't work.

[0xPT]

@saltcod Not sure if this would be a supabase-js problem... If the webhook infra for real-time is not configured properly with custom domains it's not a supabase-js issue right? Still facing this issue and having to run two Supabase clients to get it to work

[lopezjurip]

any solution to this?

[w3b6x9]

@0xPT @lopezjurip i can confirm that establishing a Realtime subscription using custom domain works for me. Can you submit a support ticket at https://supabase.help and I'll take a closer look at your project?

[Aadilhassan]

I am also facing the same issue