My production deployment is using a stale and incorrect value for the NEXT_PUBLIC_SUPABASE_URL environment variable. When a user tries to authenticate, the application attempts to contact the old URL (https://xaemxnvsnnipokhaaaym.supabase.co), which results in a DNS_PROBE_FINISHED_NXDOMAIN error. This makes the core authentication feature of my site unusable in production.
Expected Behavior: The production deployment should use the new, correct Supabase URL that is saved in my Vercel project’s environment variables for the “Production” scope. The authentication flow should start correctly and redirect to my new Supabase project.ehavior →
The issue is related to Vercel’s build environment configuration, not a specific code snippet.
Steps to Reproduce:
A new commit is pushed to the main branch, triggering a Vercel deployment.
The deployment builds and completes successfully.
Visiting the production domain (www.tailrmatch.com) and attempting to sign in triggers the DNS error because the application is using the wrong Supabase URL.n, and steps that reproduce this issue →
Project Name: tailr
Production Domain: www.tailrmatch.com
Framework: Next.js
Environment: Production
GitHub Repo: AnnaBromley0/tailr
Latest Deployment ID with Issue: AximVuj2j
Relevant Settings: The NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY have been correctly updated in the Vercel UI for the Production environment, but the build process is not using these new values.mation (URL, framework, environment, project settings) →