Common Errors & When Leo Needs a LlamaPress Admin
What the scary messages mean — and the fastest way to get back up.
Sometimes Leo runs into something it can't fix on its own and shows a technical message — or your app shows an error page. Most of these are environment-level issues (the server or container behind your app), not problems with your actual code. They're quick for our team to resolve. This page helps you recognize them and get unstuck fast.
The 10-second version: if you see any of the errors below, email support@llamapress.ai with your app name and a copy of the exact message (or a screenshot). These almost always just need a quick restart or redeploy on our side, and your code/data is safe.
Error cheat-sheet
502 error, blank white page, or "Puma needs a restart"
Your app's web server needs a restart. This often happens right after an app wakes from sleep, or after a big change. Try a hard refresh (Ctrl/Cmd + Shift + R) and wait a couple of minutes first — if it persists, email us and we'll restart it.
"409 Conflict" / "every command returns a 409" / ERROR CREATE-EXEC ... 409
Leo's file tools (read/edit) still work, but its ability to run commands in your container is temporarily blocked. The container needs a reset. This isn't something Leo can fix from inside — email us and we'll restart the container; it's usually back within minutes.
"My edits won't take effect" / "shared volume doesn't sync" / "needs a redeploy"
Some changes — especially to configuration files (for example session/login settings) — only take effect after the app is redeployed and the server restarted. If Leo says it made a fix but tells you it "needs a LlamaPress admin to redeploy," that's expected for those files. Let us know what changed and we'll deploy it.
"Leo needs write access to public/" / "allow inline scripts" / "run precompile"
Parts of the app environment are intentionally read-only for safety, so Leo can't always move files into certain folders or precompile assets itself. There's usually a cleaner way to achieve the same result — email us the request (paste exactly what Leo asked for) and we'll either open the right access or suggest the better approach.
A note on Leo's diagnoses: when Leo gets stuck, it sometimes guesses at the cause and can be confidently wrong (for example blaming a "permission" or "cache" problem that isn't real). That's okay — just forward us what it said and what you were actually trying to do, and we'll find the real cause. The error name and your goal are the two most useful things to include.
What to send us (so we can fix it on the first try)
- Your app name / URL (e.g.
leo-yourname). - The exact error — copy Leo's message or screenshot the page.
- What you were doing when it happened.
Reach us at support@llamapress.ai (or kody@ / darren@llamapress.ai).
How to hit fewer of these
- An always-on paid plan avoids most sleep-related 502s and wake errors — your app stays warm 24/7. See Plans & Pricing.
- Save checkpoints as you go so you can always roll back a change cleanly. See Saving Your Work.
- If your app freezes during a heavy task (like generating PDFs), that's usually a resource issue, not an error — see Why Is My App Slow or Frozen?