How to restart or update the n8n service?

Introduction

Running a self-hosted n8n instance on your Virtual Private Server (VPS) requires occasional maintenance. You may need to restart the service to apply configuration changes or update it to access new features and security improvements.

This guide explains how to safely restart and update n8n using Node.js, PM2, or Docker—ensuring your automation workflows remain secure, stable, and fully functional. For best reliability and performance, running n8n on a dependable VPS such as one from BigCloudy is highly recommended.

Why Restart or Update n8n?

Keeping n8n up to date and properly restarted ensures optimal performance and security.

1. Apply Configuration Changes

Updates to environment variables, authentication settings, or workflow configurations require a restart to take effect.

2. Maintain Security

n8n releases updates that fix bugs and patch vulnerabilities. Regular updates help protect your automation data.

3. Access New Features and Improvements

New versions include additional integrations, workflow enhancements, and performance optimizations.

Step 1: Identify How n8n Is Running

Before restarting or updating, identify how n8n is installed on your VPS:

• Node.js Direct Installation – Installed globally via npm
• PM2 Process Manager – Running as a managed background service
• Docker or Docker Compose – Running inside a container

Each setup uses different commands.

Step 2: Restart n8n

Option 1: Node.js Direct Installation

If running n8n manually:

n8n stop

n8n start

If the process is stuck or running in the background:

pkill -f n8n

n8n start

Option 2: Restart n8n Using PM2

Restart the PM2-managed service:

pm2 restart n8n

Check the status:

pm2 list

Option 3: Restart n8n Using Docker

Restart using the container name or ID:

docker ps

docker restart <container_name_or_id>

For Docker Compose:

docker-compose restart

Your n8n instance should now be back online.

Step 3: Update n8n

Option 1: Update n8n (Node.js Installation)

Update using npm:

sudo npm install n8n -g

Restart n8n after updating.

Option 2: Update n8n Using PM2

Update globally:

sudo npm install n8n -g

Restart PM2 service:

pm2 restart n8n

Option 3: Update n8n Using Docker

Pull the latest n8n image:

docker pull n8nio/n8n

docker-compose down

docker-compose up -d

This replaces the old container with the latest version.

Step 4: Verify the Update

After restarting or updating:

• Open your n8n dashboard
• Check the version (Profile → About)
• Test workflows to confirm everything works correctly

Step 5: Optional — Backup Before Updating

Creating a backup ensures you can restore your workflows if something goes wrong.

Node.js or PM2 Backup

Backup the default n8n directory:

tar -czvf n8n_backup.tar.gz ~/.n8n

Docker Backup

If using Docker volumes:

docker run --rm -v n8n-data:/data -v $(pwd):/backup busybox tar czvf /backup/n8n_backup.tar.gz /data

Troubleshooting

1. Service Fails to Restart

Check logs:

pm2 logs n8n

Docker logs:

docker logs <container_name>

2. Version Didn’t Update

Clear npm cache:

npm cache clean --force

Ensure you are updating the correct npm installation or Docker image.

3. Workflow Errors After Update

• Verify environment variables
• Check credentials
• Restore from backup if needed