Error Status 502 when running supabase start #2893
Comments
|
Hey there ! Thanks for reporting. Did you tried cleaning up your local volumes and made sure all containers were down with Could you try to run things with the |
|
Same here, it prompts for a warning about analytics requiring TCP enabled. It is the same setup as OP and I also enabled the 2 checkboxes as highlighted in the supabase docker setup. The vector container is the one that is the problem, The cause of the error was updating the CLI, I wanted the newer update of the docker images so updated the CLI alongside those. Here's the log from attempting to run |
|
starting with Log attached below, did not use --debug as the output was way too garbled up |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Following an update to the CLI, I am no longer able to start supabase services via the cli.
I am using Ubuntu 22.04 via Windows 11 WSL. I initially installed supabase via dpkg with the instructions here. Following this, I ran supabase init, start, etc. as expected without issues. After using supbase cli for a period of time, I was prompted to update the cli. To make this easier, I decided to uninstall the cli installed via source and re-install via npm. Following this, I am now unable to run
supabase startwithout encounteringError status 502:.The final lines of the error trace are below:
As part of efforts to resolve the issue I have attempted the following without success:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect my supabase local instance to be available through localhost.
Screenshots
N/A
System information
Rerun the failing command with
--create-ticketflag.Additional context
If applicable, add any other context about the problem here.
The text was updated successfully, but these errors were encountered: