Error status 502: An invalid response was received from the upstream server
I get this error when running npx supabase db reset after my supabase instance has been started.
I recently updated to the newest CLI version 2.62.10 and have been running into issues when running : npx supabase db reset command at this step:
Restarting containers...
Error status 502: An invalid response was received from the upstream server
The logs from the supabase local dashboard show:
event message:
"2025/11/27 02:31:53 [error] 1114#0: *313 connect() failed (111: Connection refused) while connecting to upstream, client: 184.150.49.33, server: kong, request: "GET /storage/v1/bucket HTTP/1.1", upstream: "http://172.18.0.10:5000/bucket\", host: "127.0.0.1:54321""
metadata:
[
{
"request": [
{
"headers": [
{
"cf_connecting_ip": "184.150.49.33"
}
],
"host": "127.0.0.1:54321",
"method": "GET",
"path": "/storage/v1/bucket",
"protocol": "HTTP/1.1"
}
],
"response": [
{
"status_code": 200
}
]
}
]
I'm running the cli via my project, it is installed as a dev dependency. I have been getting various issues ever since I upgraded from the older version (I think it was 2.45.5 which worked very well) and now since upgrading to 2.62.10 I have this error.
1 Reply
I think the problem lies with certain containers (storage )
SUPABASE_DB_ONLY=true npx supabase db reset works for me because it doesn't reset the failing containers.