"API Gateway" and "Postgres" infrastructure links in logs explorer are broken for self-hosted GA image(1.24.04 and newer) about supabase

[boozedog]

Oddly enough, this is happening to me using the 20240422-5cf8f30 Studio image

[0reo]

Oddly enough, this is happening to me using the 20240422-5cf8f30 Studio image

Interesting. Are you referring to the 502 error, or the timestamp error specifically?

Here are all the containers I'm using

supabase/realtime:v2.28.32
supabase/logflare:1.4.0
supabase/gotrue:v2.151.0
supabase/postgres:15.1.1.41
supabase/edge-runtime:v1.45.2
darthsim/imgproxy:v3.13
kong:2.8.1
supabase/postgres-meta:v0.80.0
postgrest/postgrest:v12.0.1
supabase/storage-api:v1.0.6
supabase/studio:20240422-5cf8f30
timberio/vector:0.28.1-alpine
lscr.io/linuxserver/swag:2.2.0

I was working on updating the DigitalOcean self-hosted repo, so 2 of my containers differ compared to what's in this repo

• image proxy is slightly newer(doubt that would cause the issue, but could always be wrong)
• using swag in front of kong, you shouldn't need this though if you're following the official supported guide here https://supabase.com/docs/guides/self-hosting/docker

There are also some other slight variations in configurations and health check addresses. So if using the above containers still fail, feel free to check out my repo and see if you get some better results.

https://github.com/0reo/supabase-on-do

It's a bit more involved the then officially supported one though. Instructions are in the readme or https://docs.digitalocean.com/developer-center/hosting-supabase-on-digitalocean/