[{"data":1,"prerenderedAt":1367},["ShallowReactive",2],{"blog-en-max-client-connections-reached":3,"blog-index-en":759},{"id":4,"title":5,"body":6,"category":715,"cover":716,"coverAlt":717,"description":718,"draft":719,"extension":720,"faq":721,"image":737,"keywords":738,"meta":747,"navigation":748,"ogTitle":749,"path":750,"published":751,"seo":752,"stem":753,"tldr":754,"updated":751,"__hash__":758},"blog_en\u002Fblog\u002Fmax-client-connections-reached.md","Supabase \"max client connections reached\", explained",{"type":7,"value":8,"toc":702},"minimark",[9,13,24,27,33,40,43,48,51,66,69,73,76,171,182,185,192,214,218,221,224,231,237,240,252,258,262,265,268,276,279,344,362,377,381,384,405,408,453,459,467,474,489,495,501,516,522,526,529,532,535,542,547,551,561,571,587,595,599,602,611,628,637,654,658,694],[10,11,12],"p",{},"Your app has been fine for weeks. Then something brings a crowd, a launch or a\npost that got shared, and the pages that read from your database start showing\nan error while the home page still loads. In your host's function logs there is\none line:",[14,15,20],"pre",{"className":16,"code":18,"language":19},[17],"language-text","(EMAXCONN) max client connections reached, limit: 200\n","text",[21,22,18],"code",{"__ignoreMap":23},"",[10,25,26],{},"Or, on an app that connects in session mode, this one:",[14,28,31],{"className":29,"code":30,"language":19},[17],"(EMAXCONNSESSION) max clients reached in session mode - max clients are limited to pool_size: 15\n",[21,32,30],{"__ignoreMap":23},[10,34,35,36,39],{},"You meet this on an app with a server of its own: a Next.js app from v0, Cursor\nor Claude Code that reads the database through Prisma or Drizzle, a Replit app\nwith an Express server, an Edge Function that opens its own Postgres\nconnection. A page that only calls ",[21,37,38],{},"supabase.from(…)"," goes through the Data API\ninstead, which keeps connections of its own.",[10,41,42],{},"The advice you will find first for \"max client connections reached\" on\nSupabase, including at the end of Supabase's own help article for the Postgres\nversion of this error, is to move to a bigger compute size. For a busy app that\nis sometimes right. On the Free plan the fix can be a port number. Before you\npay for anything, read which of the two messages you got and which port your\nconnection string uses. The two limits are set by different things, and only\none of them moves with the price.",[44,45,47],"h2",{"id":46},"what-does-max-client-connections-reached-mean-on-supabase","What does \"max client connections reached\" mean on Supabase?",[10,49,50],{},"Supavisor, the connection pooler that sits between your app and your Supabase\ndatabase, already has as many clients connected as it allows, and it turned the\nnext one away.",[10,52,53,54,57,58,61,62,65],{},"A client here is one open connection from your code: one database client in one\nrunning copy of your server. The message is Supavisor's own, from the file\n",[21,55,56],{},"max_connections_error.ex"," in its source, and it reaches your app as a Postgres\nerror with the severity ",[21,59,60],{},"FATAL"," and the code ",[21,63,64],{},"XX000",". Libraries print that\nwrapping in different ways, but the words are the ones above.",[10,67,68],{},"Picture your database as a kitchen with a counter and a fixed number of stools.\nEach stool is a connection to Postgres, the database inside your Supabase\nproject, and a request for data needs a stool for as long as its order takes.\nSupavisor is the host at the door. It decides who sits where, and it keeps a\nwaiting area for people who have come in and are not eating yet. The message\nmeans the host's list is full.",[44,70,72],{"id":71},"which-limit-did-you-hit","Which limit did you hit?",[10,74,75],{},"The words of the error tell you, and so does the port at the end of your\nconnection string.",[77,78,79,98],"table",{},[80,81,82],"thead",{},[83,84,85,89,92,95],"tr",{},[86,87,88],"th",{},"What you see",[86,90,91],{},"Who sent it",[86,93,94],{},"What it counts",[86,96,97],{},"On the Free plan",[99,100,101,121,141,157],"tbody",{},[83,102,103,109,115,118],{},[104,105,106],"td",{},[21,107,108],{},"(EMAXCONN) max client connections reached, limit: …",[104,110,111,112],{},"Supavisor in transaction mode, port ",[21,113,114],{},"6543",[104,116,117],{},"clients connected to the pooler at once",[104,119,120],{},"200",[83,122,123,128,135,138],{},[104,124,125],{},[21,126,127],{},"(EMAXCONNSESSION) max clients reached in session mode …",[104,129,130,131,134],{},"Supavisor in session mode, port ",[21,132,133],{},"5432"," on the pooler host",[104,136,137],{},"clients, capped at the pool size",[104,139,140],{},"15",[83,142,143,148,151,154],{},[104,144,145],{},[21,146,147],{},"remaining connection slots are reserved for roles with the SUPERUSER attribute",[104,149,150],{},"Postgres itself",[104,152,153],{},"connections to the database",[104,155,156],{},"60",[83,158,159,164,166,169],{},[104,160,161],{},[21,162,163],{},"sorry, too many clients already",[104,165,150],{},[104,167,168],{},"every connection, the reserved ones included",[104,170,156],{},[10,172,173,174,177,178,181],{},"The figures are from the table in Supabase's compute guide, for Nano, the size\nthe Free plan runs on. Micro, the smallest paid size, has the same three. The\ntwo Postgres messages come from Postgres's own source and carry the code\n",[21,175,176],{},"53300","; Postgres 15 words the first of them ",[21,179,180],{},"remaining connection slots are reserved for non-replication superuser connections",".",[10,183,184],{},"In the kitchen, those last two rows are the stools themselves running out. The\nfirst two are the host refusing to let one more person through the door.",[10,186,187,188,191],{},"Your connection string says which door you came in by. It sits in your server's\nenvironment variables, often as ",[21,189,190],{},"DATABASE_URL",", and Supabase's guide to\nconnecting shows each kind:",[193,194,195,202,208],"ul",{},[196,197,198,201],"li",{},[21,199,200],{},"…@db.[PROJECT-REF].supabase.co:5432\u002Fpostgres"," is a direct connection, past\nthe host and straight to a stool.",[196,203,204,207],{},[21,205,206],{},"…@aws-[INDEX]-[REGION].pooler.supabase.com:5432\u002Fpostgres"," is the pooler in\nsession mode.",[196,209,210,213],{},[21,211,212],{},"…@aws-[INDEX]-[REGION].pooler.supabase.com:6543\u002Fpostgres"," is the pooler in\ntransaction mode.",[44,215,217],{"id":216},"why-does-a-supabase-app-run-out-of-connections","Why does a Supabase app run out of connections?",[10,219,220],{},"Because something opens connections faster than it gives them back, and\nserverless functions, in Supabase's own words, open many short-lived\nconnections.",[10,222,223],{},"A function on Vercel, Netlify or Supabase's own Edge Functions runs as many\ncopies of itself as traffic asks for, and each warm copy keeps its own database\nclient. Supabase's guide to connecting gives the arithmetic for Postgres.js,\none of the common Postgres libraries: it opens up to 10 connections per copy by\ndefault, and \"A few dozen instances is enough to exhaust the pool.\"",[10,225,226,230],{},[227,228,229],"strong",{},"Session mode runs out first."," The host gives you a stool and you keep it\nuntil you leave, eating or not. Supabase's FAQ on Supavisor says so directly:\n\"once the pooler assigns a direct connection, it stays with that client until\nvoluntarily surrendered.\" So the host can let in only as many people as it has\nstools for that connection string, which is why the session-mode message names\nthe pool size. Supavisor's source checks exactly that: in session mode a new\nclient is refused once the clients already connected reach the pool size. Fifteen\nstools, and the sixteenth client is turned away at the door however quiet the\nfirst fifteen are.",[10,232,233,236],{},[227,234,235],{},"Transaction mode lets far more people in."," The host seats you for one order,\na single transaction, and hands the stool to the next person as soon as it is\ndone, so 200 clients can share a handful of connections. It still has a waiting\narea of a fixed size, and a burst of function copies that each open several\nclients fills it.",[10,238,239],{},"Things outside your app hold stools too: a database tool such as TablePlus or\nDBeaver left open, an automation in n8n or Make with a Postgres step, your own\nlaptop running the app in development against the production string, a backup\njob. Each one is a client of whatever string it was given.",[10,241,242,243,246,247,181],{},"A slow query keeps its stool longer. If your logs also show\n",[21,244,245],{},"canceling statement due to statement timeout",", fix that query first, because\nevery second it runs is a second its stool is taken.\n",[248,249,251],"a",{"href":250},"\u002Fblog\u002Fcanceling-statement-due-to-statement-timeout","That error has its own walk-through",[253,254],"diagram",{"alt":255,"caption":256,"src":257},"Two doors into the same database. Through the 5432 door every client is joined to a connection of its own, the idle ones included, and the next client in line is crossed out because every connection is held. Through the 6543 door a crowd of clients waits on a few shared connections, and only the ones running a query are joined to one.","Session mode gives each client a connection until it leaves, so the pool size is also the client limit. Transaction mode lends connections out one transaction at a time.","\u002Fblog\u002Fmax-client-connections-reached\u002Ftwo-doors-1600x760.png",[44,259,261],{"id":260},"see-who-is-holding-the-connections","See who is holding the connections",[10,263,264],{},"Ask Postgres, then ask the dashboard. Postgres lists every connection it has\nopen, and Supabase's dashboard counts the pooler's clients.",[10,266,267],{},"In the SQL Editor, this counts the connections by the role and the app that\nopened them, and by what they are doing:",[14,269,274],{"className":270,"code":272,"language":273,"meta":23},[271],"language-sql","select usename, application_name, state, count(*)\nfrom pg_stat_activity\nwhere backend_type = 'client backend'\ngroup by usename, application_name, state\norder by count(*) desc;\n","sql",[21,275,272],{"__ignoreMap":23},[10,277,278],{},"The role tells you who it is. Supabase's guide to managing connections lists\nthem:",[77,280,281,291],{},[80,282,283],{},[83,284,285,288],{},[86,286,287],{},"Role",[86,289,290],{},"Who it is",[99,292,293,306,316,326,336],{},[83,294,295,300],{},[104,296,297],{},[21,298,299],{},"authenticator",[104,301,302,303,305],{},"the Data API, which every ",[21,304,38],{}," call goes through",[83,307,308,313],{},[104,309,310],{},[21,311,312],{},"supabase_auth_admin",[104,314,315],{},"Auth, the service that signs your users in",[83,317,318,323],{},[104,319,320],{},[21,321,322],{},"supabase_storage_admin",[104,324,325],{},"Storage",[83,327,328,333],{},[104,329,330],{},[21,331,332],{},"postgres",[104,334,335],{},"the dashboard and external tools, Prisma and psql included",[83,337,338,341],{},[104,339,340],{},"a role you created",[104,342,343],{},"whatever you gave that role's password to",[10,345,346,347,349,350,353,354,357,358,361],{},"A pile of ",[21,348,332],{}," connections in the ",[21,351,352],{},"idle"," state, with an\n",[21,355,356],{},"application_name"," you recognise, is a client sitting on a stool with nothing\nin front of it. ",[21,359,360],{},"idle in transaction"," is the state to look at first: the guide\nsays it \"almost always means the application forgot to commit or roll back\",\nand the session holds its locks for as long as it stays open.",[10,363,364,365,368,369,372,373,376],{},"For the pooler itself, open ",[227,366,367],{},"Observability"," in the dashboard. The report\n",[227,370,371],{},"Shared Pooler (Supavisor) Client Connections"," counts its clients over time.\nThe guide notes that these reports show the count as of their last refresh,\nand ",[21,374,375],{},"pg_stat_activity"," is the live view.",[44,378,380],{"id":379},"how-to-fix-max-client-connections-reached-on-supabase","How to fix \"max client connections reached\" on Supabase",[10,382,383],{},"Move serverless code to transaction mode, give each copy of it one connection,\nand keep session mode for the jobs that need a whole session. Do them in that\norder.",[10,385,386,389,390,393,394,397,398,401,402,181],{},[227,387,388],{},"1. Use the Transaction pooler for serverless functions."," In your Supabase\nproject, press ",[227,391,392],{},"Connect"," at the top of the page, choose ",[227,395,396],{},"Transaction\npooler",", and copy the string. It ends in ",[21,399,400],{},":6543\u002Fpostgres",". Put it in your\nserver's environment in place of the old one, with your database password where\nthe string says ",[21,403,404],{},"[YOUR-PASSWORD]",[10,406,407],{},"Transaction mode keeps nothing between transactions, so prepared statements\nhave to be turned off. Supabase's guide gives the setting per library:",[77,409,410,420],{},[80,411,412],{},[83,413,414,417],{},[86,415,416],{},"Library",[86,418,419],{},"Setting",[99,421,422,432,443],{},[83,423,424,427],{},[104,425,426],{},"Postgres.js, Drizzle",[104,428,429],{},[21,430,431],{},"prepare: false",[83,433,434,437],{},[104,435,436],{},"Prisma",[104,438,439,442],{},[21,440,441],{},"pgbouncer=true"," on the connection string",[83,444,445,448],{},[104,446,447],{},"asyncpg",[104,449,450],{},[21,451,452],{},"statement_cache_size=0",[10,454,455,458],{},[227,456,457],{},"2. Create the client once, with a pool of one."," A client created inside the\nrequest handler is a new connection for every request. Supabase's guide says to\ncreate it once at the top of the file, outside any handler, and to cap its pool\nat 1, because \"The client is shared by every invocation on that warm instance\":",[14,460,465],{"className":461,"code":463,"language":464,"meta":23},[462],"language-ts","import postgres from 'postgres'\n\nexport const sql = postgres(process.env.DATABASE_URL, {\n  max: 1,\n  prepare: false,\n  ssl: 'require',\n})\n","ts",[21,466,463],{"__ignoreMap":23},[10,468,469,470,473],{},"For Prisma the same advice is ",[21,471,472],{},"connection_limit=1"," on the connection string,\nfrom Supabase's Prisma troubleshooting guide. If you built the app with Cursor,\nClaude Code or v0, this is a short change to describe to it: the file that\ncreates the database client, the new string, and these two settings.",[10,475,476,479,480,483,484,488],{},[227,477,478],{},"3. Keep session mode for one long job."," A migration, a ",[21,481,482],{},"pg_dump",", a tool\nyou open by hand: each is a single session that wants to keep its stool.\nSupabase's guide sends those to a direct connection, or to session mode on a\nnetwork without IPv6, which is how\n",[248,485,487],{"href":486},"\u002Fblog\u002Fsupabase-backup-github-action","a backup running on GitHub's runners","\nconnects.",[10,490,491,494],{},[227,492,493],{},"4. Close what you left open."," Quit the database tool, stop the automation's\ntest runs, and take the production string out of your laptop. A connection you\ncannot close from its own end can be ended from the SQL Editor. This lists the\nones holding a transaction open:",[14,496,499],{"className":497,"code":498,"language":273,"meta":23},[271],"select pid, usename, application_name, query_start, query\nfrom pg_stat_activity\nwhere state = 'idle in transaction';\n",[21,500,498],{"__ignoreMap":23},[10,502,503,504,507,508,511,512,515],{},"Then ",[21,505,506],{},"select pg_terminate_backend(pid);"," with the ",[21,509,510],{},"pid"," from that list ends the\nsession. Postgres rolls back whatever its open transaction had written and not\ncommitted, so read its ",[21,513,514],{},"query"," column before you end it.",[10,517,518,521],{},[227,519,520],{},"5. Then look at the compute size."," If the clients are all real traffic,\nsharing connections as they should and still more than 200, the limit moves\nwith the size: Small allows 400 pooler clients and Medium 600, per Supabase's\ncompute table. Its knowledge base says the shared pooler's client limits \"are\nhard-coded and cannot be changed without upgrading the compute size\", and its\ncompute guide says a change usually comes with \"less than 2 minutes of\ndowntime\".",[44,523,525],{"id":524},"should-i-raise-the-pool-size","Should I raise the pool size?",[10,527,528],{},"Not to fix this. In transaction mode the pool size does not change the client\nlimit at all, and in either mode it decides how many of your database's own\nconnections the pooler may take.",[10,530,531],{},"The pool size is the number of stools the host may hand out, and the kitchen\nhas 60 on the Free plan. Supabase's FAQ defines it as \"the maximum number of\ndirect connections the pooler can maintain per unique user, database, and mode\ncombination\", so two connection strings with a different user or mode each get\na pool of that size. The same 60 serve the Data API, Auth and Storage, and\nStorage connects through Supavisor with a pool of its own. The FAQ's warning:\n\"If Supavisor uses most of the available connections, you risk depriving other\nservers, such as Auth, from accessing your database.\" Auth is the service that\nsigns your users in.",[10,533,534],{},"Its rule of thumb is to keep the pooler under 40% of the connections if your\napp also uses the Data API, and to go toward 80% only if it does not.",[10,536,537,538,541],{},"In session mode a bigger pool does let more clients in, one stool each. That\nmoves the queue from the host's door into the kitchen. When the stools run out\nthere, Postgres answers ",[21,539,540],{},"remaining connection slots are reserved…"," to whichever\nservice asks next, and that can be Auth.",[253,543],{"alt":544,"caption":545,"src":546},"Two rows of the same 60 connection slots. In the first, the pooler's share is small and the Data API, Auth and Storage each hold a few, with free slots left over. In the second, the pooler's share has grown across most of the row, and Auth's slots at the end are pushed out past the edge and crossed out.","The pool size comes out of the same connections the Data API, Auth and Storage use. Grow it far enough and one of them is left without a seat.","\u002Fblog\u002Fmax-client-connections-reached\u002Fone-kitchen-1600x700.png",[44,548,550],{"id":549},"the-connection-string-skips-your-policies","The connection string skips your policies",[10,552,553,554,556,557,560],{},"A connection string is a password, and the user in it is usually ",[21,555,332],{},",\nwhich Supabase's own Row Level Security guide says has ",[21,558,559],{},"bypassrls",". Every policy\nyou wrote is skipped for every query that string sends.",[10,562,563,564,566,567,570],{},"That changes what your server code has to do. A page that reads through\n",[21,565,38],{}," with your publishable key is filtered row by row by your\npolicies. The same page moved to a server route with Prisma or Drizzle reads\nevery row of the table, and the only thing standing between one user and\nanother user's rows is the ",[21,568,569],{},"where"," your route adds. If you move pages to a\nserver route to get past this error, check that each one filters by the\nsigned-in user before it ships.",[10,572,573,574,577,578,581,582,586],{},"The string also never goes in a variable whose name starts with ",[21,575,576],{},"VITE_"," or\n",[21,579,580],{},"NEXT_PUBLIC_",". Those prefixes put the value into the code every visitor\ndownloads, and\n",[248,583,585],{"href":584},"\u002Fblog\u002Fvite-and-next-public-env-vars","what those two prefixes do"," has a\npost of its own. A browser cannot open a Postgres connection, so a connection\nstring in the frontend makes nothing work and hands the database password to\nanyone who opens your site.",[10,588,589,590,594],{},"Whether any of your tables answers a request that carries no login, and\nwhether a secret key it recognises is in the code your site sends, are two of\nthe nine checks in ",[248,591,593],{"href":592},"\u002Fsecurity-scanner","Reeve's free scan",". It reads your live\napp the way a visitor's browser does, takes about 20 seconds and needs no\naccount.",[44,596,598],{"id":597},"knowing-when-it-happens-again","Knowing when it happens again",[10,600,601],{},"This error comes back when the traffic does, and the busy hour is rarely one you\nspend reading function logs.",[10,603,604],{},[227,605,606,610],{},[248,607,609],{"href":608},"\u002Fwebsite-monitoring","Reeve Monitor"," checks your live app from outside:",[193,612,613,616,619,622,625],{},[196,614,615],{},"whether it is up, every 60 seconds, and every 15 while it is down",[196,617,618],{},"up to 10 more pages, read for words that must be there and words that must not, such as \"Something went wrong\"",[196,620,621],{},"a message by email, Telegram, Slack or webhook, with a screenshot and a log kept for 30 days, so you know which page failed and when",[196,623,624],{},"all nine security checks every hour",[196,626,627],{},"a monthly report, in plain language, of what it saw",[10,629,630],{},[227,631,632,636],{},[248,633,635],{"href":634},"\u002Fsupabase-backups","Reeve Care"," keeps a copy of your Supabase database from\nbefore the next change you make to it:",[193,638,639,642,645,648,651],{},[196,640,641],{},"an encrypted copy on a schedule, on Reeve's own storage in the EU, outside your Supabase account",[196,643,644],{},"each copy verified before it counts, by counting the rows in every table",[196,646,647],{},"your uploaded files as well, once you connect a Storage credential",[196,649,650],{},"a one-click restore, with a safety copy of the current state taken first",[196,652,653],{},"everything Monitor does",[44,655,657],{"id":656},"what-to-do-today","What to do today",[659,660,661],"key-takeaways",{},[193,662,663,679,685,688,691],{},[196,664,665,666,669,670,672,673,669,676,678],{},"Read the error and the port: ",[21,667,668],{},"(EMAXCONN)"," on ",[21,671,114],{}," is the transaction pooler's client limit, and ",[21,674,675],{},"(EMAXCONNSESSION)",[21,677,133],{}," at the pooler address is the pool size.",[196,680,681,682,684],{},"Count who holds the connections with ",[21,683,375],{},", and close the tools and test runs you left connected.",[196,686,687],{},"Point serverless code at the Transaction pooler string, turn prepared statements off, and create the client once with a pool of 1.",[196,689,690],{},"Leave the pool size inside Supabase's 40% and 80% guidance, because Auth and the Data API draw on the same connections.",[196,692,693],{},"Check that every server route using the connection string filters by the signed-in user, since no policy does it for that string.",[10,695,696,697,701],{},"Start with the connection string in your server's environment: its port tells\nyou which half of this post is yours. If you are moving pages to a server route\nas part of the fix, ",[248,698,700],{"href":699},"\u002Fchecklist","the 10-minute security checklist"," covers what\nto look at before it goes live.",{"title":23,"searchDepth":703,"depth":703,"links":704},3,[705,707,708,709,710,711,712,713,714],{"id":46,"depth":706,"text":47},2,{"id":71,"depth":706,"text":72},{"id":216,"depth":706,"text":217},{"id":260,"depth":706,"text":261},{"id":379,"depth":706,"text":380},{"id":524,"depth":706,"text":525},{"id":549,"depth":706,"text":550},{"id":597,"depth":706,"text":598},{"id":656,"depth":706,"text":657},"Security basics","\u002Fblog\u002Fmax-client-connections-reached\u002Fcover-1200x630.png","A long counter with a person on every stool, running out of the frame, and a queue at the door whose first person has been turned away.","Supabase \"max client connections reached\" means the pooler has no room for one more client. The port in your connection string decides the limit.",false,"md",[722,725,728,731,734],{"q":723,"a":724},"What does \"max client connections reached\" mean in Supabase?","Supavisor, the pooler between your app and your Supabase database, already has as many clients connected as it allows and refused one more. In transaction mode, port 6543, your compute size sets the limit: 200 on the Free plan. The message reaches your app as a FATAL error with the code XX000 and the prefix (EMAXCONN).",{"q":726,"a":727},"Why do I get \"max clients reached in session mode\" with only a few users?","In session mode each client keeps its database connection until it disconnects, so Supavisor admits only as many clients as the pool size, 15 by default. A serverless function opens a client in every running copy of itself, and a handful of copies fills that. Use the Transaction pooler string, port 6543, for serverless code.",{"q":729,"a":730},"Does raising the pool size fix \"max client connections reached\"?","Not in transaction mode, where the client limit comes from the compute size. The pool size is how many of the database's own connections the pooler may open, out of the same 60 on the Free plan that Auth, Storage and the Data API use. Supabase suggests keeping the pooler under 40% of them if your app also uses the Data API.",{"q":732,"a":733},"What is the difference between port 5432 and 6543 on Supabase?","On the pooler address, 5432 is session mode, where a client keeps its database connection for as long as it stays connected, and 6543 is transaction mode, where clients take turns on shared connections one transaction at a time. Supabase recommends 6543 for serverless and edge functions, and session mode or a direct connection for long jobs such as migrations and pg_dump.",{"q":735,"a":736},"What does \"remaining connection slots are reserved\" mean on Supabase?","Postgres itself has run out of ordinary connections and is keeping the last few for superusers. It counts every connection: your direct ones, the pooler's, and those of the Data API, Auth and Storage. On the Free plan the total is 60. Find who holds them with pg_stat_activity before you change any setting.","\u002Fblog\u002Fmax-client-connections-reached\u002Fcard-800x500.png",[739,740,741,742,743,744,745,746],"max client connections reached supabase","max client connections reached","max clients reached in session mode","EMAXCONN supabase","supabase too many connections","remaining connection slots are reserved","sorry too many clients already","supavisor max clients",{},true,"Supabase \"max client connections reached\"","\u002Fblog\u002Fmax-client-connections-reached","2026-11-09",{"title":5,"description":718},"blog\u002Fmax-client-connections-reached",[755,756,757],"\"max client connections reached\" on Supabase comes from Supavisor, the pooler between your app and its database. It already holds as many clients as it allows: 200 on the Free plan in transaction mode, port 6543.","In session mode, port 5432 on the pooler address, the limit is the pool size, 15 by default, and each client keeps its database connection until it disconnects. A serverless app on that string is refused at its sixteenth client.","Move serverless code to port 6543, create its database client once with a pool of 1, and close the tools you left connected. A bigger pool size does not lift the client limit, and it takes connections that Auth needs.","JVBzHmEjmOWQc3zkM3sawnsmclyk5M85jt8fZNruiHE",[760,766,772,778,784,790,797,803,809,815,821,827,833,839,840,846,852,858,864,870,876,882,888,893,899,905,911,917,923,929,935,941,947,953,959,965,971,977,983,989,995,1001,1007,1013,1019,1025,1031,1037,1043,1049,1055,1061,1067,1073,1079,1085,1091,1096,1102,1107,1113,1119,1125,1131,1137,1143,1149,1154,1160,1166,1172,1178,1184,1190,1196,1202,1208,1214,1220,1226,1232,1238,1244,1250,1256,1262,1268,1274,1280,1286,1292,1298,1304,1310,1316,1322,1328,1333,1339,1345,1351,1356,1362],{"path":761,"title":762,"description":763,"published":764,"category":715,"image":765,"draft":719},"\u002Fblog\u002Fsupabase-only-returns-1000-rows","Supabase only returns 1000 rows: how to get the rest","Supabase only returns 1000 rows per request because of its Max rows setting. How to page through the rest, count them, and what the cap is there for.","2026-11-22","\u002Fblog\u002Fsupabase-only-returns-1000-rows\u002Fcard-800x500.png",{"path":767,"title":768,"description":769,"published":770,"category":715,"image":771,"draft":719},"\u002Fblog\u002Ferror-running-hook-uri","\"Error running hook URI\" in Supabase: why nobody can sign in","\"Error running hook URI\" means a Supabase Auth hook failed, so sign-in or sign-up fails for everyone. Where the real error is, and the safe fix.","2026-11-21","\u002Fblog\u002Ferror-running-hook-uri\u002Fcard-800x500.png",{"path":773,"title":774,"description":775,"published":776,"category":715,"image":777,"draft":719},"\u002Fblog\u002Fsupabase-realtime-channel-error","Supabase Realtime CHANNEL_ERROR: why a subscription gets nothing","Supabase Realtime CHANNEL_ERROR, or no events at all: usually a rule doing its job. How to read the reason and fix it without opening your data.","2026-11-20","\u002Fblog\u002Fsupabase-realtime-channel-error\u002Fcard-800x500.png",{"path":779,"title":780,"description":781,"published":782,"category":715,"image":783,"draft":719},"\u002Fblog\u002Ferr-ssl-version-or-cipher-mismatch","ERR_SSL_VERSION_OR_CIPHER_MISMATCH on a new custom domain","ERR_SSL_VERSION_OR_CIPHER_MISMATCH on a domain you just connected: why the name has no certificate yet, and when to wait, go DNS only or shorten the name.","2026-11-19","\u002Fblog\u002Ferr-ssl-version-or-cipher-mismatch\u002Fcard-800x500.png",{"path":785,"title":786,"description":787,"published":788,"category":715,"image":789,"draft":719},"\u002Fblog\u002Fapplication-error-a-client-side-exception-has-occurred","\"Application error: a client-side exception has occurred\" in Next.js","Application error: a client-side exception has occurred on your v0 or Next.js app: where the real error is and how to fix it.","2026-11-18","\u002Fblog\u002Fapplication-error-a-client-side-exception-has-occurred\u002Fcard-800x500.png",{"path":791,"title":792,"description":793,"published":794,"category":795,"image":796,"draft":719},"\u002Fblog\u002Freplit-database-rollback","Replit database rollback: does a checkpoint bring your data back?","A Replit database rollback restores the development database only when you ask. Your live data has a restore of its own. Which one you need, and how.","2026-11-17","Backups","\u002Fblog\u002Freplit-database-rollback\u002Fcard-800x500.png",{"path":798,"title":799,"description":800,"published":801,"category":715,"image":802,"draft":719},"\u002Fblog\u002Fthe-object-exceeded-the-maximum-allowed-size","\"The object exceeded the maximum allowed size\" in Supabase Storage","\"The object exceeded the maximum allowed size\" means a Supabase Storage limit refused the file. Which of two limits did it, and how to raise it.","2026-11-16","\u002Fblog\u002Fthe-object-exceeded-the-maximum-allowed-size\u002Fcard-800x500.png",{"path":804,"title":805,"description":806,"published":807,"category":715,"image":808,"draft":719},"\u002Fblog\u002Fsignups-not-allowed-for-this-instance","\"Signups not allowed for this instance\" in Supabase","\"Signups not allowed for this instance\" is Supabase refusing new accounts. Which switch does it, and why hiding your sign-up form is not the same thing.","2026-11-15","\u002Fblog\u002Fsignups-not-allowed-for-this-instance\u002Fcard-800x500.png",{"path":810,"title":811,"description":812,"published":813,"category":715,"image":814,"draft":719},"\u002Fblog\u002Fis-lovable-down-or-your-app","Is Lovable down, or is it your app? How to tell","Is Lovable down, or is it your app? Its editor, hosting and backend fail separately, and a paused backend looks like an outage. Here is how to tell.","2026-11-14","\u002Fblog\u002Fis-lovable-down-or-your-app\u002Fcard-800x500.png",{"path":816,"title":817,"description":818,"published":819,"category":715,"image":820,"draft":719},"\u002Fblog\u002Ffailed-to-load-module-script","\"Failed to load module script\": the blank page after a deploy","Failed to load module script and a blank page after a deploy: how to tell if one visitor or every visitor sees it, and the fix for each case.","2026-11-13","\u002Fblog\u002Ffailed-to-load-module-script\u002Fcard-800x500.png",{"path":822,"title":823,"description":824,"published":825,"category":715,"image":826,"draft":719},"\u002Fblog\u002Ferr-too-many-redirects","ERR_TOO_MANY_REDIRECTS on a custom domain behind Cloudflare","ERR_TOO_MANY_REDIRECTS after you put Cloudflare in front of your site: why the loop happens, and the fix that keeps your sign-ins encrypted.","2026-11-12","\u002Fblog\u002Ferr-too-many-redirects\u002Fcard-800x500.png",{"path":828,"title":829,"description":830,"published":831,"category":795,"image":832,"draft":719},"\u002Fblog\u002Flovable-cloud-backup","Lovable Cloud backup: does Lovable back up your database?","A Lovable Cloud backup is taken daily and kept about 14 days, in the same backend as your data. What it holds, who can restore it, how to keep a copy.","2026-11-11","\u002Fblog\u002Flovable-cloud-backup\u002Fcard-800x500.png",{"path":834,"title":835,"description":836,"published":837,"category":715,"image":838,"draft":719},"\u002Fblog\u002Fthis-site-cant-be-reached","\"This site can't be reached\" on your own domain: read the code","Your own site says \"This site can't be reached\". The code under the headline tells you whether the name, the host or the network failed, and what to fix.","2026-11-10","\u002Fblog\u002Fthis-site-cant-be-reached\u002Fcard-800x500.png",{"path":750,"title":5,"description":718,"published":751,"category":715,"image":737,"draft":719},{"path":841,"title":842,"description":843,"published":844,"category":715,"image":845,"draft":719},"\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":847,"title":848,"description":849,"published":850,"category":715,"image":851,"draft":719},"\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":853,"title":854,"description":855,"published":856,"category":715,"image":857,"draft":719},"\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":859,"title":860,"description":861,"published":862,"category":715,"image":863,"draft":719},"\u002Fblog\u002Fauth-session-missing","Supabase \"Auth session missing!\": where the session went","\"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.","2026-11-05","\u002Fblog\u002Fauth-session-missing\u002Fcard-800x500.png",{"path":865,"title":866,"description":867,"published":868,"category":715,"image":869,"draft":719},"\u002Fblog\u002Finvalid-claim-missing-sub-claim","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":871,"title":872,"description":873,"published":874,"category":715,"image":875,"draft":719},"\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":877,"title":878,"description":879,"published":880,"category":715,"image":881,"draft":719},"\u002Fblog\u002Fsupabase-auth-redirects-to-localhost","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":883,"title":884,"description":885,"published":886,"category":715,"image":887,"draft":719},"\u002Fblog\u002Femail-link-is-invalid-or-has-expired","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":250,"title":889,"description":890,"published":891,"category":715,"image":892,"draft":719},"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":894,"title":895,"description":896,"published":897,"category":795,"image":898,"draft":719},"\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","\u002Fblog\u002Fdatabase-error-deleting-user\u002Fcard-800x500.png",{"path":900,"title":901,"description":902,"published":903,"category":715,"image":904,"draft":719},"\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":906,"title":907,"description":908,"published":909,"category":715,"image":910,"draft":719},"\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":912,"title":913,"description":914,"published":915,"category":715,"image":916,"draft":719},"\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code","\"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":918,"title":919,"description":920,"published":921,"category":715,"image":922,"draft":719},"\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":924,"title":925,"description":926,"published":927,"category":715,"image":928,"draft":719},"\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":930,"title":931,"description":932,"published":933,"category":715,"image":934,"draft":719},"\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":936,"title":937,"description":938,"published":939,"category":715,"image":940,"draft":719},"\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":942,"title":943,"description":944,"published":945,"category":715,"image":946,"draft":719},"\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":948,"title":949,"description":950,"published":951,"category":715,"image":952,"draft":719},"\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":954,"title":955,"description":956,"published":957,"category":715,"image":958,"draft":719},"\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":960,"title":961,"description":962,"published":963,"category":715,"image":964,"draft":719},"\u002Fblog\u002Fsupabase-users-logged-out","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":966,"title":967,"description":968,"published":969,"category":715,"image":970,"draft":719},"\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":972,"title":973,"description":974,"published":975,"category":715,"image":976,"draft":719},"\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":978,"title":979,"description":980,"published":981,"category":715,"image":982,"draft":719},"\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":984,"title":985,"description":986,"published":987,"category":715,"image":988,"draft":719},"\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":990,"title":991,"description":992,"published":993,"category":715,"image":994,"draft":719},"\u002Fblog\u002Fdatabase-error-saving-new-user","\"Database error saving new user\" in Supabase: how to fix it","\"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":996,"title":997,"description":998,"published":999,"category":715,"image":1000,"draft":719},"\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":1002,"title":1003,"description":1004,"published":1005,"category":715,"image":1006,"draft":719},"\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":1008,"title":1009,"description":1010,"published":1011,"category":715,"image":1012,"draft":719},"\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":1014,"title":1015,"description":1016,"published":1017,"category":715,"image":1018,"draft":719},"\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":1020,"title":1021,"description":1022,"published":1023,"category":715,"image":1024,"draft":719},"\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":1026,"title":1027,"description":1028,"published":1029,"category":715,"image":1030,"draft":719},"\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":1032,"title":1033,"description":1034,"published":1035,"category":715,"image":1036,"draft":719},"\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":1038,"title":1039,"description":1040,"published":1041,"category":715,"image":1042,"draft":719},"\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":1044,"title":1045,"description":1046,"published":1047,"category":715,"image":1048,"draft":719},"\u002Fblog\u002Fmove-a-secret-to-an-edge-function","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":1050,"title":1051,"description":1052,"published":1053,"category":715,"image":1054,"draft":719},"\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":1056,"title":1057,"description":1058,"published":1059,"category":715,"image":1060,"draft":719},"\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":1062,"title":1063,"description":1064,"published":1065,"category":715,"image":1066,"draft":719},"\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":1068,"title":1069,"description":1070,"published":1071,"category":715,"image":1072,"draft":719},"\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":1074,"title":1075,"description":1076,"published":1077,"category":715,"image":1078,"draft":719},"\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":1080,"title":1081,"description":1082,"published":1083,"category":715,"image":1084,"draft":719},"\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":1086,"title":1087,"description":1088,"published":1089,"category":795,"image":1090,"draft":719},"\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":486,"title":1092,"description":1093,"published":1094,"category":795,"image":1095,"draft":719},"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":1097,"title":1098,"description":1099,"published":1100,"category":795,"image":1101,"draft":719},"\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":1103,"title":1104,"description":1105,"published":1100,"category":715,"image":1106,"draft":719},"\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":1108,"title":1109,"description":1110,"published":1111,"category":715,"image":1112,"draft":719},"\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":1114,"title":1115,"description":1116,"published":1117,"category":715,"image":1118,"draft":719},"\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":1120,"title":1121,"description":1122,"published":1123,"category":795,"image":1124,"draft":719},"\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":1126,"title":1127,"description":1128,"published":1129,"category":715,"image":1130,"draft":719},"\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":1132,"title":1133,"description":1134,"published":1135,"category":715,"image":1136,"draft":719},"\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":1138,"title":1139,"description":1140,"published":1141,"category":715,"image":1142,"draft":719},"\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":1144,"title":1145,"description":1146,"published":1147,"category":715,"image":1148,"draft":719},"\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":584,"title":1150,"description":1151,"published":1152,"category":715,"image":1153,"draft":719},"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":1155,"title":1156,"description":1157,"published":1158,"category":715,"image":1159,"draft":719},"\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":1161,"title":1162,"description":1163,"published":1164,"category":715,"image":1165,"draft":719},"\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":1167,"title":1168,"description":1169,"published":1170,"category":715,"image":1171,"draft":719},"\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":1173,"title":1174,"description":1175,"published":1176,"category":795,"image":1177,"draft":719},"\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":1179,"title":1180,"description":1181,"published":1182,"category":795,"image":1183,"draft":719},"\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":1185,"title":1186,"description":1187,"published":1188,"category":795,"image":1189,"draft":719},"\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":1191,"title":1192,"description":1193,"published":1194,"category":715,"image":1195,"draft":719},"\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":1197,"title":1198,"description":1199,"published":1200,"category":715,"image":1201,"draft":719},"\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":1203,"title":1204,"description":1205,"published":1206,"category":715,"image":1207,"draft":719},"\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":1209,"title":1210,"description":1211,"published":1212,"category":715,"image":1213,"draft":719},"\u002Fblog\u002Frotate-supabase-service-role-key","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":1215,"title":1216,"description":1217,"published":1218,"category":715,"image":1219,"draft":719},"\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":1221,"title":1222,"description":1223,"published":1224,"category":715,"image":1225,"draft":719},"\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":1227,"title":1228,"description":1229,"published":1230,"category":715,"image":1231,"draft":719},"\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":1233,"title":1234,"description":1235,"published":1236,"category":715,"image":1237,"draft":719},"\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":1239,"title":1240,"description":1241,"published":1242,"category":715,"image":1243,"draft":719},"\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":1245,"title":1246,"description":1247,"published":1248,"category":715,"image":1249,"draft":719},"\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":1251,"title":1252,"description":1253,"published":1254,"category":795,"image":1255,"draft":719},"\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":1257,"title":1258,"description":1259,"published":1260,"category":715,"image":1261,"draft":719},"\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":1263,"title":1264,"description":1265,"published":1266,"category":795,"image":1267,"draft":719},"\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":1269,"title":1270,"description":1271,"published":1272,"category":715,"image":1273,"draft":719},"\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":1275,"title":1276,"description":1277,"published":1278,"category":715,"image":1279,"draft":719},"\u002Fblog\u002Fwhere-to-find-supabase-api-keys","Where to find your Supabase URL, publishable and secret keys","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":1281,"title":1282,"description":1283,"published":1284,"category":715,"image":1285,"draft":719},"\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":1287,"title":1288,"description":1289,"published":1290,"category":715,"image":1291,"draft":719},"\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":1293,"title":1294,"description":1295,"published":1296,"category":795,"image":1297,"draft":719},"\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":1299,"title":1300,"description":1301,"published":1302,"category":795,"image":1303,"draft":719},"\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":1305,"title":1306,"description":1307,"published":1308,"category":715,"image":1309,"draft":719},"\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":1311,"title":1312,"description":1313,"published":1314,"category":715,"image":1315,"draft":719},"\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":1317,"title":1318,"description":1319,"published":1320,"category":795,"image":1321,"draft":719},"\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":1323,"title":1324,"description":1325,"published":1326,"category":715,"image":1327,"draft":719},"\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":1329,"title":1330,"description":1331,"published":1326,"category":715,"image":1332,"draft":719},"\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":1334,"title":1335,"description":1336,"published":1337,"category":715,"image":1338,"draft":719},"\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":1340,"title":1341,"description":1342,"published":1343,"category":795,"image":1344,"draft":719},"\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":1346,"title":1347,"description":1348,"published":1349,"category":715,"image":1350,"draft":719},"\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":1352,"title":1353,"description":1354,"published":1349,"category":795,"image":1355,"draft":719},"\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":1357,"title":1358,"description":1359,"published":1360,"category":795,"image":1361,"draft":719},"\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":1363,"title":1364,"description":1365,"published":1360,"category":715,"image":1366,"draft":719},"\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",1795336308202]