Update n8n self hosted in Heroku

Questions
1

Hello Community,

I’m looking for the best method to update our n8n self-hosted instance on Heroku without risking any data loss. We have instances hosted on GPC and Digital Ocean, but the Heroku setup seems to be lagging behind, and I don’t have much context on how to smoothly update it without issues.

I’d really appreciate a detailed walkthrough or suggestions on how to handle this update properly. Thanks in advance!

2
  1. Update Version:
  • If using Docker: Edit the Dockerfile to specify the desired version (e.g., n8n:1.XX.X instead of latest) or use latest for the newest release.
  • If deployed via Git: Pull changes (git pull) and ensure package.json or Dockerfile points to the new version.
  1. Redeploy:
  • For Git: Push changes with git push heroku main.
  • For Docker: Run heroku container:push web and heroku container:release web.
  1. Verify: Access n8n in your browser to confirm workflows and data are intact. Roll back with heroku rollbacks if issues arise.
  2. Logs: Monitor logs (heroku logs --tail) to catch any errors during the update.

Note: Heroku may override some environment variables (e.g., PORT). Ensure settings like N8N_ENCRYPTION_KEY remain unchanged. If using an external database, verify connectivity.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.