Hi. I am wondering if my n8n gets updated properly. On Github, as of today, I see version 1.70.3 in releases, but on my raspberry pi I see 1.67.1.
I have executed the update command multiple times without errors, but I keep seeing 1.67.1 instead of the latest.
Do RPI versions come out slower than the ones released on github?
Thanks for answering. Have a yummy day!
n8n
2
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
ria
3
Hey @fpcteam
How exactly are you running the update on your RPI?
Are you using a docker image?
We have our versions up to date there
https://hub.docker.com/r/n8nio/n8n/tags
I installed via npm. Here are the commands I run:
pm2 stop n8n
sudo npm update -g n8n
here’s what I have

here’s the log:
sudo npm update -g n8n --loglevel verbose -dd
npm verbose cli /usr/bin/node /usr/bin/npm
npm info using [email protected]
npm info using [email protected]
npm verbose title npm update n8n
npm verbose argv "update" "--global" "n8n" "--loglevel" "verbose" "--loglevel" "verbose"
npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2024-12-06T09_22_18_796Z-
npm verbose logfile /root/.npm/_logs/2024-12-06T09_22_18_796Z-debug-0.log
npm http cache https://registry.npmjs.org/@pm2%2fpm2-version-check 43ms (cache hit)
npm http cache @pm2/pm2-version-check@https://registry.npmjs.org/@pm2/pm2-version-check/-/pm2-version-check-1.0.4.tgz 1ms (cache hit)
changed 1 package in 4s
79 packages are looking for funding
run `npm fund` for details
npm verbose cwd /home/pi
npm verbose os Linux 6.6.51+rpt-rpi-v8
npm verbose node v22.11.0
npm verbose npm v10.9.1
npm verbose exit 0
npm info ok
Jon
5
Hey @fpcteam,
Try running npm install -g n8n@latest
and see if that works instead.
1 Like
fpcteam
6
Hi Ria… any clue on how to get my n8n updated?
fpcteam
7
trying now… but I am still curious as to why ‘update’ doesn’t work. 
fpcteam
8
did that and it still shows 1.67.1
but then I did this and got this:

fpcteam
9
It seems I have 2 n8n instances installed. one in /usr/bin/n8n and the other on /usr/local/bin/n8n.
the one in /usr/bin is 1.70.4 while the one in /usr/local/bin is 1.67.1
i check in the ui and it’s showing 1.67.1 which means my local version is running.
I tried npm update n8n (without -g), but it still shows as 1.67.1.
How do I get rid of the local n8n instance?
I tried this:
pi@rwpi:~ $ sudo npm uninstall n8n --verbose
npm verbose cli /usr/bin/node /usr/bin/npm
npm info using [email protected]
npm info using [email protected]
npm verbose title npm uninstall n8n
npm verbose argv "uninstall" "n8n" "--loglevel" "verbose"
npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2024-12-10T15_39_10_494Z-
npm verbose logfile /root/.npm/_logs/2024-12-10T15_39_10_494Z-debug-0.log
npm verbose reify failed optional dependency /home/pi/node_modules/fsevents
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 841ms
up to date, audited 139 packages in 3s
13 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
npm verbose cwd /home/pi
npm verbose os Linux 6.6.62+rpt-rpi-v8
npm verbose node v22.12.0
npm verbose npm v10.9.0
npm verbose exit 0
npm info ok
pi@rwpi:~ $ which n8n
/usr/local/bin/n8n
fpcteam
10
uninstalled all n8n instances. reinstalled one again with -g. it works fine now. closing this thread.
1 Like
system
Closed
11
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.