Bolt.new Error 500: What This Means and What to Do Next

Your app is showing "Error 500," "Internal Server Error," or just "Something went wrong." You ask the AI to fix it. It changes something. Now you have a different error. Or the same one. You've been going in circles for an hour and burned through 200 credits.

Stop. Here's what's actually happening.

What "Error 500" actually means

Every website has two halves:

• The front — what you see. Buttons, text, images, forms.
• The back — what you don't see. The code that saves data, checks passwords, talks to Stripe, sends emails.

"Error 500" means the back half crashed. It tried to do something, hit a problem it didn't expect, and gave up. The "500" is a code that means "I broke and I can't tell you why."

This is different from an error you see in your app. This is the server itself failing. And the AI often can't fix it because it can't see what the server sees.

The three most common causes

1. The database connection is broken

Your app tries to save or load data, and the database isn't responding. Maybe the connection details are wrong, maybe the database hit its free tier limit, or maybe the AI wrote a query that the database doesn't understand.

Signs: The error happens when you try to sign up, log in, save something, or load a page that shows data.

2. A secret key is missing or wrong

Your app needs to talk to external services — Supabase, Stripe, an email provider. Each one requires a secret key. If the key is missing, the app can't connect, and instead of showing a nice error message, it crashes with a 500.

Signs: The error happens when you try to do something specific — pay, send an email, upload a file — but other parts of the app work fine.

3. The AI wrote code that works sometimes but not always

This is the sneaky one. The code works when there's one user, but crashes when two people use it at the same time. Or it works with small amounts of data but breaks when the database has more than a few hundred entries. Or it works on Tuesday but not on the first of the month because of a date calculation bug.

Signs: The error is intermittent — sometimes it works, sometimes it doesn't, and you can't figure out the pattern.

What to try

1. Check the terminal output. In Bolt.new, look at the terminal/console panel at the bottom. If you see red text or error messages there, copy the ENTIRE message — not just the first line — and paste it back to the AI. Say "this is the server error, not a front-end error."
2. Check your environment variables. In Bolt.new, look for a section called "Secrets" or "Environment Variables." Make sure every key that your app needs is actually filled in. The AI sometimes references keys that don't exist yet.
3. Try reverting. If the app was working before and the AI's "fix" broke it, use the version history to go back to when it worked. Then describe the problem differently instead of asking the AI to fix the same thing again.

The credit burn trap

Here's what happens to most Bolt.new users with a 500 error:

1. You tell the AI about the error
2. The AI changes something
3. You get a different error (or the same one)
4. You tell the AI about the new error
5. The AI changes something else, which breaks something that was working
6. Repeat until you've burned $50-200 in credits

This loop happens because the AI is guessing. It can't see the actual server logs. It can't reproduce the problem. It's pattern-matching against your error message and trying things that sometimes work for other people. Each attempt costs you credits whether it works or not.

A human engineer doesn't guess — they read the actual error, understand the actual cause, and fix the actual problem. Usually in one pass.