Middleware server error accessing Supabase variables

Still getting the error, I can see the variables now but they are not accessible to the code got this message from the chat.“runtime environment still isn’t providing the variables to the middleware”

instead of app loading i get the following error

@supabase/ssr: Your project’s URL and API key are required to create a Supabase client! Check your Supabase project’s API settings to find these values API Settings | Supabase at ge (@supabase/ssr) at createClient (/lib/supabase/client) at updateSession (/lib/supabase/middleware) at async Object.middleware [as handler] (/middleware)

1 Like

My app still doesnt work, get the same message:

Runtime Error

either NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY env variables or supabaseUrl and supabaseKey are required! at E (@supabase/auth-helpers-nextjs) at Object.middleware [as handler] (/middleware)

1 Like

any updates? we have few production items that we need to fix, not able to do anything at the moment.

1 Like

Mine is now working. All the env variables showed back up, but this was just created today and v0 linked the supabase instance for me initially, so not sure if others have a different setup.

2 Likes

mine is not working, still getting the error.

Runtime Error

@supabase/ssr: Your project’s URL and API key are required to create a Supabase client! Check your Supabase project’s API settings to find these values API Settings | Supabase at ge (@supabase/ssr) at createClient (/lib/supabase/client) at updateSession (/lib/supabase/middleware) at async Object.middleware [as handler] (/middleware)

1 Like

I’m still seeing this

1 Like

Middleware server error accessing Supabase variables on Home page. Confirming env variables exist, but v0 preview can’t find or access them. Was not an issue 24 hours ago.

1 Like

same issue here

Your project’s URL and Key are required to create a Supabase client! Check your Supabase project’s API settings to find these values

1 Like

Any updates on this? V0 is unusable with Supabase currently

1 Like

Still facing the same issue on all my projects, need a resolution.

Runtime Error

Your project’s URL and Key are required to create a Supabase client! Check your Supabase project’s API settings to find these values API Settings | Supabase at Ce (@supabase/ssr) at updateSession (/lib/supabase/middleware) at Object.middleware [as handler] (/middleware)

1 Like

Still getting the issue in mine

I am also getting these errors on one of my projects!

Still getting the error on one of my projects

[v0] Supabase credentials not available in middleware, skipping auth check

13:52:06.294Z**[SERVER]**

[v0] Supabase credentials not available in middleware, skipping auth check

13:52:06.425Z**[SERVER]**

[v0] Supabase credentials not available, returning null client

13:52:06.425Z**[SERVER]**

[v0] Supabase credentials not available, returning null client

13:52:06.426Z**[SERVER]**

[v0] Supabase client not available in getPerformanceMetrics

13:52:06.426Z**[SERVER]**

[v0] Supabase credentials not available, returning null client

13:52:06.426Z**[SERVER]**

[v0] Supabase client not available in getTopPicks

13:52:13.453Z**[SERVER]**

GoTrueClient@sb-jxswntpuuznxeqhlqdsx-auth-token:1 (2.84.0) 2025-11-23T18:52:13.453Z Multiple GoTrueClient instances detected in the same browser context. It is not an error, but this should be avoided as it may produce undefined behavior when used concurrently under the same storage key.

13:52:13.471Z**[SERVER]**

GoTrueClient@sb-jxswntpuuznxeqhlqdsx-auth-token:2 (2.84.0) 2025-11-23T18:52:13.471Z Multiple GoTrueClient instances detected in the same browser context. It is not an error, but this should be avoided as it may produce undefined behavior when used concurrently under the same storage key.

I cannot get V0 to fix this error in any capacity…

Received an email from Vercel that issue has been resolved. I rechecked and the issue is still there, has not yet been resolved when v0 preview loads/initialises.

1 Like

same issue with here can’t fix it.

Same issue here and they seem to be unresponsive this is costing me a great deal of time lost.

@pawlean Please address this issue, i am getting same error and all my vars show up and I am able to update and edit them. The error still occurs after duplicating readding vars etc please assist!

Still getting issues in my apps, no idea what is going on with all of this:

fetch to https://xxxxxxxxxxxxxxxx.supabase.co/rest/v1/contact_history?select=*&interaction_type=eq.call failed with status 556 and body:

This will be 3 working days where V0 + Supabase has completely failed me and at this stage I struggle to work out who is broken

Hey, everyone! Just catching up after the weekend.

Let me share this with the v0 team - appreciate your patience :slight_smile:


Update: I just moved this from the original thread as this is a separate issue.

Can you folks confirm a new chat shows the same error?

Any chat links would be helpful!

1 Like