<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AppFirstAid</title>
    <description>The latest articles on DEV Community by AppFirstAid (@appfirstaid).</description>
    <link>https://dev.to/appfirstaid</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4248236%2F9e04cf5c-18dc-4516-852b-add21331ea99.png</url>
      <title>DEV Community: AppFirstAid</title>
      <link>https://dev.to/appfirstaid</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/appfirstaid"/>
    <language>en</language>
    <item>
      <title>Supabase "permission denied for table" (42501) on a new table: why it happens and the safe fix</title>
      <dc:creator>AppFirstAid</dc:creator>
      <pubDate>Mon, 16 Nov 2026 17:31:32 +0000</pubDate>
      <link>https://dev.to/appfirstaid/supabase-permission-denied-for-table-42501-on-a-new-table-why-it-happens-and-the-safe-fix-21dn</link>
      <guid>https://dev.to/appfirstaid/supabase-permission-denied-for-table-42501-on-a-new-table-why-it-happens-and-the-safe-fix-21dn</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://appfirstaid.com/guides/supabase-new-table-permission-denied?ref=devto" rel="noopener noreferrer"&gt;AppFirstAid&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Short answer: Supabase changed a default. New tables in the &lt;code&gt;public&lt;/code&gt; schema are no longer reachable through the Data API (what &lt;code&gt;supabase-js&lt;/code&gt; uses) until you grant access to them. Supabase says this applies to all existing projects from October 30, 2026, and it's already the default for projects created since late May. Tables you already have keep working. The fix is to grant only what each role needs on that one table, keep row-level security (RLS) on, and add policies. Don't turn RLS off, and don't grant everything to everyone.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix: grant one table, keep RLS on, add policies
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Grant only the privileges each role needs on that one table.&lt;/li&gt;
&lt;li&gt;Keep row-level security on for the table.&lt;/li&gt;
&lt;li&gt;Add policies so people only see and change their own rows.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Do these three things together for each new table your app reads or writes. Replace &lt;code&gt;your_table&lt;/code&gt; and &lt;code&gt;user_id&lt;/code&gt; with your own names, and only grant what each role really needs:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="c1"&gt;-- 1. Grant only what each role needs on THIS table&lt;/span&gt;
&lt;span class="k"&gt;grant&lt;/span&gt; &lt;span class="k"&gt;select&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;insert&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;update&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;delete&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;your_table&lt;/span&gt; &lt;span class="k"&gt;to&lt;/span&gt; &lt;span class="n"&gt;authenticated&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;grant&lt;/span&gt; &lt;span class="k"&gt;select&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;insert&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;update&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;delete&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;your_table&lt;/span&gt; &lt;span class="k"&gt;to&lt;/span&gt; &lt;span class="n"&gt;service_role&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="c1"&gt;-- Only if logged-out visitors should see this table (e.g. a public list):&lt;/span&gt;
&lt;span class="c1"&gt;-- grant select on public.your_table to anon;&lt;/span&gt;

&lt;span class="c1"&gt;-- 2. Keep row-level security on&lt;/span&gt;
&lt;span class="k"&gt;alter&lt;/span&gt; &lt;span class="k"&gt;table&lt;/span&gt; &lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;your_table&lt;/span&gt; &lt;span class="n"&gt;enable&lt;/span&gt; &lt;span class="k"&gt;row&lt;/span&gt; &lt;span class="n"&gt;level&lt;/span&gt; &lt;span class="n"&gt;security&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c1"&gt;-- 3. Policies: people only see and change their own rows&lt;/span&gt;
&lt;span class="k"&gt;create&lt;/span&gt; &lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="s2"&gt;"read own rows"&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;your_table&lt;/span&gt;
  &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="k"&gt;to&lt;/span&gt; &lt;span class="n"&gt;authenticated&lt;/span&gt; &lt;span class="k"&gt;using&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;uid&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;user_id&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;create&lt;/span&gt; &lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="s2"&gt;"add own rows"&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;your_table&lt;/span&gt;
  &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="k"&gt;insert&lt;/span&gt; &lt;span class="k"&gt;to&lt;/span&gt; &lt;span class="n"&gt;authenticated&lt;/span&gt; &lt;span class="k"&gt;with&lt;/span&gt; &lt;span class="k"&gt;check&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;uid&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;user_id&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;create&lt;/span&gt; &lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="s2"&gt;"edit own rows"&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;your_table&lt;/span&gt;
  &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="k"&gt;update&lt;/span&gt; &lt;span class="k"&gt;to&lt;/span&gt; &lt;span class="n"&gt;authenticated&lt;/span&gt; &lt;span class="k"&gt;using&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;uid&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;user_id&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;with&lt;/span&gt; &lt;span class="k"&gt;check&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;uid&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;user_id&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What not to do, even if a forum answer or an AI suggests it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Don't disable RLS to make the error go away. With the grant in place and RLS off, anyone with your public key can read the whole table.&lt;/li&gt;
