search

supabase / cli

Supabase CLI. Manage postgres migrations, run Supabase locally, deploy edge functions. Postgres backups. Generating types from your database schema.
https://supabase.com/docs/reference/cli/about
MIT License
1.09k stars 212 forks source link

Error Running Supabase Locally: Client.Timeout Exceeded While Awaiting Headers for /storage/v1/bucket #2540

Open ensticks opened 4 months ago

ensticks commented 4 months ago

Describe the bug When running Supabase locally, I encounter the following error:

failed to execute http request: Get "http://127.0.0.1:54321/storage/v1/bucket": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

To Reproduce Steps to reproduce the behavior:

  1. Run supabase start

Expected behavior Local Supabase should start correctly without errors.

Screenshots N/A

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

        SERVICE IMAGE      │      LOCAL       │ LINKED
  ─────────────────────────┼──────────────────┼─────────
    supabase/postgres      │ 15.1.1.61        │ -
    supabase/gotrue        │ v2.151.0         │ -
    postgrest/postgrest    │ v12.2.0          │ -
    supabase/realtime      │ v2.29.15         │ -
    supabase/storage-api   │ v1.0.6           │ -
    supabase/edge-runtime  │ v1.54.10         │ -
    supabase/studio        │ 20240701-05dfbec │ -
    supabase/postgres-meta │ v0.83.2          │ -
    supabase/logflare      │ 1.4.0            │ -
    supabase/supavisor     │ 1.1.56           │ -
    darthsim/imgproxy      │ v3.8.0           │ -

Additional context N/A

shawnmclean commented 4 months ago

Whats the command you use to start the services? Or to get supavisor running?

ensticks commented 4 months ago

Whats the command you use to start the services? Or to get supavisor running?

supabase start
sweatybridge commented 3 months ago

This is a strange error. May be you can try to isolate the issue by excluding the storage container from starting. 

supabase start -x storage
petercsiba commented 3 months ago

I am experiencing a similar issue on MacOS with CLI version 1.190.0, trying what @sweatybridge is suggesting npx supabase start -x storage resulted in the same behavior as OP (and same as without -x storage)

npx supabase start -x storage
WARNING: You are running different service versions locally than your linked project:
supabase/storage-api:v1.10.1 => v1.10.3
Run supabase link to update them.
Seeding globals from roles.sql...
Applying migration 20230718010725_ ... (truncated)
Seeding data from seed.sql...
WARNING: analytics requires mounting default docker socket: /var/run/docker.sock
Stopping containers...
failed to execute http request: Get "http://127.0.0.1:54321/storage/v1/bucket": net/http: HTTP/1.x transport connection broken: malformed HTTP response "{\"type\":\"Tier1\",\"version\":\"1.0\"}"

Linking my issue for possible duplicate https://github.com/supabase/supabase/issues/28830