`supabase start` errors with `Invalid Compact JWS`

Hi there!
I upgraded my remote DB from pg 15 -> 17 a while ago.
I noticed that my local supabase CLI DB docker container were still running pg 15. This was causing issues trying to run supabase db dump. So I updated the CLI and re-generated all local containers:

  • Updated [db] major_version = 17 in supabase/config.toml
  • Stopped everything with supabase stop --no-backup
  • Updated supabase cli with brew upgrade supabase
  • Now trying to start with
    supabase start
    first downloaded all new versions of the images, but after that, the command errors with:
(...)
WARN: no files matched pattern: supabase/seed.sql
Starting containers...
Waiting for health checks...
Stopping containers...
Error status 400: {"statusCode":"403","error":"Unauthorized","message":"Invalid Compact JWS"}
Try rerunning the command with --debug to troubleshoot the error.


Rerunning with --debug returns nothing relevant I think:
(...)
WARN: no files matched pattern: supabase/seed.sql
2025/09/03 09:46:55 PG Send: {"Type":"Terminate"}
Starting containers...
Waiting for health checks...
2025/09/03 09:47:06 HTTP GET: http://127.0.0.1:54321/storage/v1/bucket
Stopping containers...
Pruned containers: [fefe4520089f5...(long list of some keys ...)]
Pruned volumes: [supabase_db_MY_PROJECT-web supabase_config_MY_PROJECT-web supabase_storage_MY_PROJECT-web]
Pruned network: [supabase_network_MY_PROJECT-web]
Error status 400: {"statusCode":"403","error":"Unauthorized","message":"Invalid Compact JWS"}


I already deleted everything again with supabase stop --no-backup and ran supabase secrets set JWT_SECRET=$(openssl rand -hex 32) (same for ANON_KEY, SERVICE_ROLE_KEY) and then ran
supabase start
, no luck.

In fact, I only need the local db, and nothing else, no auth etc. But I guess it's not possible to only run the db & studio, right?
The Supabase CLI provides tools to develop your project locally, deploy to the Supabase Platform, and set up CI/CD workflows.
Was this page helpful?