&lt;li&gt;Don't grant everything on every table (for example &lt;code&gt;grant all on all tables in schema public to anon&lt;/code&gt;). That undoes the protection for tables you meant to keep private.&lt;/li&gt;
&lt;li&gt;Don't give &lt;code&gt;anon&lt;/code&gt; insert, update or delete unless logged-out visitors really need to write to that table, and then only with a strict policy.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If inserts still fail with &lt;code&gt;permission denied for sequence&lt;/code&gt;, the table uses an older-style auto-numbering column. Grant &lt;code&gt;usage, select&lt;/code&gt; on that one sequence to the same role.&lt;/p&gt;

&lt;h2&gt;
  
  
  Signs this is your problem
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;You (or your AI builder) just added a feature with a new table, and that page fails while older pages still work.&lt;/li&gt;
&lt;li&gt;The browser console or network tab shows an error with code &lt;code&gt;42501&lt;/code&gt; and a message like &lt;code&gt;permission denied for table your_table&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The page just looks empty, or saving does nothing. Many AI-built apps hide database errors, so a refused request can look like "no data yet".&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Supabase's own example of the error looks like this, and the &lt;code&gt;hint&lt;/code&gt; tells you which role is missing which permission:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"code"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"42501"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"permission denied for table your_table"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"hint"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Grant the required privileges to the current role with: GRANT SELECT ON public.your_table TO anon;"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Supabase has two separate layers of protection:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Grants decide whether a role can touch a table at all. The roles that matter are &lt;code&gt;anon&lt;/code&gt; (visitors who aren't logged in), &lt;code&gt;authenticated&lt;/code&gt; (logged-in users) and &lt;code&gt;service_role&lt;/code&gt; (your server code).&lt;/li&gt;
&lt;li&gt;RLS policies decide which rows that role can see or change.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Until now, every new table in &lt;code&gt;public&lt;/code&gt; got grants for all three roles automatically. Supabase is ending that so a new table isn't exposed before anyone has secured it. Its timeline: optional from April 28, 2026; the default for new projects from May 30, 2026 (rolled out gradually); applied to all existing projects on October 30, 2026. After that, a table created without a grant isn't visible to the Data API, however it was made: the SQL editor, a migration, the CLI or an AI coding tool.&lt;/p&gt;

&lt;p&gt;It only matters if your app talks to the database through the Data API (&lt;code&gt;supabase-js&lt;/code&gt;, the other client libraries, or &lt;code&gt;/rest/v1/&lt;/code&gt; and &lt;code&gt;/graphql/v1&lt;/code&gt;). Apps that only use a direct Postgres connection aren't affected. Supabase also says tables in the &lt;code&gt;auth&lt;/code&gt;, &lt;code&gt;storage&lt;/code&gt; and &lt;code&gt;realtime&lt;/code&gt; schemas, and tables you already have, keep their current grants.&lt;/p&gt;

