RESCUE · LOVABLE · AUTH
Lovable Supabase auth not working?
When Supabase login in a Lovable app breaks, it is usually configuration, not React code: the Supabase Site URL and Redirect URLs still point at the preview, Google OAuth is missing the Supabase callback URL, confirmation emails use the built-in sender, or a signup trigger fails. Fix the settings first, then the code. VibePitstop fixes Lovable auth with read-only access and a human review on every fix.
Match the symptom
- Sign-in returns to the preview or localhost: set the Site URL to your live domain and add every origin you use (preview and custom domain) to Redirect URLs.
- Google sign-in fails: in Google Cloud, the authorized redirect URI must be your Supabase callback,
https://YOUR-PROJECT.supabase.co/auth/v1/callback, and your domains must be authorized JavaScript origins. See redirect_uri_mismatch. - Confirmation or reset emails never arrive: the built-in sender only reaches your team. See auth emails not sending.
- "Database error saving new user": a trigger that creates a profile row on signup is failing, often a NOT NULL column or a policy. Check the Postgres logs for the exact error.
- Logged in, but every query returns nothing: RLS policies do not match the signed-in role. See data not saving.
A signup trigger that does not break signups
create function public.handle_new_user() returns trigger
language plpgsql security definer set search_path = '' as $$
begin
insert into public.profiles (id, email) values (new.id, new.email);
return new;
end; $$;
create trigger on_auth_user_created after insert on auth.users
for each row execute function public.handle_new_user();
Keep the profile insert minimal; columns the trigger does not fill must be nullable or have defaults.
Want it fixed instead?
Auth & database security fix (Supabase, Firebase): from $400 (one issue); larger scope quoted up to $800 after diagnosis. The $149 diagnosis is credited toward any paid job.
Common worries, answered
- Will you mess up my repo? No. We work from read-only access, and every fix arrives as a pull request. Nothing merges until you merge it.
- Is this just more AI? AI coding agents help prepare fixes. A human reviews every fix before it ships.
- What if it still breaks? We keep working until the written scope is done, at no extra cost. Fixed, or we keep working free until it is (within the written scope).
- What about Stripe and my secret keys? Scoped access only. We never take full keys or owner logins; your secrets stay yours.
- How is this different from asking ChatGPT? We don't stop at advice. We fix and launch against a written scope.
Get a $149 diagnosis See pricing Fix my auth & database security
- Fixed, or we keep working free until it is (within the written scope).
- A human reviews every fix before it ships.
- read-only access; fixes arrive as pull requests you merge
- Your $149 diagnosis is credited in full toward any paid job.
FAQ
Why does my Lovable login redirect to the lovable.app preview?
The Supabase Site URL is still the preview. Change it to your live domain and add that domain to Redirect URLs.
Who can fix Supabase auth in my Lovable app?
VibePitstop fixes it as an auth & database security fix, from $400 (one issue); larger scope quoted up to $800 after diagnosis, with fixes delivered as pull requests you merge.
Will fixing auth break Lovable syncing?
No. Fixes land in your GitHub repo, which Lovable syncs with.
Related
- Fix a broken Lovable app
- Login loop after sign-in
- Login breaks on a custom domain
- Auth & database security fixes