[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # Middleware server error accessing Supabase variables 399 views · 19 likes · 28 posts Jerry 2306 (@jerry-2306) · 2025-11-21 · ♥ 1 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 https://supabase.com/dashboard/project/\_/settings/api at ge (@supabase/ssr) at createClient (/lib/supabase/client) at updateSession (/lib/supabase/middleware) at async Object.middleware \[as handler\] (/middleware) Alex 3807 (@alex-3807) · 2025-11-21 · ♥ 1 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) Jerry 2306 (@jerry-2306) · 2025-11-21 · ♥ 1 any updates? we have few production items that we need to fix, not able to do anything at the moment. rothnic (@rothnic) · 2025-11-21 · ♥ 2 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. Jerry 2306 (@jerry-2306) · 2025-11-21 · ♥ 1 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 https://supabase.com/dashboard/project/\_/settings/api at ge (@supabase/ssr) at createClient (/lib/supabase/client) at updateSession (/lib/supabase/middleware) at async Object.middleware \[as handler\] (/middleware) Jwalsh (@jwalsh-bdt) · 2025-11-21 · ♥ 1 I’m still seeing this T72428 (@vet-6321) · 2025-11-22 · ♥ 1 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.  Sasha (@chuponsito) · 2025-11-22 · ♥ 1 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 Jwalsh (@jwalsh-bdt) · 2025-11-22 · ♥ 1 Any updates on this? V0 is unusable with Supabase currently Jerry 2306 (@jerry-2306) · 2025-11-22 · ♥ 1 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 https://supabase.com/dashboard/project/\_/settings/api at Ce (@supabase/ssr) at updateSession (/lib/supabase/middleware) at Object.middleware \[as handler\] (/middleware) Alex 3807 (@alex-3807) · 2025-11-22 Still getting the issue in mine  Eric Torres (@corebytes) · 2025-11-23 I am also getting these errors on one of my projects!  Eric Torres (@corebytes) · 2025-11-23 Still getting the error on one of my projects  Thesimplesidenews 3702 (@thesimplesidenews-37) · 2025-11-23 \[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… T72428 (@vet-6321) · 2025-11-23 · ♥ 1 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. Hamedia (@ryanb-hamedia) · 2025-11-24 same issue with here can’t fix it. Eric Torres (@corebytes) · 2025-11-24 Same issue here and they seem to be unresponsive this is costing me a great deal of time lost. Eric Torres (@corebytes) · 2025-11-24 @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! AH7128 (@alexhandsaker-7128) · 2025-11-24 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 Pauline P. Narvas (@pawlean) · 2025-11-24 · ♥ 1 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! Pauline P. Narvas (@pawlean) · 2025-11-24 · ♥ 3 Update: we just shipped a fix. Let me know if you have any issues! T72428 (@vet-6321) · 2025-11-24 · ♥ 1 @pawlean confirming i no longer have the issue - the fix worked - thank you Eric Torres (@corebytes) · 2025-11-25 · ♥ 1 Thank you so much for the help, feels great to be able to count on you! Pauline P. Narvas (@pawlean) · 2025-11-25 What we are here for :saluting_face: Jerry 2306 (@jerry-2306) · 2025-11-25 · ♥ 1 Fix confirmed. Thank you Kim Rydstrand (@kimrydstrand) · 2025-11-26 @pawlean I get an ‘unexpected error occurred’ whenever I try to add integrations like supabase or add variables. Pauline P. Narvas (@pawlean) · 2025-11-27 Are you still seeing this, Kim? I recommend creating a new post in #v0. Kim Rydstrand (@kimrydstrand) · 2025-11-30 Thanks Pauline, a new chat wasnt enough but moving a chat to a new project worked.
