[{"data":1,"prerenderedAt":1154},["ShallowReactive",2],{"blog-en-auth-session-missing":3,"blog-index-en":628},{"id":4,"title":5,"body":6,"category":586,"cover":587,"coverAlt":588,"description":589,"draft":590,"extension":591,"faq":592,"image":607,"keywords":608,"meta":616,"navigation":617,"ogTitle":618,"path":619,"published":620,"seo":621,"stem":622,"tldr":623,"updated":620,"__hash__":627},"blog_en\u002Fblog\u002Fauth-session-missing.md","Supabase \"Auth session missing!\": where the session went",{"type":7,"value":8,"toc":574},"minimark",[9,13,24,27,43,48,51,54,72,75,81,85,90,108,116,123,150,153,159,170,174,177,186,212,237,246,258,263,267,270,296,302,319,335,339,342,351,361,367,370,376,382,400,410,414,417,435,453,460,464,470,479,493,503,520,524,561],[10,11,12],"p",{},"Your Lovable or Bolt app signs people in with Supabase. One morning you open\nthe browser console and find this in red, on a page where nothing looks wrong:",[14,15,20],"pre",{"className":16,"code":18,"language":19},[17],"language-text","AuthSessionMissingError: Auth session missing!\n","text",[21,22,18],"code",{"__ignoreMap":23},"",[10,25,26],{},"Or a customer writes in to say the \"set a new password\" page refuses them with\nthe same words, every time.",[10,28,29,30,33,34,37,38,42],{},"Search \"auth session missing supabase\" and you will find threads full of\nfixes: switch ",[21,31,32],{},"getUser()"," to ",[21,35,36],{},"getSession()",", downgrade the library, add a\ndelay, restart the project. They assume something between your app and\nSupabase broke. ",[39,40,41],"strong",{},"No request was made."," The error is written inside your app,\nby the Supabase library, before anything leaves the browser.",[44,45,47],"h2",{"id":46},"what-does-auth-session-missing-mean-in-supabase","What does \"Auth session missing!\" mean in Supabase?",[10,49,50],{},"supabase-js was asked who is signed in, looked for a session, found none, and\nanswered on its own.",[10,52,53],{},"A session is what Supabase Auth hands a person when they sign in: a pair of\ntokens that say who they are, kept by the browser so the next page load still\nknows them. supabase-js is the library your app uses to talk to Supabase, and\nevery call that needs a person starts by taking out that session.",[10,55,56,57,60,61,64,65,68,69,71],{},"The message is written in supabase-js itself, in the auth library's\n",[21,58,59],{},"errors.ts",": an ",[21,62,63],{},"AuthSessionMissingError"," with the text ",[21,66,67],{},"Auth session missing!","\nand the status 400. The 400 is a label the library gives itself. No server\nanswered with it, and Supabase's logs will show nothing, because ",[21,70,32],{},"\nchecks for a session before it does anything else. Its source says so in a\ncomment: it \"returns an error if there is no access_token or custom\nauthorization header\".",[10,73,74],{},"Picture a front desk that can tell you which visitor someone is. Everyone who\nsigns in is given a badge at the door, and supabase-js keeps that badge in the\nbrowser's pocket. When your code asks \"who is this?\", supabase-js reaches into\nthe pocket first. If there is a badge, it walks it to the desk and brings back\na name. If the pocket is empty, it does not walk to the desk at all. It comes\nstraight back and tells you there is no badge.",[76,77],"diagram",{"alt":78,"caption":79,"src":80},"Two lanes start from a browser window. In the upper one a badge travels to a front desk, and the desk answers with a person and a tick. In the lower one the badge holder is empty and outlined in amber, and the lane stops at a cross with 400 beside it, well before the desk, which stays dim and dashed.","With a session, supabase-js asks Supabase Auth. Without one, it stops in your app and the error comes from there.","\u002Fblog\u002Fauth-session-missing\u002Fthe-empty-pocket-1600x720.png",[44,82,84],{"id":83},"it-is-handed-back-not-thrown","It is handed back, not thrown",[10,86,87,89],{},[21,88,32],{}," returns the error next to an empty user, and your code decides what\nhappens next.",[10,91,92,93,96,97,100,101,104,105,107],{},"The call looks like this, and with no session the result is ",[21,94,95],{},"user"," set to\n",[21,98,99],{},"null"," and ",[21,102,103],{},"error"," set to the ",[21,106,63],{},":",[14,109,114],{"className":110,"code":112,"language":113,"meta":23},[111],"language-ts","const { data: { user }, error } = await supabase.auth.getUser()\n","ts",[21,115,112],{"__ignoreMap":23},[10,117,118,119,122],{},"Nothing is thrown, so a ",[21,120,121],{},"try … catch"," around the call catches nothing. That is\nwhere the visible damage comes from, in one of two shapes:",[124,125,126,136],"ul",{},[127,128,129,135],"li",{},[39,130,131,132,134],{},"The code shows any ",[21,133,103],{}," it gets."," A visitor who has not signed in yet\nsees \"Auth session missing!\" in a toast or a red box on a page they were\nallowed to see.",[127,137,138,141,142,145,146,149],{},[39,139,140],{},"The code uses the user without checking."," It reads ",[21,143,144],{},"user.id"," and the page\nbreaks with ",[21,147,148],{},"Cannot read properties of null",", which looks like a different\nbug entirely.",[10,151,152],{},"Both are the same mistake: treating \"nobody is signed in\" as a failure. Check\nthe user first, and give a signed-out visitor the screen meant for them:",[14,154,157],{"className":155,"code":156,"language":113,"meta":23},[111],"const { data: { user } } = await supabase.auth.getUser()\nif (!user) {\n  \u002F\u002F nobody is signed in: show the sign-in screen, or the public page\n  return\n}\n",[21,158,156],{"__ignoreMap":23},[10,160,161,162,165,166,169],{},"If you want to tell this apart from a real failure, the library names it:\n",[21,163,164],{},"error.name"," is ",[21,167,168],{},"'AuthSessionMissingError'",".",[44,171,173],{"id":172},"where-the-session-goes-missing","Where the session goes missing",[10,175,176],{},"Three places, and only the first one is harmless.",[10,178,179,182,183,185],{},[39,180,181],{},"1. Nobody has signed in on this browser."," Your app calls ",[21,184,32],{}," on a\npage anyone can open, perhaps to decide whether to show \"Sign in\" or \"My\naccount\". For a visitor, the empty pocket is the true answer. This is where\nmost people meet the message, and the code fix above is all it needs.",[10,187,188,191,192,195,196,203,204,207,208,211],{},[39,189,190],{},"2. A password reset or magic link page."," Setting a new password calls\n",[21,193,194],{},"updateUser({ password })",", and Supabase's\n",[197,198,202],"a",{"href":199,"rel":200},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fpasswords",[201],"nofollow","password guide"," is plain\nabout the order: \"Once you have a session, collect the user's new password and\ncall ",[21,205,206],{},"updateUser",".\" On that page, the session is supposed to come from the link\nin the email, which signs the person in as it opens. When it does not, the\npocket is empty and ",[21,209,210],{},"updateUser()"," answers \"Auth session missing!\". The usual\nreasons:",[124,213,214,222,225],{},[127,215,216,217,221],{},"The link had already been used, or had expired, before it was opened.\n",[197,218,220],{"href":219},"\u002Fblog\u002Femail-link-is-invalid-or-has-expired","Why Supabase says the email link is invalid or has expired","\ngoes through each one.",[127,223,224],{},"It was opened in a different browser or app from the one that asked for it.\nWhen an app uses Supabase's PKCE sign-in, part of the exchange is kept in the\nbrowser that started it, and Supabase's documentation says \"the code exchange\nmust be initiated on the same browser and device where the flow was started\".",[127,226,227,228,231,232,236],{},"It sent the person somewhere else, such as ",[21,229,230],{},"localhost",", so the session landed\non an address that is not your app.\n",[197,233,235],{"href":234},"\u002Fblog\u002Fsupabase-auth-redirects-to-localhost","Why Supabase redirects to localhost","\nhas that one.",[10,238,239,242,243,245],{},[39,240,241],{},"3. Your server or an Edge Function never received the session."," The badge\nlives in your visitor's browser. Code that runs anywhere else, a Supabase Edge\nFunction or the server half of a Next.js app built with v0 or Cursor, creates\nits own Supabase client, and a new client starts with an empty pocket. Unless\nthe visitor's session is passed in, ",[21,244,32],{}," there finds nothing and\nanswers \"Auth session missing!\" without asking Supabase.",[10,247,248,249,252,253,257],{},"In an Edge Function the session travels in the request's ",[21,250,251],{},"Authorization","\nheader, and supabase-js only uses it when you hand it over while creating the\nclient. In a Next.js app it travels in cookies, which Supabase's server-side\nhelper reads only if you give it the request's cookies. If an Edge Function\nhands that failure back as an error, your app shows\n",[197,254,256],{"href":255},"\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code","\"Edge Function returned a non-2xx status code\"","\nwith this message waiting in the function's log.",[76,259],{"alt":260,"caption":261,"src":262},"A person at a browser window, wearing a badge, sends two requests to an Edge Function. In the upper lane the request arrives without the badge, the function's own holder is empty and outlined in amber, and the lane ends in a cross. In the lower lane the badge travels with the request under the label Authorization, the function's holder is filled, and the desk answers with a tick.","The session belongs to the browser. A function or server only has it if the request carries it and the code passes it to its client.","\u002Fblog\u002Fauth-session-missing\u002Fthe-badge-stays-behind-1600x760.png",[44,264,266],{"id":265},"how-to-tell-which-one-you-have","How to tell which one you have",[10,268,269],{},"Look at where the message appears, then at what the browser actually sent.",[10,271,272,275,276,279,280,283,284,287,288,291,292,295],{},[39,273,274],{},"In the browser console, on a page anyone can open."," Route 1. Open your\nbrowser's developer tools (F12), choose ",[39,277,278],{},"Application",", then ",[39,281,282],{},"Local\nStorage"," and your app's address. supabase-js keeps the session under a key\nshaped like ",[21,285,286],{},"sb-"," followed by your project's id and ",[21,289,290],{},"-auth-token",". If there is\nno such entry, this browser has no session, and the message is telling the\ntruth. A Next.js app using Supabase's server-side helpers keeps the session in\ncookies instead, so look under ",[39,293,294],{},"Cookies"," for the same name.",[10,297,298,301],{},[39,299,300],{},"On a reset or magic link page."," Route 2. Look at the address the link opened\non. If it is not your app, or it is a link you or a mail scanner already\nopened, the session never had a chance to arrive.",[10,303,304,307,308,311,312,314,315,318],{},[39,305,306],{},"In an Edge Function's log, or your server's."," Route 3. Open the ",[39,309,310],{},"Network","\ntab, repeat the action and click the request to your function. If its\n",[21,313,251],{}," header holds a long string beginning ",[21,316,317],{},"eyJ",", the browser sent a\nperson's token and your function did not pass it on to its client.",[10,320,321,322,325,326,329,330,334],{},"One thing you will not find, on any route, is a request to ",[21,323,324],{},"\u002Fauth\u002Fv1\u002Fuser"," that\ncame back with this message. If you do see one that failed, it is a different\nerror. A reply saying ",[21,327,328],{},"invalid claim: missing sub claim"," means your project key\nwas sent where a person belongs, and\n",[197,331,333],{"href":332},"\u002Fblog\u002Finvalid-claim-missing-sub-claim","that post"," is its twin.",[44,336,338],{"id":337},"the-fix-for-each-route","The fix for each route",[10,340,341],{},"Give each one the session it is missing, or an answer that does not need one.",[10,343,344,347,348,350],{},[39,345,346],{},"Route 1, the signed-out visitor:"," check ",[21,349,95],{}," before using it, as in the\ncode above, and show the screen meant for someone who has not signed in.",[10,352,353,356,357,360],{},[39,354,355],{},"Route 2, the reset page:"," wait for the link to sign the person in before you\nshow the form. Supabase sends a ",[21,358,359],{},"PASSWORD_RECOVERY"," event when someone arrives\nfrom a recovery link, and its reference shows the page listening for it:",[14,362,365],{"className":363,"code":364,"language":113,"meta":23},[111],"supabase.auth.onAuthStateChange((event) => {\n  if (event === 'PASSWORD_RECOVERY') {\n    \u002F\u002F the link signed them in: now show the new-password form\n  }\n})\n",[21,366,364],{"__ignoreMap":23},[10,368,369],{},"If the event never comes, the link did not work. Say so, and offer to send a\nnew one, rather than showing a form that is certain to fail.",[10,371,372,375],{},[39,373,374],{},"Route 3, the function or server:"," pass the visitor's session to the client\nyou create. In an Edge Function, create it with the incoming header:",[14,377,380],{"className":378,"code":379,"language":113,"meta":23},[111],"const supabase = createClient(\n  Deno.env.get('SUPABASE_URL')!,\n  Deno.env.get('SUPABASE_ANON_KEY')!,\n  { global: { headers: { Authorization: req.headers.get('Authorization')! } } },\n)\nconst { data: { user } } = await supabase.auth.getUser()\nif (!user) {\n  return new Response(JSON.stringify({ error: 'Sign in first' }), {\n    status: 401,\n    headers: { ...corsHeaders, 'Content-Type': 'application\u002Fjson' },\n  })\n}\n",[21,381,379],{"__ignoreMap":23},[10,383,384,385,388,389,393,394,396,397,399],{},"Supabase's newer ",[21,386,387],{},"withSupabase({ auth: 'user' })"," wrapper does the same before\nyour handler runs, and the\n",[197,390,392],{"href":391},"\u002Fblog\u002Fmove-a-secret-to-an-edge-function","Edge Function post"," shows the setup.\nKeep the 401 for a caller with no session, so a request from a signed-out page\ngets a clear refusal. With the header passed on, a signed-out caller's\n",[21,395,32],{}," there may come back with ",[21,398,328],{},"\ninstead: the same visitor seen from the other side, and the 401 covers both.",[10,401,402,403,406,407,409],{},"In a Next.js app, create the server client with Supabase's ",[21,404,405],{},"@supabase\u002Fssr","\nhelper and the request's cookies, as its server-side setup shows, and call\n",[21,408,32],{}," on that client.",[44,411,413],{"id":412},"two-fixes-that-make-it-worse","Two fixes that make it worse",[10,415,416],{},"Both get suggested for this message, and each one stops the error by removing\nthe check behind it.",[10,418,419,427,428,431,432,434],{},[39,420,421,422,424,425,169],{},"Swapping ",[21,423,32],{}," for ",[21,426,36],{}," In the browser it changes nothing\nthat matters: the storage is still empty, so you get no session and no user,\nonly without the message. On a server it is dangerous. Supabase's server-side\nguide says \"Never trust ",[21,429,430],{},"supabase.auth.getSession()"," inside server code\",\nbecause \"It reads the session out of the cookie without revalidating it.\" A\ncookie is something the visitor sends you, and anyone can send you any cookie\nthey like. ",[21,433,32],{}," is the one supabase-js documents as making \"a network\nrequest to the Supabase Auth server, so the returned value is authentic\". Keep\nit wherever the answer decides what someone may do.",[10,436,437,440,441,444,445,448,449,169],{},[39,438,439],{},"Putting the secret key into the client so the call stops failing."," A client\nmade with the ",[21,442,443],{},"service_role"," or ",[21,446,447],{},"sb_secret_"," key does not need a session to\nread and write, because it skips your database rules entirely. The function\nworks again, for every caller, signed in or not. If a builder makes that change\nin code that ships to the browser, the key goes out to every visitor with it.\nIf it already has, ",[197,450,452],{"href":451},"\u002Fblog\u002Frotate-supabase-service-role-key","rotate it first",[10,454,455,456,169],{},"You can check that from outside. Our free scan reads your live app's JavaScript\nthe way a stranger would and names every key it finds, including whether it is\none that belongs there. It takes about 20 seconds and needs no account:\n",[197,457,459],{"href":458},"\u002Fsecurity-scanner","scan your app",[44,461,463],{"id":462},"keeping-the-check-in-place-after-the-next-change","Keeping the check in place after the next change",[10,465,466,469],{},[39,467,468],{},"The check on who is signed in is the part of a page most likely to vanish\nwhen you ask your builder to make an error go away",", and both of the quick\nfixes above remove it.",[10,471,472],{},[39,473,474,478],{},[197,475,477],{"href":476},"\u002Fwebsite-monitoring","Reeve Monitor"," re-scans your live app every hour:",[124,480,481,484,487,490],{},[127,482,483],{},"all nine checks every hour, on up to three apps",[127,485,486],{},"an email the day a re-scan grades your app lower than the one before; a secret key in your JavaScript caps the grade at D on its own",[127,488,489],{},"whether the app is up, every 60 seconds",[127,491,492],{},"a monthly report of what it saw",[10,494,495],{},[39,496,497,498,502],{},"A server that believes any cookie, or a function running on the secret key,\nlets a stranger change your users' rows. ",[197,499,501],{"href":500},"\u002Fsupabase-backups","Reeve Care"," keeps\na copy of your Supabase database from before that happens.",[124,504,505,508,511,514,517],{},[127,506,507],{},"an encrypted copy on a schedule, kept on Reeve's own storage in the EU, outside your Supabase account",[127,509,510],{},"each copy verified before it counts, by counting the rows in every table",[127,512,513],{},"a one-click restore that saves what is there now before it replaces anything",[127,515,516],{},"your uploaded files as well, once you connect a Storage credential",[127,518,519],{},"everything Monitor does",[44,521,523],{"id":522},"what-to-do-now","What to do now",[525,526,527],"key-takeaways",{},[124,528,529,532,540,546,552],{},[127,530,531],{},"Read \"Auth session missing!\" as \"nobody is signed in here\". The request never left your app.",[127,533,534,535,424,537,539],{},"Check ",[21,536,95],{},[21,538,99],{}," before using it, and give a signed-out visitor the screen meant for them instead of the error.",[127,541,542,543,545],{},"On a reset page, wait for the ",[21,544,359],{}," event before showing the form, and offer a new link when it never arrives.",[127,547,548,549,551],{},"In an Edge Function or on a server, pass the visitor's ",[21,550,251],{}," header or cookies to the client you create, and answer 401 when there is still no user.",[127,553,554,555,557,558,560],{},"Keep ",[21,556,32],{}," on the server. ",[21,559,36],{}," there believes whatever cookie it is sent.",[10,562,563,564,568,569,573],{},"If your sessions exist and then disappear, so that people who were signed in\nare suddenly signed out, that is a different problem with its own causes, and\n",[197,565,567],{"href":566},"\u002Fblog\u002Fsupabase-users-logged-out","why Supabase users get logged out"," covers it.\nThe ",[197,570,572],{"href":571},"\u002Fchecklist","10-minute security checklist"," covers what else a newly\nlaunched app tends to leave open.",{"title":23,"searchDepth":575,"depth":575,"links":576},3,[577,579,580,581,582,583,584,585],{"id":46,"depth":578,"text":47},2,{"id":83,"depth":578,"text":84},{"id":172,"depth":578,"text":173},{"id":265,"depth":578,"text":266},{"id":337,"depth":578,"text":338},{"id":412,"depth":578,"text":413},{"id":462,"depth":578,"text":463},{"id":522,"depth":578,"text":523},"Security basics","\u002Fblog\u002Fauth-session-missing\u002Fcover-1200x630.png","An empty badge holder on a lanyard, the space where the badge belongs outlined in amber, in front of two badges that carry a face.","\"Auth session missing!\" is supabase-js finding no signed-in session and stopping before it asks Supabase. Where the session went, and the fix for each.",false,"md",[593,595,598,601,604],{"q":47,"a":594},"It means supabase-js, the Supabase library inside your app, was asked for the signed-in user and had no session to ask with. A session is what Supabase Auth gives a person when they sign in, and the library keeps it in the browser. With none there, it does not contact Supabase at all. It hands back AuthSessionMissingError with the status 400 and a user of null.",{"q":596,"a":597},"Why do I see \"Auth session missing!\" when nobody is logged in?","Because that is the answer for a visitor who has not signed in. Your app called getUser() on a page that anyone can open, and supabase-js reported that nobody was signed in. Nothing is broken. Your code only has to read user as null and show the sign-in screen, instead of showing the error.",{"q":599,"a":600},"Why does my password reset page say \"Auth session missing!\"?","Changing a password with updateUser() needs a session, and on a reset page that session is supposed to come from the link in the email. If the link had already been used or had expired, was opened in a different browser from the one that asked for it, or sent the person to a different address, no session arrived and updateUser() has nobody to change. Wait for the PASSWORD_RECOVERY event before showing the form, and offer a fresh link when it never comes.",{"q":602,"a":603},"Is \"Auth session missing!\" the same as \"invalid claim: missing sub claim\"?","No. \"Auth session missing!\" is decided inside your app, before any request leaves it. \"invalid claim: missing sub claim\" comes back from Supabase Auth, which received a request and found your project key where a person's token should be. The first means there was nothing to send. The second means the wrong thing was sent.",{"q":605,"a":606},"Should I use getSession() instead of getUser()?","Not to make this error go away. In the browser, getSession() finds the same empty storage and returns no session, so nothing changes except that the error message stops. On a server it is worse: supabase-js documents that getSession() reads the session straight from storage such as request cookies, which may not be authentic, and recommends getUser() instead because it checks with Supabase Auth.","\u002Fblog\u002Fauth-session-missing\u002Fcard-800x500.png",[609,610,611,612,613,614,615],"auth session missing supabase","AuthSessionMissingError: Auth session missing!","supabase getuser auth session missing","supabase updateuser auth session missing","supabase reset password auth session missing","supabase edge function auth session missing","supabase ssr auth session missing",{},true,"\"Auth session missing!\" in Supabase","\u002Fblog\u002Fauth-session-missing","2026-11-05",{"title":5,"description":589},"blog\u002Fauth-session-missing",[624,625,626],"\"Auth session missing!\" (AuthSessionMissingError, status 400) comes from supabase-js inside your app. It looked for a signed-in session, found none, and never sent the request to Supabase.","On a page nobody has signed in to, that is the correct answer and your code only has to handle it. On a password reset page it means the link never signed anyone in here. In an Edge Function or on a server, the visitor's session was never passed along.","Leave getUser() where it is. Swapping in getSession() on a server makes the error go away by trusting whatever the cookie says.","m1r56oWbT2V0wYFtw0rsKtsQxypcfg6I2eKi7Q6qakg",[629,635,641,647,653,654,659,665,670,675,681,688,694,700,705,711,717,723,729,735,741,747,752,758,764,770,776,782,788,794,800,806,812,818,824,830,835,841,847,853,859,865,871,877,883,889,894,900,906,912,918,924,930,936,942,948,954,960,966,972,978,984,990,996,1001,1007,1013,1019,1025,1031,1037,1043,1049,1055,1061,1067,1073,1079,1085,1091,1097,1103,1109,1115,1120,1126,1132,1138,1143,1149],{"path":630,"title":631,"description":632,"published":633,"category":586,"image":634,"draft":590},"\u002Fblog\u002Fmax-client-connections-reached","Supabase \"max client connections reached\", explained","Supabase \"max client connections reached\" means the pooler has no room for one more client. The port in your connection string decides the limit.","2026-11-09","\u002Fblog\u002Fmax-client-connections-reached\u002Fcard-800x500.png",{"path":636,"title":637,"description":638,"published":639,"category":586,"image":640,"draft":590},"\u002Fblog\u002Funsupported-provider-provider-is-not-enabled","\"Unsupported provider: provider is not enabled\" in Supabase","\"Unsupported provider: provider is not enabled\" means Google sign-in is off in your Supabase project. How to turn it on, and fix redirect_uri_mismatch.","2026-11-08","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled\u002Fcard-800x500.png",{"path":642,"title":643,"description":644,"published":645,"category":586,"image":646,"draft":590},"\u002Fblog\u002Fviolates-foreign-key-constraint","\"violates foreign key constraint\" on insert in Supabase","Supabase \"insert or update on table violates foreign key constraint\": your row points at a row that is not there. Which one, why, and the fix.","2026-11-07","\u002Fblog\u002Fviolates-foreign-key-constraint\u002Fcard-800x500.png",{"path":648,"title":649,"description":650,"published":651,"category":586,"image":652,"draft":590},"\u002Fblog\u002Fnull-value-violates-not-null-constraint","\"null value in column violates not-null constraint\" in Supabase","Supabase \"null value in column violates not-null constraint\": a required column arrived empty. Where the null came from, and the fix.","2026-11-06","\u002Fblog\u002Fnull-value-violates-not-null-constraint\u002Fcard-800x500.png",{"path":619,"title":5,"description":589,"published":620,"category":586,"image":607,"draft":590},{"path":332,"title":655,"description":656,"published":657,"category":586,"image":658,"draft":590},"Supabase \"invalid claim: missing sub claim\": nobody is signed in","\"invalid claim: missing sub claim\" means Supabase Auth got a genuine token that names no user: your project key, sent where a session belongs.","2026-11-04","\u002Fblog\u002Finvalid-claim-missing-sub-claim\u002Fcard-800x500.png",{"path":660,"title":661,"description":662,"published":663,"category":586,"image":664,"draft":590},"\u002Fblog\u002Ffailed-to-send-a-request-to-the-edge-function","\"Failed to send a request to the Edge Function\" in Supabase","\"Failed to send a request to the Edge Function\" means the browser got no reply it could read. Its console says why, and whether your function ran.","2026-11-03","\u002Fblog\u002Ffailed-to-send-a-request-to-the-edge-function\u002Fcard-800x500.png",{"path":234,"title":666,"description":667,"published":668,"category":586,"image":669,"draft":590},"Why Supabase email links redirect to localhost:3000","A Supabase redirect to localhost:3000 means the Site URL was never changed, or your address is missing from Redirect URLs. The fix, and the wildcard to avoid.","2026-11-02","\u002Fblog\u002Fsupabase-auth-redirects-to-localhost\u002Fcard-800x500.png",{"path":219,"title":671,"description":672,"published":673,"category":586,"image":674,"draft":590},"Supabase \"Email link is invalid or has expired\" on a fresh link","On a link sent a minute ago, Supabase's \"Email link is invalid or has expired\" usually means a mail filter used it first. How to check and fix it.","2026-11-01","\u002Fblog\u002Femail-link-is-invalid-or-has-expired\u002Fcard-800x500.png",{"path":676,"title":677,"description":678,"published":679,"category":586,"image":680,"draft":590},"\u002Fblog\u002Fcanceling-statement-due-to-statement-timeout","Supabase \"canceling statement due to statement timeout\", explained","Supabase \"canceling statement due to statement timeout\" means a query outran its role's limit, 3 seconds for a visitor. Check the RLS policy first.","2026-10-31","\u002Fblog\u002Fcanceling-statement-due-to-statement-timeout\u002Fcard-800x500.png",{"path":682,"title":683,"description":684,"published":685,"category":686,"image":687,"draft":590},"\u002Fblog\u002Fdatabase-error-deleting-user","\"Database error deleting user\" in Supabase, and what goes with it","\"Database error deleting user\" in Supabase means your database refused the delete. The reason is in your logs, and the fix decides what else is deleted.","2026-10-30","Backups","\u002Fblog\u002Fdatabase-error-deleting-user\u002Fcard-800x500.png",{"path":689,"title":690,"description":691,"published":692,"category":586,"image":693,"draft":590},"\u002Fblog\u002Fstripe-webhook-no-signatures-found","\"No signatures found matching the expected signature\" in Supabase","A Stripe webhook in a Supabase Edge Function that says \"No signatures found matching the expected signature\" has one of two causes. Never stop checking.","2026-10-29","\u002Fblog\u002Fstripe-webhook-no-signatures-found\u002Fcard-800x500.png",{"path":695,"title":696,"description":697,"published":698,"category":586,"image":699,"draft":590},"\u002Fblog\u002Fsupabase-invalid-login","\"Invalid login credentials\" in Supabase: the three causes","Supabase says \"Invalid login credentials\" for a wrong password, an unknown email and a Google account. How to tell which, and why it is vague.","2026-10-28","\u002Fblog\u002Fsupabase-invalid-login\u002Fcard-800x500.png",{"path":255,"title":701,"description":702,"published":703,"category":586,"image":704,"draft":590},"\"Edge Function returned a non-2xx status code\" in Supabase","\"Edge Function returned a non-2xx status code\" means your Supabase function answered with an error. Here is where to read the real one.","2026-10-27","\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code\u002Fcard-800x500.png",{"path":706,"title":707,"description":708,"published":709,"category":586,"image":710,"draft":590},"\u002Fblog\u002Fcertificate-not-trusted","Certificate not trusted: the three causes besides expiry","Certificate not trusted, and the date is fine? It names another address, it signed itself, or its chain is missing a link. How to tell which.","2026-10-26","\u002Fblog\u002Fcertificate-not-trusted\u002Fcard-800x500.png",{"path":712,"title":713,"description":714,"published":715,"category":586,"image":716,"draft":590},"\u002Fblog\u002Finvalid-input-syntax-for-type-uuid","Supabase \"invalid input syntax for type uuid\": read the quotes","Supabase \"invalid input syntax for type uuid\" means your app sent something that is not an id. Read the quotes, hold the query, keep the column.","2026-10-25","\u002Fblog\u002Finvalid-input-syntax-for-type-uuid\u002Fcard-800x500.png",{"path":718,"title":719,"description":720,"published":721,"category":586,"image":722,"draft":590},"\u002Fblog\u002Fduplicate-key-value-violates-unique-constraint","Supabase \"duplicate key value violates unique constraint\", explained","Supabase \"duplicate key value violates unique constraint\" means the value is already taken. Find the column, pick a fix, and keep the value off screen.","2026-10-24","\u002Fblog\u002Fduplicate-key-value-violates-unique-constraint\u002Fcard-800x500.png",{"path":724,"title":725,"description":726,"published":727,"category":586,"image":728,"draft":590},"\u002Fblog\u002Fsupabase-relation-does-not-exist","Supabase \"relation does not exist\" when the table is right there","Supabase \"relation does not exist\" or PGRST205 means no table matches the name and schema your query used. Four checks, and what exposing a schema opens.","2026-10-23","\u002Fblog\u002Fsupabase-relation-does-not-exist\u002Fcard-800x500.png",{"path":730,"title":731,"description":732,"published":733,"category":586,"image":734,"draft":590},"\u002Fblog\u002Fsupabase-function-not-found","Supabase PGRST202: \"Could not find the function in the schema cache\"","Supabase \"Could not find the function in the schema cache\" lists the argument names your app sent. Compare them with the function first.","2026-10-22","\u002Fblog\u002Fsupabase-function-not-found\u002Fcard-800x500.png",{"path":736,"title":737,"description":738,"published":739,"category":586,"image":740,"draft":590},"\u002Fblog\u002Fsupabase-schema-cache-column-error","Supabase PGRST204: \"Could not find the column in the schema cache\"","Supabase \"Could not find the column in the schema cache\" usually means a name mismatch. Four checks in order, and the one-line reload.","2026-10-21","\u002Fblog\u002Fsupabase-schema-cache-column-error\u002Fcard-800x500.png",{"path":742,"title":743,"description":744,"published":745,"category":586,"image":746,"draft":590},"\u002Fblog\u002Fsupabase-email-rate-limit-exceeded","Supabase \"Email Rate Limit Exceeded\": two limits, one error code","Supabase \"Email Rate Limit Exceeded\" caps every email your project sends: 2 an hour on the built-in sender. What it counts and how to lift it.","2026-10-20","\u002Fblog\u002Fsupabase-email-rate-limit-exceeded\u002Fcard-800x500.png",{"path":566,"title":748,"description":749,"published":750,"category":586,"image":751,"draft":590},"Supabase \"Invalid Refresh Token: Refresh Token Not Found\": 3 causes","Supabase \"Invalid Refresh Token: Refresh Token Not Found\" logs your users out. Three causes, and how the auth log tells them apart.","2026-10-19","\u002Fblog\u002Fsupabase-users-logged-out\u002Fcard-800x500.png",{"path":753,"title":754,"description":755,"published":756,"category":586,"image":757,"draft":590},"\u002Fblog\u002Fpermission-denied-for-schema-public","Supabase \"permission denied for schema public\": three causes","Supabase \"permission denied for schema public\" means a missing schema grant. What removed it, and the line that puts it back.","2026-10-18","\u002Fblog\u002Fpermission-denied-for-schema-public\u002Fcard-800x500.png",{"path":759,"title":760,"description":761,"published":762,"category":586,"image":763,"draft":590},"\u002Fblog\u002Fsupabase-bucket-not-found","Supabase \"Bucket not found\": the three things it means","Supabase \"Bucket not found\" is one of three things: a public link to a private bucket, a name that is not an exact match, or the wrong project.","2026-10-17","\u002Fblog\u002Fsupabase-bucket-not-found\u002Fcard-800x500.png",{"path":765,"title":766,"description":767,"published":768,"category":586,"image":769,"draft":590},"\u002Fblog\u002Fsupabase-invalid-jwt","Supabase invalid JWT: which key stopped working?","A Supabase invalid JWT error is PGRST301, and it means a signed token failed verification. On a newer project that token is your user, not your API key.","2026-10-16","\u002Fblog\u002Fsupabase-invalid-jwt\u002Fcard-800x500.png",{"path":771,"title":772,"description":773,"published":774,"category":586,"image":775,"draft":590},"\u002Fblog\u002Fsupabase-single-row-error","Supabase \"multiple (or no) rows returned\" usually means no rows","Supabase returns PGRST116, \"JSON object requested, multiple (or no) rows returned\", when your query found none. A row your rules hide looks missing.","2026-10-15","\u002Fblog\u002Fsupabase-single-row-error\u002Fcard-800x500.png",{"path":777,"title":778,"description":779,"published":780,"category":586,"image":781,"draft":590},"\u002Fblog\u002Fdatabase-error-saving-new-user","\"Database error saving new user\" in Supabase, and where to look","\"Database error saving new user\" means something attached to your Supabase signup failed and it was all rolled back. The real error is in your logs.","2026-10-14","\u002Fblog\u002Fdatabase-error-saving-new-user\u002Fcard-800x500.png",{"path":783,"title":784,"description":785,"published":786,"category":586,"image":787,"draft":590},"\u002Fblog\u002Fwhat-is-supabase","What is Supabase? The database your builder picked for you","What is Supabase: the database, login and file storage behind your app. Supabase runs the servers; the rules about who reads your rows are yours.","2026-10-13","\u002Fblog\u002Fwhat-is-supabase\u002Fcard-800x500.png",{"path":789,"title":790,"description":791,"published":792,"category":586,"image":793,"draft":590},"\u002Fblog\u002Faws-access-key-exposed-in-frontend","An AWS access key exposed in your frontend is not like an OpenAI key","An AWS access key exposed in your frontend reads and writes your storage. The fix is usually a presigned URL rather than a new key.","2026-10-12","\u002Fblog\u002Faws-access-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":795,"title":796,"description":797,"published":798,"category":586,"image":799,"draft":590},"\u002Fblog\u002Fstorage-upload-violates-row-level-security","\"Row-level security policy for table objects\" on upload","\"New row violates row-level security policy for table objects\" means your upload has no insert rule. Making the bucket public does not add one.","2026-10-11","\u002Fblog\u002Fstorage-upload-violates-row-level-security\u002Fcard-800x500.png",{"path":801,"title":802,"description":803,"published":804,"category":586,"image":805,"draft":590},"\u002Fblog\u002Fbase44-security-scan","Base44 security scan: the one thing only it can see","The Base44 security scan checks seven kinds of problem from inside your app. Here is the half it reads that nothing outside can, and the half it never looks at.","2026-10-10","\u002Fblog\u002Fbase44-security-scan\u002Fcard-800x500.png",{"path":807,"title":808,"description":809,"published":810,"category":586,"image":811,"draft":590},"\u002Fblog\u002Fapi-key-leaked-what-to-do","Your API key leaked. Here is the order to do things in","An API key leaked and you want to know what to do first. Not every key in your frontend is one, and the order matters more than the speed.","2026-10-09","\u002Fblog\u002Fapi-key-leaked-what-to-do\u002Fcard-800x500.png",{"path":813,"title":814,"description":815,"published":816,"category":586,"image":817,"draft":590},"\u002Fblog\u002Finfinite-recursion-in-policy-for-relation","\"Infinite recursion detected in policy\" without disabling RLS","\"Infinite recursion detected in policy for relation\" means your Supabase policy asked the table it protects. Here is how to break the circle.","2026-10-08","\u002Fblog\u002Finfinite-recursion-in-policy-for-relation\u002Fcard-800x500.png",{"path":819,"title":820,"description":821,"published":822,"category":586,"image":823,"draft":590},"\u002Fblog\u002Fno-api-key-found-in-request","\"No API key found in request\" in Supabase, and the wrong fix","\"No API key found in request\" means your Supabase request arrived without a key. Most answers you find point at your database rules instead.","2026-10-07","\u002Fblog\u002Fno-api-key-found-in-request\u002Fcard-800x500.png",{"path":825,"title":826,"description":827,"published":828,"category":586,"image":829,"draft":590},"\u002Fblog\u002Fis-base44-safe","Is Base44 safe? What 5,442 live Base44 apps showed","Is Base44 safe? We ran nine checks on 5,442 live Base44 apps. Almost all scored B for reasons the owner never chose, and one question nobody can answer.","2026-10-06","\u002Fblog\u002Fis-base44-safe\u002Fcard-800x500.png",{"path":391,"title":831,"description":832,"published":833,"category":586,"image":834,"draft":590},"Hide an API key: move it to a Supabase Edge Function","Hiding an API key means moving it off the browser, and a Supabase Edge Function is the smallest place to put it. Two steps around the move matter more.","2026-10-05","\u002Fblog\u002Fmove-a-secret-to-an-edge-function\u002Fcard-800x500.png",{"path":836,"title":837,"description":838,"published":839,"category":586,"image":840,"draft":590},"\u002Fblog\u002Fenv-file-exposed-on-your-server","Is your .env file exposed? The twelve paths to check","Is your .env file exposed on your own web server? Twelve addresses tell you in a minute, and a hit means everything in the file is already public.","2026-10-04","\u002Fblog\u002Fenv-file-exposed-on-your-server\u002Fcard-800x500.png",{"path":842,"title":843,"description":844,"published":845,"category":586,"image":846,"draft":590},"\u002Fblog\u002Fis-v0-safe","v0 security: all 1,790 v0 apps we scanned got an A","v0 security, measured on 1,790 live v0 apps: every one graded A. Only 17 named a database, and that is most of what the A is measuring.","2026-10-03","\u002Fblog\u002Fis-v0-safe\u002Fcard-800x500.png",{"path":848,"title":849,"description":850,"published":851,"category":586,"image":852,"draft":590},"\u002Fblog\u002Fis-bolt-safe","Is Bolt safe? What 1,123 live Bolt apps showed","Is Bolt safe? We ran nine checks on 1,123 live Bolt apps. The hosting came back clean. The findings were API keys and open tables inside the apps.","2026-10-02","\u002Fblog\u002Fis-bolt-safe\u002Fcard-800x500.png",{"path":854,"title":855,"description":856,"published":857,"category":586,"image":858,"draft":590},"\u002Fblog\u002Fis-supabase-down-or-your-app","Is Supabase down, or is it your app? How to tell","Is Supabase down, or is it your app? A paused project, a full database and a bug of your own all look like an outage. Four checks tell them apart.","2026-10-01","\u002Fblog\u002Fis-supabase-down-or-your-app\u002Fcard-800x500.png",{"path":860,"title":861,"description":862,"published":863,"category":586,"image":864,"draft":590},"\u002Fblog\u002Fdoes-supabase-encrypt-my-data","Does Supabase encrypt my data? Yes. Here is what it stops","Does Supabase encrypt data? Yes: AES-256 at rest, TLS in transit, SOC 2 and ISO 27001 audited. What each one covers, and the leak none of them stops.","2026-09-30","\u002Fblog\u002Fdoes-supabase-encrypt-my-data\u002Fcard-800x500.png",{"path":866,"title":867,"description":868,"published":869,"category":586,"image":870,"draft":590},"\u002Fblog\u002Fsupabase-free-plan-limits","Supabase free plan limits, and what happens at each one","The Supabase free plan limits you to 500 MB of database and 5 GB of egress, with no backups. What happens as you cross each line, and what $25 changes.","2026-09-29","\u002Fblog\u002Fsupabase-free-plan-limits\u002Fcard-800x500.png",{"path":872,"title":873,"description":874,"published":875,"category":686,"image":876,"draft":590},"\u002Fblog\u002Ftest-your-supabase-backup","Test your Supabase backup before the day you need it","How to test your Supabase backup: restore it into a spare project, compare the row counts, sign in, and check for the line a cut-off file is missing.","2026-09-28","\u002Fblog\u002Ftest-your-supabase-backup\u002Fcard-800x500.png",{"path":878,"title":879,"description":880,"published":881,"category":686,"image":882,"draft":590},"\u002Fblog\u002Fsupabase-backup-github-action","Free Supabase backup with a GitHub Action, and the catch","A Supabase backup GitHub Action costs nothing and suits a lot of apps. The workflow, the connection string that works on GitHub, and the egress each run uses.","2026-09-27","\u002Fblog\u002Fsupabase-backup-github-action\u002Fcard-800x500.png",{"path":884,"title":885,"description":886,"published":887,"category":686,"image":888,"draft":590},"\u002Fblog\u002Fdownload-your-supabase-backup","Why you can't download your Supabase backup","You can't download your Supabase backup on a current project, because the daily copy is a physical snapshot. How to tell, and how to hold a copy of your own.","2026-09-26","\u002Fblog\u002Fdownload-your-supabase-backup\u002Fcard-800x500.png",{"path":890,"title":891,"description":892,"published":887,"category":586,"image":893,"draft":590},"\u002Fblog\u002Fsupabase-permission-denied-for-table","Supabase \"permission denied for table\": the missing grant","From October 30, a new Supabase table answers \"permission denied for table\" until you grant access. The grant the email shows is half the fix.","\u002Fblog\u002Fsupabase-permission-denied-for-table\u002Fcard-800x500.png",{"path":895,"title":896,"description":897,"published":898,"category":586,"image":899,"draft":590},"\u002Fblog\u002Fopen-api-endpoint-exposed","Is an open API endpoint a security problem? Look at the JSON","Your scan flagged an open API endpoint. Whether it matters depends on what came back, and most of the ones we found were the platform's own.","2026-09-25","\u002Fblog\u002Fopen-api-endpoint-exposed\u002Fcard-800x500.png",{"path":901,"title":902,"description":903,"published":904,"category":586,"image":905,"draft":590},"\u002Fblog\u002Flovable-security-scan","Lovable security scan: the one thing it cannot prove","Lovable security scan: what the Quick and Deep scans check, when each one runs, and the one thing no scan from inside your project can prove.","2026-09-24","\u002Fblog\u002Flovable-security-scan\u002Fcard-800x500.png",{"path":907,"title":908,"description":909,"published":910,"category":686,"image":911,"draft":590},"\u002Fblog\u002Fsupabase-backup-auth-users","Why your Supabase dump has no users in it","Run supabase db dump on its own and you get the shape of your database and none of its rows, with the auth schema your users live in left out entirely.","2026-09-23","\u002Fblog\u002Fsupabase-backup-auth-users\u002Fcard-800x500.png",{"path":913,"title":914,"description":915,"published":916,"category":586,"image":917,"draft":590},"\u002Fblog\u002Fdomain-and-certificate-expiry","Domain expired, website down: what actually happens next","Your domain expired and your website is down. Here is the clock you are on, why a lapsed certificate is the easier of the two, and how to check both.","2026-09-22","\u002Fblog\u002Fdomain-and-certificate-expiry\u002Fcard-800x500.png",{"path":919,"title":920,"description":921,"published":922,"category":586,"image":923,"draft":590},"\u002Fblog\u002Fis-lovable-safe","Is Lovable safe? What 18,554 live Lovable apps showed","Is Lovable safe? We ran nine checks on 18,554 live Lovable apps. The platform was the cleanest of five builders. Every finding was inside the app itself.","2026-09-21","\u002Fblog\u002Fis-lovable-safe\u002Fcard-800x500.png",{"path":925,"title":926,"description":927,"published":928,"category":586,"image":929,"draft":590},"\u002Fblog\u002Fvibe-coded-app-security-checklist","The vibe coding security checklist, in nine checks","A vibe coding security checklist with nine items, each one something anyone can verify about your live app from outside, and each with a one-line test.","2026-09-20","\u002Fblog\u002Fvibe-coded-app-security-checklist\u002Fcard-800x500.png",{"path":931,"title":932,"description":933,"published":934,"category":586,"image":935,"draft":590},"\u002Fblog\u002Fstripe-secret-key-in-frontend","A Stripe secret key exposed in your frontend can move money","A Stripe secret key exposed in your frontend can refund, charge and read every customer record you hold. Your pk_live_ key is meant to be there.","2026-09-19","\u002Fblog\u002Fstripe-secret-key-in-frontend\u002Fcard-800x500.png",{"path":937,"title":938,"description":939,"published":940,"category":586,"image":941,"draft":590},"\u002Fblog\u002Fvite-and-next-public-env-vars","Vite env variables exposed: VITE_ and NEXT_PUBLIC_ mean publish this","Vite env variables exposed in your app did what the prefix asked. VITE_ and NEXT_PUBLIC_ mean publish this, and the AI that added one never knew the cost.","2026-09-18","\u002Fblog\u002Fvite-and-next-public-env-vars\u002Fcard-800x500.png",{"path":943,"title":944,"description":945,"published":946,"category":586,"image":947,"draft":590},"\u002Fblog\u002Fbase44-source-maps","Base44 security: what a scan flags, and what is yours to fix","Base44 security on 5,438 scanned apps: three findings on nearly every one are the platform's, the source map is Base44's badge, and what is yours is short.","2026-09-17","\u002Fblog\u002Fbase44-source-maps\u002Fcard-800x500.png",{"path":949,"title":950,"description":951,"published":952,"category":586,"image":953,"draft":590},"\u002Fblog\u002Fis-cursor-ai-safe","Is Cursor AI safe? The editor, the code, and the app you shipped","Is Cursor AI safe? Three questions in one search: what Cursor keeps, what the code it writes gets wrong, and whether the app you shipped is open.","2026-09-16","\u002Fblog\u002Fis-cursor-ai-safe\u002Fcard-800x500.png",{"path":955,"title":956,"description":957,"published":958,"category":586,"image":959,"draft":590},"\u002Fblog\u002Fis-replit-safe","Is Replit safe? What we found in 3,042 live Replit apps","Is Replit safe? We ran nine external checks on 3,042 live Replit apps. The host was not where the findings were. The app each owner published was.","2026-09-15","\u002Fblog\u002Fis-replit-safe\u002Fcard-800x500.png",{"path":961,"title":962,"description":963,"published":964,"category":686,"image":965,"draft":590},"\u002Fblog\u002Fsupabase-storage-backup","Supabase storage backup: why your database copy has no files","A Supabase storage backup is a separate job. Database backups keep the list of your files and none of the files, so a restore leaves every upload broken.","2026-09-14","\u002Fblog\u002Fsupabase-storage-backup\u002Fcard-800x500.png",{"path":967,"title":968,"description":969,"published":970,"category":686,"image":971,"draft":590},"\u002Fblog\u002Fsupabase-point-in-time-recovery","Supabase point-in-time recovery: what it costs, what it misses","Supabase point-in-time recovery rewinds your database to any second in the last week. It costs $100 a month on top of Pro, and it covers your database only.","2026-09-13","\u002Fblog\u002Fsupabase-point-in-time-recovery\u002Fcard-800x500.png",{"path":973,"title":974,"description":975,"published":976,"category":686,"image":977,"draft":590},"\u002Fblog\u002Fsupabase-project-paused-recover","Supabase project paused? Your data is still there","Supabase paused your project after a week of inactivity. Nothing is deleted, Restore sits beside the project name, and you have a year before that changes.","2026-09-12","\u002Fblog\u002Fsupabase-project-paused-recover\u002Fcard-800x500.png",{"path":979,"title":980,"description":981,"published":982,"category":586,"image":983,"draft":590},"\u002Fblog\u002Fsafest-ai-app-builder","Which AI app builder is safest? We scanned 30,998 apps","Which AI app builder is safest? We scanned 30,998 live apps from Lovable, Base44, Replit, v0 and Bolt. The builder is not what decides your grade.","2026-09-11","\u002Fblog\u002Fsafest-ai-app-builder\u002Fcard-800x500.png",{"path":985,"title":986,"description":987,"published":988,"category":586,"image":989,"draft":590},"\u002Fblog\u002Fenable-rls-on-every-supabase-table","Enable Row Level Security on every Supabase table, then prove it","Enabling Row Level Security in Supabase with no policy locks a table completely. A policy without the setting does nothing. Here is the SQL, and the test.","2026-09-10","\u002Fblog\u002Fenable-rls-on-every-supabase-table\u002Fcard-800x500.png",{"path":991,"title":992,"description":993,"published":994,"category":586,"image":995,"draft":590},"\u002Fblog\u002Fsupabase-rls-disabled-in-public","Supabase \"RLS disabled in public\": what the warning misses","Supabase reports \"RLS disabled in public\" as an error. It says nothing about the read policy that leaves your table just as open to strangers.","2026-09-09","\u002Fblog\u002Fsupabase-rls-disabled-in-public\u002Fcard-800x500.png",{"path":451,"title":997,"description":998,"published":999,"category":586,"image":1000,"draft":590},"How to rotate a leaked Supabase service_role key","Supabase says fix the leak first. Other guides say rotate now. Which is right depends on where your service_role key leaked.","2026-09-08","\u002Fblog\u002Frotate-supabase-service-role-key\u002Fcard-800x500.png",{"path":1002,"title":1003,"description":1004,"published":1005,"category":586,"image":1006,"draft":590},"\u002Fblog\u002Fvibe-coding-security-scanners-compared","Vibe coding security scanners compared, including ours","The best vibe coding security scanner comes down to three questions no feature list answers. Eight tools compared, with prices, and the jobs Reeve does not do.","2026-09-07","\u002Fblog\u002Fvibe-coding-security-scanners-compared\u002Fcard-800x500.png",{"path":1008,"title":1009,"description":1010,"published":1011,"category":586,"image":1012,"draft":590},"\u002Fblog\u002Fsupabase-security-checker","Supabase security checker: run the five checks yourself","A Supabase security checker reads your published app instead of your project settings. Here are the five checks it runs, and how to run each one yourself.","2026-09-06","\u002Fblog\u002Fsupabase-security-checker\u002Fcard-800x500.png",{"path":1014,"title":1015,"description":1016,"published":1017,"category":586,"image":1018,"draft":590},"\u002Fblog\u002Fvibe-coding-security-scanner","Vibe coding security scanner: what a URL scan misses","A vibe coding security scanner reads your live app from outside. Here is what that covers, the four things it cannot see, and how to read the result.","2026-09-05","\u002Fblog\u002Fvibe-coding-security-scanner\u002Fcard-800x500.png",{"path":1020,"title":1021,"description":1022,"published":1023,"category":586,"image":1024,"draft":590},"\u002Fblog\u002Fmissing-security-headers","Missing security headers: when it actually matters","Missing security headers is the finding our scanner prints most. Here is what it protects against, and when it is the least urgent line on your report.","2026-09-04","\u002Fblog\u002Fmissing-security-headers\u002Fcard-800x500.png",{"path":1026,"title":1027,"description":1028,"published":1029,"category":586,"image":1030,"draft":590},"\u002Fblog\u002Fopenai-api-key-exposed-in-frontend","Your OpenAI API key is exposed in your frontend. Rotate it.","An OpenAI API key exposed in your frontend cannot be locked to a domain. Rotate it today, move the call behind your own endpoint, and cap the spend.","2026-09-03","\u002Fblog\u002Fopenai-api-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":1032,"title":1033,"description":1034,"published":1035,"category":586,"image":1036,"draft":590},"\u002Fblog\u002Fwhat-secrets-leak-from-vibe-coded-apps","An API key exposed in your frontend: what 30,998 apps shipped","An API key exposed in your frontend is usually a Google Maps key. We scanned 30,998 live vibe-coded apps and counted which secrets actually leak.","2026-09-02","\u002Fblog\u002Fwhat-secrets-leak-from-vibe-coded-apps\u002Fcard-800x500.png",{"path":1038,"title":1039,"description":1040,"published":1041,"category":686,"image":1042,"draft":590},"\u002Fblog\u002Fsupabase-backup-tools-compared","Supabase backup tools compared, including ours","Four kinds of Supabase backup tool, what each one actually copies, and the case where a free GitHub Action beats paying anyone, us included.","2026-09-01","\u002Fblog\u002Fsupabase-backup-tools-compared\u002Fcard-800x500.png",{"path":1044,"title":1045,"description":1046,"published":1047,"category":586,"image":1048,"draft":590},"\u002Fblog\u002Freplit-secrets-explained","How to use secrets in Replit, and what still gets published","How to use secrets in Replit: add one, read it back, and fix the two reasons it comes back undefined. Plus the keys the Secrets tool cannot keep private.","2026-08-31","\u002Fblog\u002Freplit-secrets-explained\u002Fcard-800x500.png",{"path":1050,"title":1051,"description":1052,"published":1053,"category":686,"image":1054,"draft":590},"\u002Fblog\u002Fback-up-supabase-free-tier","Supabase free tier backups: how to make one without a terminal","There are no Supabase free tier backups, so the copy has to come from you. How to make one from the dashboard, and what CSV leaves out.","2026-08-30","\u002Fblog\u002Fback-up-supabase-free-tier\u002Fcard-800x500.png",{"path":1056,"title":1057,"description":1058,"published":1059,"category":586,"image":1060,"draft":590},"\u002Fblog\u002Fis-supabase-secure","Is Supabase secure? Yes. Your project is a separate question","Is Supabase secure? The platform is audited, encrypted and pen-tested. Their own compliance documents say where that stops and your settings begin.","2026-08-29","\u002Fblog\u002Fis-supabase-secure\u002Fcard-800x500.png",{"path":1062,"title":1063,"description":1064,"published":1065,"category":586,"image":1066,"draft":590},"\u002Fblog\u002Fwhere-to-find-supabase-api-keys","Where to find your Supabase API keys: anon, service_role and the URL","Your Supabase project URL, anon key and service_role key are on one dashboard page. Here is where that page is, and which of the four belongs in your app.","2026-08-28","\u002Fblog\u002Fwhere-to-find-supabase-api-keys\u002Fcard-800x500.png",{"path":1068,"title":1069,"description":1070,"published":1071,"category":586,"image":1072,"draft":590},"\u002Fblog\u002Fnew-row-violates-row-level-security-policy","New row violates row-level security policy in Supabase. Now what?","\"New row violates row-level security policy\" means Supabase refused a write. The fix that clears it in ten seconds also reopens the table to everyone.","2026-08-27","\u002Fblog\u002Fnew-row-violates-row-level-security-policy\u002Fcard-800x500.png",{"path":1074,"title":1075,"description":1076,"published":1077,"category":586,"image":1078,"draft":590},"\u002Fblog\u002Fcors-wildcard-security-risk","Is a CORS wildcard a security risk? Usually not.","Is a CORS wildcard a security risk? Usually it is your builder default, and it gives away nothing your server was not already handing to anyone who asked.","2026-08-26","\u002Fblog\u002Fcors-wildcard-security-risk\u002Fcard-800x500.png",{"path":1080,"title":1081,"description":1082,"published":1083,"category":686,"image":1084,"draft":590},"\u002Fblog\u002Fsupabase-branching-is-not-a-backup","Supabase branching is not a backup. It only goes forwards.","Supabase branching is not a backup: a branch starts with none of your data, and merging only moves schema. What it is for, and what to use instead.","2026-08-25","\u002Fblog\u002Fsupabase-branching-is-not-a-backup\u002Fcard-800x500.png",{"path":1086,"title":1087,"description":1088,"published":1089,"category":686,"image":1090,"draft":590},"\u002Fblog\u002Fhow-to-restore-a-supabase-backup","How to restore a Supabase backup, and what breaks after","How to restore a Supabase backup from the dashboard or from a dump file, what the restore replaces, and why your app can still be broken when it finishes.","2026-08-24","\u002Fblog\u002Fhow-to-restore-a-supabase-backup\u002Fcard-800x500.png",{"path":1092,"title":1093,"description":1094,"published":1095,"category":586,"image":1096,"draft":590},"\u002Fblog\u002Fsupabase-storage-bucket-public","Your Supabase storage bucket is public. Is that a problem?","A public Supabase storage bucket means anyone with a file URL can open it. It does not mean anyone can list what is in there. Two different settings.","2026-08-23","\u002Fblog\u002Fsupabase-storage-bucket-public\u002Fcard-800x500.png",{"path":1098,"title":1099,"description":1100,"published":1101,"category":586,"image":1102,"draft":590},"\u002Fblog\u002Fgoogle-api-key-exposed-in-frontend","Is a Google API key exposed in your frontend a problem?","A Google API key exposed in your frontend is the key our scanner finds most often, and usually it is fine. One free setting decides which it is.","2026-08-22","\u002Fblog\u002Fgoogle-api-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":1104,"title":1105,"description":1106,"published":1107,"category":686,"image":1108,"draft":590},"\u002Fblog\u002Fai-agent-deleted-my-database","An AI agent deleted my Supabase data. What can I recover?","An AI agent deleted your database data. What you can recover was decided before it ran, and the next few minutes decide how much of it survives.","2026-08-21","\u002Fblog\u002Fai-agent-deleted-my-database\u002Fcard-800x500.png",{"path":1110,"title":1111,"description":1112,"published":1113,"category":586,"image":1114,"draft":590},"\u002Fblog\u002Fcan-anyone-read-your-supabase-database","Can anyone read your Supabase database? We checked 3,680 apps","Can anyone read your Supabase database without logging in? We scanned 30,998 live apps built with AI builders and measured how often the answer is yes.","2026-08-18","\u002Fblog\u002Fcan-anyone-read-your-supabase-database\u002Fcard-800x500.png",{"path":1116,"title":1117,"description":1118,"published":1113,"category":586,"image":1119,"draft":590},"\u002Fblog\u002Fsource-maps-exposed-in-production","Source maps exposed: your app is publishing its original code","An exposed source map lets anyone read your app's original code, comments included. The 30-second check, and what actually matters if yours are public.","\u002Fblog\u002Fsource-maps-exposed-in-production\u002Fcard-800x500.png",{"path":1121,"title":1122,"description":1123,"published":1124,"category":586,"image":1125,"draft":590},"\u002Fblog\u002Fsupabase-new-api-keys","Supabase publishable key: is it the same as the anon key?","Supabase replaced anon and service_role with publishable and secret keys. Which one belongs in your app, and which never does?","2026-08-12","\u002Fblog\u002Fsupabase-new-api-keys\u002Fcard-800x500.png",{"path":1127,"title":1128,"description":1129,"published":1130,"category":686,"image":1131,"draft":590},"\u002Fblog\u002Fdoes-supabase-back-up-my-database","Does Supabase back up my database? It depends on your plan.","Does Supabase back up your database? Daily on paid plans, and not at all on the free one. How to check which you have, and what that copy cannot survive.","2026-08-11","\u002Fblog\u002Fdoes-supabase-back-up-my-database\u002Fcard-800x500.png",{"path":1133,"title":1134,"description":1135,"published":1136,"category":586,"image":1137,"draft":590},"\u002Fblog\u002Fsupabase-rls-on-but-table-still-public","Supabase Row Level Security is on. Your table is still public.","Turning on Supabase Row Level Security does not protect a table. Your policies do, and the policy that fixed your broken app may let everyone in.","2026-08-10","\u002Fblog\u002Fsupabase-rls-on-but-table-still-public\u002Fcard-800x500.png",{"path":1139,"title":1140,"description":1141,"published":1136,"category":686,"image":1142,"draft":590},"\u002Fblog\u002Fversion-history-is-not-a-backup","Version history is not a backup. It cannot undo a deleted table.","Lovable and Bolt keep version history for your code. Your database is a separate service, so rolling back to this morning does not bring your data back.","\u002Fblog\u002Fversion-history-is-not-a-backup\u002Fcard-800x500.png",{"path":1144,"title":1145,"description":1146,"published":1147,"category":686,"image":1148,"draft":590},"\u002Fblog\u002Fthree-ways-to-back-up-a-supabase-database","Three ways to back up a Supabase database, and what each misses","The dashboard, pg_dump, and a managed service. What each one actually saves, what it quietly leaves out, and which one survives losing the account.","2026-08-09","\u002Fblog\u002Fthree-ways-to-back-up-a-supabase-database\u002Fcard-800x500.png",{"path":1150,"title":1151,"description":1152,"published":1147,"category":586,"image":1153,"draft":590},"\u002Fblog\u002Fwhich-api-keys-are-safe-in-your-frontend","Which API keys are safe in your frontend, and which aren't","Your Supabase anon key is supposed to be public. Your service_role key is not, and it ignores every rule you set. Here is how to tell them apart.","\u002Fblog\u002Fwhich-api-keys-are-safe-in-your-frontend\u002Fcard-800x500.png",1794213635058]