Replit website not working? Start here
The most common reasons a Replit site or app stops working, and what fixes each one.
Updated
Replit's Agent will build a whole working app, front and back, from a description. That's also why Replit problems are a wider mix than the other tools. There's more there to go wrong.
The good news is that one problem accounts for most of the calls we get, and it's near the top of this list.
The site goes down when you close the tab
You build the app, it runs, you send the link to someone, and an hour later it's dead. Open Replit again and it comes back.
This isn't a bug. The link you're sharing is probably the workspace, the place where you build, and workspaces go to sleep when you're not in them. A site customers can rely on has to be deployed, which is a separate step in Replit that keeps it running whether or not you're there. If your "live" address contains a long random-looking string, it's likely the workspace. This one is worth fixing before anything else, and it's quick.
It works in the workspace but not after deploying
Two usual causes:
- Secrets didn't come along. Replit stores keys and passwords as secrets. The deployed app needs its own copy. If a key is missing there, the app fails silently at the first point it needs it, often the database or an email sender.
- The database is the wrong one. It's common for the workspace and the deployment to end up pointing at different databases. Your test data is in one, your customers are writing to the other, and neither of you can see what the other sees.
Both are quick to confirm once you know to look. Both are routine Service Call work if you'd rather not dig.
Open it as a stranger
Whatever else is going on, open the deployed address in a private window on your phone and run the free site check on it. Replit apps vary a lot in how they're built, so the check is the fastest way to find out whether Google can read yours.
Something stopped working and nobody told you
Replit apps rarely report errors anywhere you'd see them. A contact form stops sending. A page breaks on phones. A customer gets a blank screen. The first you hear of it is when someone complains, if they bother.
A Service Call finds the failure and fixes it, and adds error reporting so the next one reaches you first.
Customer data is open
If the Agent built a database for you, ask yourself who can read it. Often the answer is anyone who finds the address. Agent-built apps frequently check who you are on the page but not on the server, which means a determined visitor can skip the page entirely.
We can't check this from outside and won't without your written permission. Security Lockdown puts real checks on the server, writes the access rules, and moves secret keys out of reach.
The Agent keeps fixing the same bug
You describe a problem. The Agent says it's fixed. It isn't, or it is and something else broke. Repeat until the credits are gone.
Past a certain size, the tool can't hold the whole app in mind at once, so each change undoes earlier work. Nearly every Replit owner we talk to has been here. A Takeover moves the code to a developer who steadies it and makes the engineering calls the tool can't. Replit exports your code, so the work you've paid for comes with you.
Payments don't match orders
Charges that never became orders, orders that were never charged, receipts that don't send. The payment screen was built and the server-side confirmation wasn't. Finish the Checkout connects the two and runs real test purchases.
What to send us
The deployed address, the workspace link if you have it, what you expected, what happens instead, and when it started. We'll ask in writing before looking at anything behind the page.