Supabase fails to start get 502 error

[jdgamble555]

Describe the bug A clear and concise description of what the bug is.

To Reproduce

1. Remove all docker images
2. Update supabase locally to 2.26.9
3. See error status 502

Expected behavior

supabase_edge_runtime_language-dev container logs:
Download https://deno.land/std/http/status.ts
                                             Download https://deno.land/std/path/posix/mod.ts
                                                                                             Download https://deno.land/x/[email protected]/index.ts
                                                                                                                                               Error status 502: 

Screenshots If applicable, add screenshots to help explain your problem.

System information Rerun the failing command with --create-ticket flag.

• Ticket ID: b3e66d0b918649dc8eafbe821433e31b
• Version of OS: Windows 11
• Version of CLI: 2.26.9
• Version of Docker: v4.42.1
• Versions of services: [output from supabase services command]

  SERVICE IMAGE          | LOCAL                  | LINKED
 ------------------------|------------------------|------------
  supabase/postgres      | 17.4.1.043             | 17.4.1.043
  supabase/gotrue        | v2.176.1               | v2.176.1
  postgrest/postgrest    | v12.2.3                | v12.2.3
  supabase/realtime      | v2.36.18               | -
  supabase/storage-api   | v1.24.6                | -
  supabase/edge-runtime  | v1.67.4                | -
  supabase/studio        | 2025.06.16-sha-c4316c3 | -
  supabase/postgres-meta | v0.89.3                | -
  supabase/logflare      | 1.14.2                 | -
  supabase/supavisor     | 2.5.2                  | -

This seems to be a problem with edge-runtime. I tried changing versions, but still get same error in older versions.

It does seem to work when I run:

npx supabase start --ignore-health-check

Which I get the same error again:

supabase_edge_runtime_language-dev container logs:
                                                  Download https://deno.land/std/http/status.ts
                                                                                               Download https://deno.land/std/path/posix/mod.ts
                                                                                                                                               Download https://deno.land/x/[email protected]/index.ts
                                                                                                                                                                                                 Stopping containers...
Error status 502: 

Possibly related https://github.com/supabase/cli/issues/2753 https://github.com/supabase/cli/issues/2893

J

[adolfoarangel]

I'm also getting the exact same error. I haven't been to find a work around.

[jdgamble555]

@adolfoarangel - Did you try my workaround above? Also try supabase start --ignore-health-check --exclude edge-runtime.

[cesarwbr]

I’m also encountering this error. Upon reviewing Docker’s log, I found the following:

1114#0: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 172.21.0.1, server: kong, request: “HEAD /functions/v1/_internal/health HTTP/1.1”, upstream: “http://172.21.0.10:8081/_internal/health”, host: “localhost:54321”.

Additionally, this is a portion of the log when I execute supabase start —debug:

2025/06/26 10:57:56 HTTP HEAD: http://127.0.0.1:54321/rest-admin/v1/ready
2025/06/26 10:57:56 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:57:58 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:57:59 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:58:00 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:58:01 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:58:02 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:58:03 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:58:04 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
2025/06/26 10:58:05 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health

Furthermore, the supabase_edge_runtime… doesn’t appear in the Docker Volume.

[caseybaggz]

Same thing for me. A little frustrating since I just got off of the supabase-js v.50 bug 😭

Excluding the health checks do allow me to keep work flowing but I don't love it.

[cesarwbr]

Surprisingly, it’s working right now. I didn’t make any changes. 🤔

[caseybaggz]

Surprisingly, it’s working right now. I didn’t make any changes. 🤔

Same thing happened to me all of the sudden too 🤔 🤔

[ruharuha]

It turned out that Docker wasn't running in my case.