&lt;p&gt;Building on Bolt's own database instead? Bolt made a similar change on the same date: new tables are private by default. See &lt;a href="https://appfirstaid.com/guides?ref=devto" rel="noopener noreferrer"&gt;Bolt app shows a database permissions error on a new table&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Copy-paste prompt for Lovable, Bolt, Cursor or another AI builder
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Supabase no longer exposes new tables in the public schema to the Data API until they are granted (applies to existing projects from Oct 30, 2026). My app gets "permission denied" (42501) or empty results on a newer table. Please:
1. List every table my app reads or writes through supabase-js, and which ones were created recently.
2. For each of those, write ONE migration that grants only the privileges each role needs on that table (authenticated and service_role as needed; anon only select, and only if logged-out visitors must see it), keeps row level security enabled, and adds policies so users only see and change their own rows (auth.uid() = user_id, with check on insert and update).
3. Do NOT disable RLS and do NOT grant all privileges to anon or on all tables.
4. Show me the SQL before running it. Then make the app show a real error message instead of an empty page when a database request fails.
5. From now on, every new table you create must include its grants, RLS and policies in the same migration.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Coding by hand?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Put the grants in the same migration that creates the table, next to &lt;code&gt;enable row level security&lt;/code&gt; and the policies, so they can't be forgotten.&lt;/li&gt;
&lt;li&gt;Read the &lt;code&gt;hint&lt;/code&gt; in the 42501 response: it names the role and the missing permission. Grant that, not more.&lt;/li&gt;
&lt;li&gt;In the Supabase dashboard, the Table Editor shows a Data API exposure badge and the Security Advisor lists tables worth reviewing, per Supabase's announcement.&lt;/li&gt;
&lt;li&gt;In local development, recent Supabase CLI versions apply the same new default, so a migration that works locally with grants will behave the same in production.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Check that it worked
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In a private window, log in as a normal test user (not an admin) and use the feature. Rows you create should show up, and you should see only your own.&lt;/li&gt;
&lt;li&gt;Log out and try the same page. Logged-out visitors should see nothing private.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The full checklist, including how to test the table the way a stranger would, is in the &lt;a href="https://appfirstaid.com/guides/supabase-new-table-permission-denied?ref=devto" rel="noopener noreferrer"&gt;original guide&lt;/a&gt;. If you want a quick outside check of your live app's sign-up, login and checkout, &lt;a href="https://appfirstaid.com/?ref=devto" rel="noopener noreferrer"&gt;AppFirstAid runs a free scan&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>postgres</category>
      <category>webdev</category>
      <category>security</category>
    </item>
    <item>
      <title>Login broke after I added my custom domain (Supabase redirect URLs)</title>
      <dc:creator>AppFirstAid</dc:creator>
      <pubDate>Mon, 16 Nov 2026 17:29:44 +0000</pubDate>
      <link>https://dev.to/appfirstaid/login-broke-after-i-added-my-custom-domain-supabase-redirect-urls-51fg</link>
      <guid>https://dev.to/appfirstaid/login-broke-after-i-added-my-custom-domain-supabase-redirect-urls-51fg</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://appfirstaid.com/guides/login-broke-after-custom-domain?ref=devto" rel="noopener noreferrer"&gt;AppFirstAid&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Short answer: your login provider still thinks your app lives at the old address. In Supabase, go to Authentication → URL Configuration, set the Site URL to your new domain and add it to Redirect URLs (for example &lt;code&gt;https://yourdomain.com/**&lt;/code&gt;). If your app asks to send people somewhere that isn't on that list, Supabase quietly sends them to the Site URL instead, which is often the old preview link or localhost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Signs this is your problem
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The confirmation or password-reset email opens the preview link, &lt;code&gt;localhost&lt;/code&gt;, or a page that says the link is invalid.&lt;/li&gt;
&lt;li&gt;Google sign-in finishes, then lands on the old address.&lt;/li&gt;
&lt;li&gt;Everything works on the preview link but not on your real domain, or the reverse.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Fix it in Supabase
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open your project, then Authentication → URL Configuration.&lt;/li&gt;
&lt;li&gt;Set Site URL to the address customers use, like &lt;code&gt;https://yourdomain.com&lt;/code&gt;. This is the default place people are sent after confirming their email.&lt;/li&gt;
&lt;li&gt;Under Redirect URLs, add every address your app sends people back to. Wildcards are allowed, so &lt;code&gt;https://yourdomain.com/**&lt;/code&gt; covers every page. Add &lt;code&gt;https://www.yourdomain.com/**&lt;/code&gt; too if people can reach the www version.&lt;/li&gt;
&lt;li&gt;Keep your preview link in the list if you still test there, and remove addresses you no longer use.&lt;/li&gt;
&lt;li&gt;If you edited the email templates, check the links in them. A template that builds its link from the Site URL follows step 2, so set that first.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Then check your app's code
&lt;/h2&gt;

