Guide
Sign-up or login broken after publishing: users bounce back to login or land on localhost
Updated
Login worked in the preview. On the live site, users sign in and end up back on the login page, on a localhost address, or on an error. Or the confirmation link opens the wrong site.
Why it happens
After sign-in, your login service (often Supabase) sends people back to your app, but only to addresses on an approved list. Your preview address is on that list; your published address often is not.
Possible causes
- The published address is not on the approved redirect list, so the service falls back to its default, which is often localhost.
- The default address (Site URL) was never changed from the local one.
- Google sign-in is on, and the callback address is not listed on the Google side.
- The app's own code has the preview address written into the sign-in code.
You can't see it yourself
You're signed in, your customers aren't. You are already signed in, or signing in from the preview. Sign-up is the one step every new customer must pass, and you never repeat it.
Related: The confirmation link in my sign-up email opens localhost · New users sign up, then land back on the login page or see an error · "Sign in with Google" fails for new people on my live app
VibeFix is independent. Lovable, Bolt, Replit, Base44, v0, Supabase, Firebase, Stripe and Vercel are trademarks of their owners.
Want it fixed?
Our AI agent finds the cause, fixes it in your code and re-checks your live app. $79 for one bug, paid up front. If we can't complete your re-check, you get your money back.
It starts with a free check that confirms the problem on your live app, no account needed.