Vovy fixes the Site URL and Redirect URLs in Supabase so confirmation, reset and OAuth links land on your live app, including Vercel previews.
My login links go to localhost:3000 in production, fix it
How it works
- Find where the redirect comes from: Vovy reads your code in Cursor for emailRedirectTo and redirectTo values and checks whether they're hardcoded to localhost.
- Set the Site URL: It opens Authentication, URL Configuration in Supabase and changes Site URL, the default place auth links send people, to your live domain.
- Add allowed Redirect URLs: Vovy adds your production URL, localhost for development, and a wildcard for Vercel preview links so every environment is allowed.
- Make the code use the current domain: In Cursor it replaces hardcoded localhost with window.location.origin or an environment variable, so each deploy points to itself.
- Test on production: Vovy triggers a password reset on your live site and confirms the email link opens your real domain, then shows a before and after card.
What you provide
- Your live domain
- Access to your Supabase project
What you get
- Auth links that open your real site
- Redirect URLs for production, local and previews
- No more hardcoded localhost
- A before and after card
FAQ
Will changing the Site URL break local development?
No, as long as localhost stays in the Redirect URLs list and your code passes the right redirectTo.
Why did old emails still go to localhost?
Links already sent keep the address they were created with. Only new emails use the fixed settings.
What is a wildcard redirect URL?
A pattern with * or ** that matches many addresses, like every Vercel preview URL for your project. Use it for previews, and exact URLs for production.
Related tasks
All tasks