Unrecognized node type after upgrade from 1.61.0 to 1.62.6

[FlorianMeyer]

Describe the problem/error/question

After upgrading from 1.61.0 to 1.62.6 many nodes are unrecognized.
I installed n8n via “npm -g install n8n” and i am using node 18.17.1. n8n is started via pm2.

If i compare the nodes with nodes that I newly add - for example the scheduleTrigger node - i can see that the version is different:
original node version in original workflow:
“type”: “n8n-nodes-base.scheduleTrigger”,
“typeVersion”: 1.1,

If i now add a new scheduleTrigger to the old workflow the Version is lower:
“type”: “n8n-nodes-base.scheduleTrigger”,
“typeVersion”: 1,

So the new n8n version dont know the n8n-node version from the workflow i created with an older n8n version. This is confusing.
What am i doing wrong or is this a bug? I really dont want to update 20 workflows with lower n8n-node versions…

What is the error message (if any)?

The following error occurred on workflow activation:
Unrecognized node type: n8n-nodes-base.filter".

Install this node to use it

This node is not currently installed. It is either from a newer version of n8n, a custom node, or has an invalid structure

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version: 1.62.6
• Database (default: SQLite): sqlite
• n8n EXECUTIONS_PROCESS setting (default: own, main): own
• Running n8n via (Docker, npm, n8n cloud, desktop app): npm
• Operating system: Ubuntu 22.04.5 LTS

instance information

Debug info

core

• n8nVersion: 1.62.6
• platform: npm
• nodeJsVersion: 18.17.1
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community
• consumerId: unknown

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

Generated at: 2024-10-30T17:07:30.430Z

[mariana-na]

Hi @FlorianMeyer ,

Welcome to the community!

This is definitely not supposed to happen. The Node.js version you’re on is a little old, but wouldn’t expect that to cause this.

I’d say first step would be to update to the latest (stable is fine) n8n version - 1.64.3 if you’re ok to do so. While you’re at it why not update Node.js too.

Let me know if that makes any difference and we’ll see from there.

Oh, and it’s never a bad idea to backup your work before updating versions.

[FlorianMeyer]

Thanks @mariana-na for your quick response. I also tried with Node.js version 20. So that does not seem to be the cause of the issue.

I tried updating from 1.57 to 1.64.3 and had this issue. Afterwards i restored my backup of the whole machine and tried updating step-by-step to see in which version might be a breaking change. That why i can say the issue started with version 1.62.6.

Today i updated to Node.js 20 and then updated n8n from 1.61.0 to 1.65.2 - same issue.
I also tried with Node.js 22 - same issue.

[Jon]

Hey @FlorianMeyer,

This shouldn’t happen as new versions of n8n can use older node versions if they didn’t we would see this kind of error a lot more.

I suspect the issue is actually with your environment and I think at some point you have either installed a bad community node or you have tried to install n8n-nodes-base with npm.

Can you share the output of

npm list -g --depth 0

I would also recommend using the Docker method for running n8n which contains everything you need and your local environment won’t be able to impact it running.

[FlorianMeyer]

Thanks @Jon, that helped me a lot!

Here is the output if anyone else has this error, too.

npm list -g --depth 0
/usr/lib
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] -> ./../../root/node_modules/psrApi
├── [email protected]
└── [email protected]

I uninstalled n8n-nodes-base by

npm uninstall n8n-nodes-base

removed 1038 packages, and audited 1 package in 4s

found 0 vulnerabilities

and:

npm uninstall n8n-nodes-base -g

removed 798 packages in 5s

After that i could update to the latest version by

npm -g up

and now everything is working fine again.

Thank you!