n8n Server Crashed? 3-Line Fix for SQLite Busy Error in v1.85.0

If you upgraded n8n to v1.85.0 and got SQLITE_BUSY: database is locked, your server probably crashed on startup.

Here’s the 3-line fix that worked for me on Docker.

Why it happens
n8n v1.85.0 is more strict with SQLite write locks. If a workflow was running during the upgrade or your container didn’t shut down clean, the DB stays locked.

The 3-Line Fix for Docker
Run these in your server terminal:

bash
 1. Stop n8n completely
docker stop n8n

 2. Remove the lock file 
docker exec n8n rm /home/node/.n8n/database.sqlite-shm
docker exec n8n rm /home/node/.n8n/database.sqlite-wal

3. Start n8n again
docker start n8n
Best long-term fix: Switch to Postgres*
SQLite is fine to start, but Postgres fixes this 100%. If you’re running n8n for production, do the switch now before it happens again.

I wrote a full step-by-step guide with Docker Compose and all Postgres commands here: 
https://worldcutruygdski.blogspot.com/2026/06/n8n-sqlite-busy-fix-1-85-0.html

---
_