Replit app bug fixing: seven common problems in an app built with Replit, and the fix for each
Short answer: most bugs in an app built with Replit's Agent are one of two things. Either a
recent change broke something, and rolling back to the checkpoint that worked is faster than asking the Agent to
repair it. Or the published app is not the same as the preview: it runs an older copy of the code, its own
secrets, its own database and a disk that forgets. Find your symptom below; each one has a fix you can do
yourself.
Where to look first (two minutes)
Four places tell you what kind of problem it is:
The Agent's checkpoints (the history icon in the Agent chat): did it work at an earlier checkpoint?
Then it is problem 1.
Publishing, Logs. Open the Publishing pane and its Logs tab: a failed publish or a crashing live app
leaves the reason there (a missing package, a failed command, a missing environment variable, an error at
startup).
The Database tool, Production. Your live app has its own database. Select Production and open My Data
to see what the live app really holds. It opens read-only, so looking is safe.
status.replit.com: if Replit itself has an incident,
wait before you change anything.
Match the symptom
What you see
Problem
It worked, you asked for one more feature, and now a page is blank or shows an error
A change broke the app. The Agent saves a checkpoint as it works, after a finished feature
and before risky fixes. The cause of a fresh bug is almost always in the last change, so the fastest repair is to
go back to before it.
Fix: in the Agent chat, find the last checkpoint where the app worked and press
Rollback to here. Read the warning: everything made after that point is removed, code edits included. Two
things Replit's documentation says that are easy to miss. A rollback does not change your database unless you
tick Database under Additional rollback options, so if the broken change also changed your tables,
tick it. And a rollback never restores the live app's production database. If you roll back too far, you can
still go forward to a later checkpoint from the history view, but only until you make new changes.
The Agent is going in circles. Each new "please fix it" is another guess on top of the last
guess. After two failed tries, a third worded the same way rarely helps, and each paid request costs money.
Fix: stop and roll back to the last checkpoint that worked (problem 1). Then ask for a plan
before any change: start the message with /plan or end it with "Do not implement the changes yet",
which is the wording Replit's own documentation uses. Planning is not free either: the documentation says paid
requests can cost money even when they only produce a plan, and your spending is under Settings, Usage. Describe
the bug the way a tester would: which page, what you clicked just before, what you expected, what happened, and
the error from the Console or the Publishing logs copied word for word. Ask for the cause first and the change
second. When the same bug survives all of that, it needs a person reading the code.
The live app was not published again. Publishing takes a snapshot of your files at that
moment. Later changes in the editor do not reach the live app until you publish again.
Fix: press Publish again after the change, then reload the live app in a private
window so an old copy in your browser does not fool you.
The app does not start the way a published app must. The preview forgives things the
published app does not. Replit's troubleshooting page lists the usual ones: the server listens only on
localhost or 127.0.0.1; the port settings are wrong; the home page takes more than five
seconds to answer, so the health check at the end of publishing times out; the run or build command has a typo
or only works in the editor; or the program runs once and exits instead of staying up as a web server.
Fix: read Publishing, Logs first; the real error is usually there. Make the server listen on
0.0.0.0. If the .replit file has a ports section, one port needs
externalPort = 80, and the server must listen on that entry's localPort. Move slow
work (loading a big file, calling an outside service) out of the start-up and the home page. Check the build and
run commands in the Publishing pane. If you picked a Static deployment for an app that has a server (a login, a
database, an API), switch it to Autoscale.
The published app has its own secrets. Replit's troubleshooting page says it plainly:
secrets you set in the editor do not automatically carry over to your published app. The live app then gets an
empty value where the key should be, and what you see is a failed login, a payment that never completes, an
email that is never sent or a database that will not connect.
Fix: open Publishing, Adjust settings, Production app secrets, and add every key the
live app needs, spelled exactly as the code reads it. Use live keys there and test keys in the editor (Stripe
has a separate pair for each). Publish again. Login and payment services also keep a list of allowed addresses:
add your live address (the replit.app one or your own domain) next to the preview's, in the
service's own settings. Static deployments get no secrets at all. And never put a secret key in the code that
runs in the browser, where every visitor can read it; our security page
shows how to check.
Two databases: development and production. Every Replit app has a development database, where
you and the Agent build, and a production database, which holds the live app's data. Test records you made while
building are in the first; your users' records are in the second. When you publish, changes to the structure
(tables and columns added or removed) are applied to production. The Agent can read production but cannot
change it.
Fix: for "my live app is empty" or "the data is different", open the Database tool, select
Production, My Data, and look at what is really there. To correct a record by hand, turn on Enable
Editing; that change is yours, not the Agent's, so make it carefully. Before publishing a change that removes
a column or table, changes a column's type, adds a required field to a table that already has rows, or adds a
"must be unique" rule, check what it does to the rows your users already have: Replit's documentation names
exactly these as the changes that need care. Never paste a database connection string into a chat or a
screenshot; it contains the password.
The disk forgets and the app sleeps. Two facts about published apps surprise people. The file
system of a published app is not permanent: Replit's documentation says it resets every time you publish, so
pictures and files your users uploaded into a folder are gone after the next publish. And an Autoscale
deployment drops to zero running copies when nobody is visiting, so a timer or background job inside the app
stops with it.
Fix: keep uploads in a storage service and records in the database, never in a folder next
to the code. For work that must run at set times, use a Scheduled deployment; for something that must stay
connected all day (a chat bot, a queue worker), use a Reserved VM, which Replit describes as a server that never
sleeps and bills at a fixed monthly price.
Test it like a stranger before real users arrive
On the published app, not the preview: (1) open it in a private window,
signed out: you must see only what a visitor should see. (2) Sign up as a brand-new user with a second email
address and do the main task from start to finish, payment included if you take payments. (3) As that second
user, look for the first user's records: you must not find them. (4) Upload a file, change something small in
the editor, publish again, and check that the live app shows the change and still has the file. If all four
hold, the seven problems above are not in your app.
This is a checklist, not a study: we have not counted how often each problem happens. The facts
about Replit (checkpoints and what a rollback restores, planning and its cost, publishing as a snapshot, the
start-up rules and the five-second health check, production secrets, the two databases, the file system, the
deployment types) were read in Replit's own documentation
on November 20, 2026; the advice on describing a bug, allowed addresses and testing as a second user is general
engineering practice. Replit changes its menus, plans and prices often, so check its documentation if a name here
does not match what you see. Urgisoft is not affiliated with Replit.
When the same bug survives the steps above, it needs a person reading
the code. We fix apps made with Replit, Lovable, Bolt, Base44, Cursor and other AI builders, and tell you in plain
words what was wrong. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app working live from
$150. No fix, no charge. For a Replit app we work as a collaborator you invite to the project; we never ask for
your password. One honest note: Replit's documentation says an invited collaborator can see the values of a
project's secrets, so replace important keys after anyone from outside has helped, us included.