&lt;p&gt;AI builders often write the old address straight into the code, for example as the &lt;code&gt;emailRedirectTo&lt;/code&gt; or &lt;code&gt;redirectTo&lt;/code&gt; option when signing up, resetting a password or signing in with Google. Search your project for the preview domain and for &lt;code&gt;localhost&lt;/code&gt;. A safer pattern is to build the address from wherever the app is running:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="n"&gt;emailRedirectTo&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;location&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;origin&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="s2"&gt;"/auth/callback"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Prompt idea for your builder: "Find every hardcoded preview URL or localhost in the auth code and replace it with window.location.origin, so sign-up, password reset and OAuth redirects work on my custom domain."&lt;/p&gt;

&lt;p&gt;If your app keeps its address in a setting like &lt;code&gt;VITE_SITE_URL&lt;/code&gt; or &lt;code&gt;NEXT_PUBLIC_SITE_URL&lt;/code&gt;, make sure the production value is your real domain and redeploy. More in &lt;a href="https://appfirstaid.com/guides?ref=devto" rel="noopener noreferrer"&gt;My app works in preview but breaks in production&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  www and non-www are different sites
&lt;/h2&gt;

&lt;p&gt;To a browser, &lt;code&gt;yourdomain.com&lt;/code&gt; and &lt;code&gt;www.yourdomain.com&lt;/code&gt; are different places, and a login on one isn't shared with the other. Pick one, redirect the other to it in your host's domain settings, and make sure the Site URL uses the one you picked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Google and other sign-in providers
&lt;/h2&gt;

&lt;p&gt;With Supabase handling Google sign-in, the redirect address in your Google Cloud settings is your Supabase project's callback (&lt;code&gt;https://&amp;lt;project-ref&amp;gt;.supabase.co/auth/v1/callback&lt;/code&gt;), and it doesn't change when you add a custom domain. Where people land afterwards is controlled by the Supabase settings above. If Google stops at "Error 400: redirect_uri_mismatch" instead (for example after giving the Supabase project its own custom domain, or when your app talks to Google directly), see &lt;a href="https://appfirstaid.com/guides/google-sign-in-redirect-uri-mismatch?ref=devto" rel="noopener noreferrer"&gt;Google sign-in says redirect_uri_mismatch&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Using Firebase or Clerk instead?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Firebase: open Authentication → Settings → Authorized domains and add your custom domain. Sign-in from a domain that isn't listed is refused.&lt;/li&gt;
&lt;li&gt;Clerk: development and production are separate instances. Going live on your own domain means setting up the production instance with your domain and its DNS records, and using the production keys.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Test like a new customer
&lt;/h2&gt;

&lt;p&gt;Open a private window on your real domain and go through it all: sign up with an email you haven't used, click the confirmation link, log out, log back in, and reset your password. A private window matters: your normal browser is probably still logged in, which hides the problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Why do sign-up emails send people to localhost or my preview link?
&lt;/h3&gt;

&lt;p&gt;Your login provider still thinks your app lives at the old address. In Supabase, open Authentication → URL Configuration, set the Site URL to your new domain and add it to Redirect URLs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need to change my Google Cloud redirect URI when I add a custom domain with Supabase?
&lt;/h3&gt;

&lt;p&gt;No. With Supabase handling Google sign-in, the redirect address in Google Cloud is your Supabase project's callback (https://.supabase.co/auth/v1/callback), which doesn't change. Where people land afterwards is set by Supabase's Site URL and Redirect URLs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Login broke on my custom domain with Firebase. What do I check?
&lt;/h3&gt;

&lt;p&gt;In Firebase, open Authentication → Settings → Authorized domains and add your custom domain. Sign-in from a domain that isn't listed is refused.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check your live app in under a minute
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://appfirstaid.com/?ref=devto" rel="noopener noreferrer"&gt;Run the free check&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;AppFirstAid's free check looks at your live site from the outside: leaked keys, files left in public, safety settings, and whether your sign-up, login and checkout pages open. No signup. Journey tests go further: a simulated first-time user (a real browser) signs up, opens your email, logs in and tries checkout, and shows you the step that broke. Your first journey test is free.&lt;/p&gt;

&lt;p&gt;Settings move around as these tools update. If a menu name has changed, look for the same words nearby. Spotted something out of date? Tell us (&lt;a href="mailto:hello@appfirstaid.com"&gt;hello@appfirstaid.com&lt;/a&gt;).&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>webdev</category>
      <category>authentication</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
