`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:
Rerunning with --debug returns nothing relevant I think:
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?Supabase CLI | Supabase Docs
The Supabase CLI provides tools to develop your project locally, deploy to the Supabase Platform, and set up CI/CD workflows.
6 Replies
You can disable the other services by turning them off in the
config.toml, they should be an enabled setting under most of them. Or you can use the -x flag when doing supabase start to exclude services.@silentworks Thanks, yeah I have disabled most of them in the
config.toml, but they still seem to be running inside the docker container.
I just tried to run supabase start and now it works?! 😄 Tried it for more than an hour haha.What version of the CLI are you using?
Used an older version, and upgraded to the latest one in the process
So currently using 2.39.2
Yeah It's always ideal to update to the latest version. I will also suggest it's better to use
npx than brew. With npx, you can pin a version in your package.json using npm install -D supabase, this way if you should upgrade and something is broken you can easily rollback to a previous version. Whereas with brew it's a bit harder to go back to previous versions.Yeah, makes sense, thanks for pointing out!
Happened again today while I was trying to
supabase db reset . (made a few local changes that I want to reset/undo since it was for testing only)
So maybe my migration files aren't quite right or something
But supabase start still works and seems like my changes are un-done in the local studio