Resolving SQLITE_FULL Errors in n8n Self-Hosted Instances

Understanding SQLITE_FULL Errors

A SQLITE_FULL error means the SQLite database used by your n8n instance has run out of space. When this happens, database operations stop working, which can prevent fetching node types and block workflow creation, modification, or execution.

Note: these actions require knowledge about server management and the used deployment method.
It is always recommended to back up your data before taking any action on the n8n database.

Steps to Resolve

Access your server

Connect to the machine hosting your n8n instance (for example, via SSH).

This might vary depending on how you choose to deploy n8n.
Using Docker, for example:


docker exec -it <container_name_or_id> sh

Finding your container name


# List all running containers
docker ps 

# Or filter for n8n 

docker ps | grep n8n

Locate the n8n database

The database file is usually named database.sqlite.
The default directory is typically /home/node/.n8n/.
Example: cd /home/node/.n8n/

Reclaim space with VACUUM

Run the SQLite VACUUM command to rebuild the database file and free unused space:


sqlite3 database.sqlite "vacuum;"

Make sure to run this command in the directory where your n8n database is located.

If the issue persists

Increase the disk/volume size allocated to the database and rerun VACUUM.
If you’re using a hosting provider (e.g., Hostinger), contact their support for help with disk resizing or server configuration.

Additional Recommendations

Monitor database size regularly and perform periodic cleanups (VACUUM).
Set up disk usage alerts to catch low-space conditions early.
Plan for additional storage if your data grows steadily.

When to Contact Support

If manual cleanup does not resolve the issue, or if you are unsure about performing these steps, contact your hosting provider's support team or n8n support for further assistance.

For more discussions and community support, visit the n8n Community Forum.