S
Supabase•3h ago
Hacoeur

I am getting Error status 501 when starting my local supabase instance

I am using version "^2.48.3" and when I start my local supabase I get this error which was not there few days ago.
10 Replies
ihm40
ihm40•2h ago
could you copy the error here and maybe anything that looks out of place when you run the -- debug flag
Hacoeur
HacoeurOP•2h ago
Hacoeur
HacoeurOP•2h ago
DEBUG Building vfs with root '/'
DEBUG Sending warning alert CloseNotify
DEBUG Opening cache /root/.cache/deno/node_analysis_cache_v2...
DEBUG edge-runtime is listening on 0.0.0.0:8081
Functions config: {}
Serving functions on http://127.0.0.1:54321/functions/v1/<function-name>
Using supabase-edge-runtime-1.69.12 (compatible with Deno v2.1.4)
Stopping containers...
Pruned containers: [2e93a877059f1050108d23836c43f89fcc91f62602d47327f324ac886d449576 ac9724ef6e7311546aaf868f59af085a7447929bbfa0dcc9ba70cad83541966d b3f496c79e8c1805f2be86abfaa506732f77457ff1918b3ecc1516ef4188490c 86ab691b7334654a302ef374490f0996cad932e36db0faa9694260012d5025f4 09d9227fa7e56d2e81cf740277aa6688347b765e9aff5d3ff80e8d47bcb8bb71 d5f6a4f3e9fb7c78138e23ac8c1f10f75345d49fab37f8b60538893bbeefcf84 d977078968c13a746f050727a6f71c78df6d6d51228b8240ac6f3f4784b24526 a9fb3945f76d6d30aa25cbcae5a47b5e043651e6abde14b1931adef536d63fd7 b4ba2684fc0d40023906a72595aa7b26f8f0f94f814de22b860f1f9f1e914686 cd438ddd68ac6eea4b92e1365253007bde4b09726722c5df9a85ea96f6be67e5]
Pruned network: [supabase_network_mavira-space]
Error status 501: 
Error status 501: 
 ELIFECYCLE  Command failed with exit code 1.
DEBUG Building vfs with root '/'
DEBUG Sending warning alert CloseNotify
DEBUG Opening cache /root/.cache/deno/node_analysis_cache_v2...
DEBUG edge-runtime is listening on 0.0.0.0:8081
Functions config: {}
Serving functions on http://127.0.0.1:54321/functions/v1/<function-name>
Using supabase-edge-runtime-1.69.12 (compatible with Deno v2.1.4)
Stopping containers...
Pruned containers: [2e93a877059f1050108d23836c43f89fcc91f62602d47327f324ac886d449576 ac9724ef6e7311546aaf868f59af085a7447929bbfa0dcc9ba70cad83541966d b3f496c79e8c1805f2be86abfaa506732f77457ff1918b3ecc1516ef4188490c 86ab691b7334654a302ef374490f0996cad932e36db0faa9694260012d5025f4 09d9227fa7e56d2e81cf740277aa6688347b765e9aff5d3ff80e8d47bcb8bb71 d5f6a4f3e9fb7c78138e23ac8c1f10f75345d49fab37f8b60538893bbeefcf84 d977078968c13a746f050727a6f71c78df6d6d51228b8240ac6f3f4784b24526 a9fb3945f76d6d30aa25cbcae5a47b5e043651e6abde14b1931adef536d63fd7 b4ba2684fc0d40023906a72595aa7b26f8f0f94f814de22b860f1f9f1e914686 cd438ddd68ac6eea4b92e1365253007bde4b09726722c5df9a85ea96f6be67e5]
Pruned network: [supabase_network_mavira-space]
Error status 501: 
Error status 501: 
 ELIFECYCLE  Command failed with exit code 1.
This is the end of the error
ihm40
ihm40•2h ago
did this start after you upgraded your supabase or was it working afterwards?
Hacoeur
HacoeurOP•2h ago
So I did not upgrade it when I strated the Supabase it just downloaded the newer version and pulled the the images I have cleaned it up and retried it but it doesnt work
ihm40
ihm40•2h ago
i haven't come across it nowloading a newer version by itself from start. Coul you try following the upgrade guide here https://supabase.com/docs/guides/local-development/cli/getting-started#updating-the-supabase-cli in particular stopping the containers
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.
Hacoeur
HacoeurOP•2h ago
I have already did this guide removed the volumes and upgraded the version but still faced the same error
ihm40
ihm40•2h ago
do you have docker desktop
Hacoeur
HacoeurOP•2h ago
Yess
ihm40
ihm40•1h ago
what do the containers in that look like, does anything look off. Presumable none of them will be started but just wondering if there is something there that shouldn't be okay i stopped all my containers, saw A new version of Supabase CLI is available: v2.48.3 (currently installed v2.47.2) and pressed start again and it seems like it is downloading images which might mean it's doing what you experienced and going to 2.48.3 I'll see if it gives me an error as well so i did the upgrade to 2.48.3 and didn't have any issues

Did you find this page helpful?