Realtime isn't working on local Supabase

[rohanrhu]

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

Realtime is completely broken on local Supabase.

It was only about supabase-swift module but now (in Supabase 2.20.5) it is erroring on Supabase Studio app too.

Please make sure that realtime Postgres changes is working with supabase-swift on local Supabase instance.

Screenshots

System information

• Supabase: v2.20.5
• supabase-swift: v2.26.0

[ning-bao]

Same issue here... The container never starts😥

[rohanrhu]

Supabase team, please take care of this. This is a major issue.

[Hallidayo]

Hi, I've moved this over to the realtime repo.

[rohanrhu]

Any news on this? We will publish our app soon but we need Supabase's realtime feature that it is claiming it has.

[ning-bao]

Reinstalled Supabase it seems to be working now. Just need to migrate.

…

________________________________ From: Oğuzhan Eroğlu ***@***.***> Sent: Friday, April 4, 2025 2:51:16 AM To: supabase/realtime ***@***.***> Cc: Ning Bao ***@***.***>; Comment ***@***.***> Subject: Re: [supabase/realtime] Realtime isn't working on local Supabase (Issue #1336) Any news on this? We will publish our app soon but we need Supabase's realtime feature that it is claiming it has. — Reply to this email directly, view it on GitHub<#1336 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO2Q6AWRRNUK6HFHKFMWU2D2XVKHJAVCNFSM6AAAAAB2FFWOUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZWGI2DSMRSHE>. You are receiving this because you commented.Message ID: ***@***.***> [rohanrhu]rohanrhu left a comment (supabase/realtime#1336)<#1336 (comment)> Any news on this? We will publish our app soon but we need Supabase's realtime feature that it is claiming it has. — Reply to this email directly, view it on GitHub<#1336 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO2Q6AWRRNUK6HFHKFMWU2D2XVKHJAVCNFSM6AAAAAB2FFWOUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZWGI2DSMRSHE>. You are receiving this because you commented.Message ID: ***@***.***>

[rohanrhu]

Reinstalled Supabase it seems to be working now. Just need to migrate.
…

Hi @ning-bao what are your Supabase and supabase-swift versions?

[filipecabaco]

Sorry for the lack of replies, just a quick FYI that I will be tackling this today

[rohanrhu]

It is still not working with all the latest versions of Supabase and supabase-swift.

I'm seeing this on logs:

{
  "event_message": "15:29:17.380 project=realtime-dev external_id=realtime-dev error_code=ErrorConnectingToWebsocket [error] ErrorConnectingToWebsocket: {:error, :signature_error}",
  "id": "7ced2198-0c9e-48d6-8d79-4f84f5a30b57",
  "metadata": [
    {
      "external_id": "default",
      "project": "default"
    }
  ],
  "timestamp": 1744471757380835
}

[GustavoMartins123]

It is still not working with all the latest versions of Supabase and supabase-swift.

I'm seeing this on logs:

{
  "event_message": "15:29:17.380 project=realtime-dev external_id=realtime-dev error_code=ErrorConnectingToWebsocket [error] ErrorConnectingToWebsocket: {:error, :signature_error}",
  "id": "7ced2198-0c9e-48d6-8d79-4f84f5a30b57",
  "metadata": [
    {
      "external_id": "default",
      "project": "default"
    }
  ],
  "timestamp": 1744471757380835
}

Probably because the jwt secret of the token you are sending is different from the jwt signature that the service is expecting. One point, if you updated the jwt secret, change the jwt secret in the tenant as well, it is in _realtime.extensions, there is the Jwt secret in the data, update it.

[rohanrhu]

It is still not working with all the latest versions of Supabase and supabase-swift.
I'm seeing this on logs:
{
"event_message": "15:29:17.380 project=realtime-dev external_id=realtime-dev error_code=ErrorConnectingToWebsocket [error] ErrorConnectingToWebsocket: {:error, :signature_error}",
"id": "7ced2198-0c9e-48d6-8d79-4f84f5a30b57",
"metadata": [
{
"external_id": "default",
"project": "default"
}
],
"timestamp": 1744471757380835
}

Probably because the jwt secret of the token you are sending is different from the jwt signature that the service is expecting. One point, if you updated the jwt secret, change the jwt secret in the tenant as well, it is in _realtime.extensions, there is the Jwt secret in the data, update it.

I didn't do anything like that since the last time it was working. Postgres server doesn't allow postgres to change update on the _realtime.tenants row.

I tried rebuilding my local Supabase on Docker many times but it is not working.