How To Fix Critical Version Warning On n8n Self-hosed Instance (Docker Compose)?

:wrench: Tutorial: How to Update Your Self-Hosted n8n Instance on AWS EC2 (Docker Compose Setup)

Watch the video

If you’re running n8n on AWS EC2 using Docker Compose and you’ve seen the dreaded:

:warning: “Critical update available”

…this step-by-step tutorial shows you exactly how to update your n8n instance safely — without losing any credentials or workflows.

:white_check_mark: What You’ll Learn

  • How to check your current n8n version

  • Where to find the latest release details

  • How to pull the updated Docker images

  • How to stop & restart containers using Docker Compose

  • How to verify that the upgrade was successful

:hammer_and_wrench: Stack Used

  • AWS EC2 (Amazon Linux 2023)

  • Docker + Docker Compose

  • n8n (Self-hosted)

This guide assumes you followed a standard Docker Compose setup for your self-hosted n8n instance.

:speech_balloon: Feedback or Questions?

Let me know how it goes, happy to answer questions or improve the guide based on your experience!