N8n docker constantly 1 version behind

Questions
1

Hi,

For a few days now, n8n on docker constantly mentions being “1 version behind” in the Help bottom left menu, even after a successful update. Do you have this on your install as well? Software runs fine, no problem at all.

Philippe

2

Hi @philippelang

I would generally ignore it if I am running the latest stable version recommended by the forum

image
image301×336 6.26 KB

I do

3

Hi @philippelang and @kjooleng

I’ve seen this a few times on my own Docker setups as well, n8n says “1 version behind” even though I just updated. In my case it was never a bug in n8n itself, it was always Docker still running an older container or image.

What usually fixed it for me:

  • First, I run a force‑recreate so Docker can’t silently reuse the old container:

    bash

    docker compose up --force-recreate n8n

  • If the banner is still there, I clean up old images and pull again to be 100% sure:

    bash

    docker rmi docker.n8n.io/n8nio/n8n:latest
    docker image prune -a
    docker pull docker.n8n.io/n8nio/n8n:latest
    docker compose down
    docker compose up -d

I also once realised my docker-compose.yml was pinned to a specific tag instead of latest, so the UI was technically correct that a newer version existed. After switching the image line to docker.n8n.io/n8nio/n8n:latest and recreating the container, the version indicator finally matched what I expected.

If you share how you’re running n8n (plain Docker Compose, Coolify, Portainer, etc.), I can try to mirror the exact steps I’d use in that environment.

4

That didn’t work for me

5

Thanks, I tried combinations of the commands you mention, but no luck for me here… I’m using the standard “docker compose”.

6

Same issue!
It’s new, since 2.20.7-exp0. I’ve shared this on the community forum as well.
Stéphane

7

If you are using the latest tag it will always point to the stablerelease, next will point to beta

Each week when we release a new version we mark it as being beta/ next and the version from the previous week becomes stable / latest

Hopefully this helps.

8

As @Jon mentioned, I have tried in docker compose with image: n8nio/n8n:next instead of latest, here I am with Version 2.25.3. Hope it helps. Happy Automation!

image

10

@monni The next version is currently 2.25.4and latest is 2.23.4 this sounds like it is maybe working as expected and you might need to just repull the image if it was a minor release.

If you click on where it shows 1 version behind which version does it show?

11

Quick update, Mystery solved, Where 2.24 didn’t release properly it still had a stale entry in the api. This has now been corrected and it should fix itself once the cache clears or when 2.25 becomes stable whichever happens first.

13

I have pulled again with image: n8nio/n8n:beta and came with Version 2.25.5
Thanks.

14

Works great, without pulling anything I’m up to date now. I guess your cache has cleared. Thanks!