Update n8n on Proxmox?

To update n8n on Proxmox, stop the current Docker container, pull the new image, restore any backups if needed, and recreate the container. This guide shows a safe, simple flow to update n8n on Proxmox using Docker and docker-compose, with commands you can run on your Proxmox VM or container host.

What You Need

Proxmox VM or LXC with Docker and docker-compose installed.
SSH access with sudo privileges.
Existing n8n Docker setup using a volume or bind mount for data.
Time to take a brief backup and restart the service.

How to Update n8n on Proxmox

Follow these numbered steps. Each step includes commands that work on common Docker setups.

1. Backup n8n data

Make a quick backup of your n8n data volume. Replace n8n-data with your volume name.

sudo docker run --rm -v n8n-data:/data -v $(pwd):/backup alpine \
  sh -c "cd /data && tar czf /backup/n8n-data-backup-$(date +%F).tgz ."

2. Stop the running container

Stop n8n to avoid write conflicts. Use the container name from your setup.

sudo docker-compose -f /path/to/docker-compose.yml down
# or if you run docker directly
sudo docker stop n8n && sudo docker rm n8n

3. Pull the latest image

Pull the new n8n image so the host has the updated bits.

sudo docker pull n8nio/n8n:latest
# With docker-compose
cd /path/to && sudo docker-compose pull n8n

4. Recreate the container

Start the container with the same volumes and environment. docker-compose is safest for reproducing your config.

cd /path/to
sudo docker-compose up -d --force-recreate --remove-orphans
# or with docker run (example)
sudo docker run -d --name n8n -p 5678:5678 \
  -v n8n-data:/home/node/.n8n \
  -e N8N_BASIC_AUTH_ACTIVE=true \
  -e N8N_BASIC_AUTH_USER=admin \
  -e N8N_BASIC_AUTH_PASSWORD=changeme \
  n8nio/n8n:latest

5. Verify the update

Check logs and the web UI. Confirm the version and that workflows load.

sudo docker-compose logs -f n8n
# or
sudo docker logs -f n8n

Update

To update in the future, repeat the pull and recreate steps. For zero-downtime, run a second container behind a proxy and swap traffic after testing. Keep a routine update schedule and test on a staging VM when possible.

If an update fails, restore the data tarball into a new volume and start the previous image tag until you troubleshoot.

Security

Use basic auth, OAuth, or reverse-proxy auth to protect n8n.
Store secrets outside the container, for example in environment files managed by your host.
Keep Docker and the host kernel updated on your Proxmox VM.
Limit SSH access and use key-based auth with sudo for commands above.

Done

After the steps, your n8n instance will run the updated image on your Proxmox host. Monitor the logs for errors and test critical workflows.

If you need to rollback, stop the updated container, re-run the old image tag, and restore the backup volume.

Written by Neil

Neil is a true n8n geek who lives and breathes workflow automation. He dives deep into nodes, triggers, webhooks, custom logic, and self-hosting setups, sharing everything he learns about n8n on AutomationCompare.com. As part of a broader team of automation specialists, Neil focuses purely on mastering n8n and helping others unlock its full potential.