Realtime Not Working

[ConProgramming]

The default realtime deployment isn't working. All other services are working fine, except realtime where I'm getting errors like the following:

Do I have to do any extra configuration for realtime? Would love to have a fix here asap.

[ConProgramming]

It seems it's trying but failing to connect to itself? The unable to connect to is its own IP.

[ethanstan]

Also having issues with this

[ConProgramming]

My database doesn't have a _realtime schema, only a realtime schema, and it has this. Nowhere in my database is tables for broadcasts / channels / presences / subscription, like how supabase.com has.

[dubscode]

I am dealing with this too. In the tenants table I found that my tenant was called realtime-dev-tenant, and the code was looking for realtime-dev

I updated this code in supabase-stack

And now I am getting a signature error in the logs, so maybe a step in the right direction:

Still debugging but thought I'd share in case it helps someone sort this out. Thanks

[ConProgramming]

I am dealing with this too. In the tenants table I found that my tenant was called realtime-dev-tenant, and the code was looking for realtime-dev

I updated this code in supabase-stack

And now I am getting a signature error in the logs, so maybe a step in the right direction:

Still debugging but thought I'd share in case it helps someone sort this out. Thanks

If you clear out the requirements schema, then update the version of realtime in the stack to the latest image: ecs.ContainerImage.fromRegistry('public.ecr.aws/supabase/realtime:v2.28.34'), and redeploy, it'll correctly insert as realtime-dev instead of realtime-dev-tenant

[ConProgramming]

Hey @mats16 would love some help here 🙏❤️

[ConProgramming]

Update: The self host docker seems to have the same problem by default. Weirdly, the cli docker works fine. Looking into this.

[ConProgramming]

Now, the websocket for realtime fails with a 426 response. For example, using websocat

websocat "ws://MYPUBLICIP/realtime/v1/websocket?apikey=XYZ&vsn=1.0.0" 
websocat: WebSocketError: WebSocketError: Received unexpected status code (426 Upgrade Required)
websocat: error running

And kong logs at the same time

"GET /realtime/v1/websocket?apikey=XYZ&vsn=1.0.0 HTTP/1.0" 426 0 "-" "-" kong_request_id: "XYZ"

Using websocat on a project on supabase.com, it connects correctly.

[ConProgramming]

Am also now getting these logs in my realtime

@dubscode How goes over there? Did healthcheck improve your issue?

[dubscode]

Hi @ConProgramming I paused trying to troubleshoot on this repo and started to take a stab at setting this up using SST. I use SST a lot and have setup RDS quite a few times using it and CDK, but have not utilized the Service construct before for container images, so learning as I go, but pretty confident it can work out. I have an extremely "Work in Progress" shell setup here if you wanted: https://github.com/dubscode/supabase-sst Feel free to use it if you want. I'll contribute on it as I can

[ConProgramming]

Now, the websocket for realtime fails with a 426 response. For example, using websocat

websocat "ws://MYPUBLICIP/realtime/v1/websocket?apikey=XYZ&vsn=1.0.0" 
websocat: WebSocketError: WebSocketError: Received unexpected status code (426 Upgrade Required)
websocat: error running

And kong logs at the same time

"GET /realtime/v1/websocket?apikey=XYZ&vsn=1.0.0 HTTP/1.0" 426 0 "-" "-" kong_request_id: "XYZ"

Using websocat on a project on supabase.com, it connects correctly.

This 426 was from a Nginx bastion in front of Kong blocking websocket headers. Wish realtime would've had better logs for this, but after I fixed Nginx this is up and running. Now it's just a matter of merging #95

[deadki0001]

@ConProgramming Hope you doing well mate, was there any official resolution to this? I tried to follow the JSON for the health check on another issue you posed in but it seems like the issue still persists? been battling it for a full day now.