cli icon indicating copy to clipboard operation
cli copied to clipboard
verified publisher icon supabase

Supabase not starting anymore

Open tech-travelers opened this issue 3 months ago • 5 comments

Describe the bug I cannot start supabase anymore, even when running a new project, it always used to work it suddenly stopped working and I cannot think of any reason why.

To Reproduce Steps to reproduce the behavior:

  1. Run supabase init in a clean project
  2. Run supabase start --debug --create-ticket
  3. I get the following error
open supabase/.temp/profile: no such file or directory
Supabase CLI 2.53.6
Using profile: supabase (supabase.co)
Loading project ref from file: supabase/.temp/project-ref
Starting database...
2025/10/23 12:02:29 PG Send: {"Type":"StartupMessage","ProtocolVersion":196608,"Parameters":{"database":"postgres","user":"postgres"}}
2025/10/23 12:02:29 PG Recv: {"Type":"AuthenticationSASL","AuthMechanisms":["SCRAM-SHA-256"]}
2025/10/23 12:02:29 PG Send: {"Type":"SASLInitialResponse","AuthMechanism":"SCRAM-SHA-256","Data":"n,,n=,r=cBF0F5Dkuh9NkFfMidd0Cyef"}
2025/10/23 12:02:29 PG Recv: {"Type":"AuthenticationSASLContinue","Data":"r=cBF0F5Dkuh9NkFfMidd0CyefAbC1Cgu4Tmm5lCAE3Idqd4J/,s=39ygTF0FG3XpqE+5t8m9LA==,i=4096"}
2025/10/23 12:02:29 PG Send: {"Type":"SASLResponse","Data":"c=biws,r=cBF0F5Dkuh9NkFfMidd0CyefAbC1Cgu4Tmm5lCAE3Idqd4J/,p=0DwDcoNhojNexgv7/akWXw8dTOvD5GaOGNI4VTRlJ1U="}
2025/10/23 12:02:29 PG Recv: {"Type":"AuthenticationSASLFinal","Data":"v=lEFkTyWifSW1hHbjPzDrwP7otYmoOvvnaCE/AKqoQKo="}
2025/10/23 12:02:29 PG Recv: {"Type":"AuthenticationOK"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"in_hot_standby","Value":"off"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"integer_datetimes","Value":"on"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"TimeZone","Value":"UTC"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"IntervalStyle","Value":"postgres"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"is_superuser","Value":"off"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"application_name","Value":""}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"default_transaction_read_only","Value":"off"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"scram_iterations","Value":"4096"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"DateStyle","Value":"ISO, MDY"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"standard_conforming_strings","Value":"on"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"session_authorization","Value":"postgres"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"client_encoding","Value":"UTF8"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"server_version","Value":"17.6"}
2025/10/23 12:02:29 PG Recv: {"Type":"ParameterStatus","Name":"server_encoding","Value":"UTF8"}
2025/10/23 12:02:29 PG Recv: {"Type":"BackendKeyData","ProcessID":215,"SecretKey":1554359802}
2025/10/23 12:02:29 PG Recv: {"Type":"ReadyForQuery","TxStatus":"I"}
Initialising schema...
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ [[ -n '' ]]
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 14989ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:

  1. Ensuring your database is available and that you can connect to it
  2. Tracking down slow queries and making sure they are running fast enough
  3. Increasing the pool_size (although this increases resource consumption)
  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval

See DBConnection.start_link/2 for more information

    (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:1098: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.18.4) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:1219: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.13.2) lib/ecto/migrator.ex:779: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.13.2) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.13.2) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.13.2) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
Stopping containers...
2025/10/23 12:02:45 PG Send: {"Type":"Terminate"}
Pruned containers: [d01937791715f42af00371a223ea7d99b710cb554f4d219f08ecde112703e08f]
Pruned volumes: [supabase_db_customer-portal supabase_config_customer-portal]
Pruned network: [supabase_network_customer-portal]
error running container: exit 1
Sent crash report: cb9ea038144a4dfa932f40056fbd7e6a
Quote the crash ID above when filing a bug report: https://github.com/supabase/cli/issues/new/choose

Expected behavior I expect supabase to start without any issues

Screenshots N/A

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

  • Ticket ID: cb9ea038144a4dfa932f40056fbd7e6a
  • Version of OS: Ubuntu 22.04 (WSL 2)
  • Version of CLI: v2.53.6
  • Version of Docker: Docker version 28.5.1, build e180ab8
  • Versions of services:
  • SERVICE IMAGE | LOCAL | LINKED ------------------------|------------------------|-------- supabase/postgres | 17.6.1.024 | - supabase/gotrue | v2.180.0 | - postgrest/postgrest | v13.0.7 | - supabase/realtime | v2.56.0 | - supabase/storage-api | v1.28.1 | - supabase/edge-runtime | v1.69.14 | - supabase/studio | 2025.10.20-sha-5005fc6 | - supabase/postgres-meta | v0.93.0 | - supabase/logflare | 1.22.6 | - supabase/supavisor | 2.7.3 | -

Additional context In this clean project I have no migrations and nothing in the seed.sql, I have plenty of disk space, memory, and CPU and I reinstalled supabase cli and docker without any result.

tech-travelers avatar Oct 23 '25 10:10 tech-travelers

same here

lucasm310 avatar Oct 23 '25 17:10 lucasm310

same here

arend-vanderveen avatar Oct 27 '25 10:10 arend-vanderveen

Could you try starting from scratch?

supabase stop --no-backup
rm -rf supabase/.temp
supabase start

Note this will clear existing data in your local db.

sweatybridge avatar Oct 27 '25 10:10 sweatybridge

I am still seeing the same error:

% supabase start --debug

open supabase/.temp/profile: no such file or directory

Supabase CLI 2.53.6

Using profile: supabase (supabase.co)

Loading project ref from file: supabase/.temp/project-ref

Starting database...

I am also seeing a separate error also when the migrations are applied. I am going to focus on the migration error for now.

On Mon, Oct 27, 2025 at 6:42 AM Han Qiao @.***> wrote:

sweatybridge left a comment (supabase/cli#4351) https://github.com/supabase/cli/issues/4351#issuecomment-3450625321

Could you try starting from scratch?

supabase stop --no-backup rm -rf supabase/.temp supabase start

Note this will clear existing data in your local db.

— Reply to this email directly, view it on GitHub https://github.com/supabase/cli/issues/4351#issuecomment-3450625321, or unsubscribe https://github.com/notifications/unsubscribe-auth/BYGW5FEPF6RTWDOW2MVKWUL3ZXZHTAVCNFSM6AAAAACJ7WDH6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINJQGYZDKMZSGE . You are receiving this because you commented.Message ID: @.***>

arend-vanderveen avatar Oct 27 '25 11:10 arend-vanderveen

Same here

ligazetom avatar Nov 21 '25 22:11 ligazetom

same here

Windows 11 Supabase CLI 2.67.1 (scoop) Docker 29.1.3 (scoop) Docker Engine 29.1.3 (on Arch WSL 2)

anmoti avatar Dec 17 '25 16:12 anmoti