Could not insert node 'n8n-nodes-base.manualTrigger' is an unknown node type

[muharihar]

Describe the bug
After installing n8n 0.222.0 i got an error:

Could not insert node 'n8n-nodes-base.manualTrigger' is an unknown node type

To Reproduce
Steps to reproduce the behavior:

1. Install n8n 0.222.0
2. Click "+" on Workflow Editor to add new node.
3. Choose node Manually.
4. See error

Expected behavior
The node n8n-nodes-base.manualTrigger should be added succesfully.

Environment (please complete the following information):

• OS: MacOS Big Sure1.7.4
• n8n Version: 0.222.0
• Node.js Version:
• Database system: MySQL 8
• Operation mode: own

Additional context

• All node seems to be undetected (please see the attactment).

[Joffcom]

Hey @muharihar,

I have just given this a go and I am not able to reproduce it, Are you seeing any errors in the browser console or in the n8n logs? Are you also running n8n from source, docker or npm?

[Joffcom]

Hey @muharihar,

Do you have any community nodes installed?

[nebulade]

We also see this when trying to package version 0.222.0 for Cloudron. It seems no nodes are available at all. Maybe this is related to 161de11 ?

[muharihar]

Hey @muharihar,

I have just given this a go and I am not able to reproduce it, Are you seeing any errors in the browser console or in the n8n logs? Are you also running n8n from source, docker or npm?

I'm running using npx.

npx n8n@0.222.0

[muharihar]

Hey @muharihar,

Do you have any community nodes installed?

No, i don't have any community node installed. (fresh install)

[Joffcom]

What version of node are you both using?

[ftpman]

Hello from Brazil.

Same case here.

I just run again npx n8n@latest start which updates it from 0.221.2 to 0.222.0.
The node version is v18.13.0.

Test on another machine (with node version v16.20.0) results in same.

[Joffcom]

@ftpman can you tell me anything else about your setup? Are you running on Windows / Mac / Linux? I have just been trying to reproduce it with no luck, My last thought was maybe the npm version as 16 is recommended but with a clean install on 16 or 18 it appears to be working.

[Joffcom]

@nebulade it could be that PR but I would expect all installs to stop working so there is something specific that is causing it, What environment options are being set?

[ftpman]

@ftpman can you tell me anything else about your setup? Are you running on Windows / Mac / Linux? I have just been trying to reproduce it with no luck, My last thought was maybe the npm version as 16 is recommended but with a clean install on 16 or 18 it appears to be working.

I tested on Linux CentOS 8 with npx and SQLite, and another Linux CentOS 7 with npm install and mariadb.

[ftpman]

@nebulade it could be that PR but I would expect all installs to stop working so there is something specific that is causing it, What environment options are being set?

Linux CentOS 8
DB_TYPE=sqlite npx n8n@latest

[Joffcom]

@ftpman any other options set? When you did the install did you also set up user management or did you skip that?

[nebulade]

Here it runs with node v18.12.1 and npm v8.19.2.

env vars are:

ENV N8N_USER_FOLDER="/app/data/user"
ENV N8N_CONFIG_FILES="/app/data/configs/default.json"
ENV N8N_CUSTOM_EXTENSIONS="/app/data/custom-extensions"

and we install it as https://git.cloudron.io/cloudron/n8n-app/-/blob/master/Dockerfile
where does the app expect the built-in nodes to be found?

I see that node_modules contains the following n8n related packages:

n8n/
n8n-core/
n8n-design-system/
n8n-editor-ui/
n8n-nodes-base/
n8n-workflow/

[ftpman]

@ftpman any other options set? When you did the install did you also set up user management or did you skip that?

@Joffcom I skiped user management and not enabled authentication.

[Joffcom]

@nebulade what options are set in the configs/default.json?

[nebulade]

There is only the database object set:

{
  "database": {
    "type": "postgresdb",
    "postgresdb": {
      "host": "postgresql",
      ....
    }
  }
}

Is there anything I could adjust to maybe get more debug logs from the app, where it looks for nodes?

[Joffcom]

Good news, I have just reproduced the issue. Nodes typically would be loaded into memory from the nodes-base on startup.

[Joffcom]

For now I would recommend downgrading to 221.2 or 220.1 until this has been resolved.

[nebulade]

ah great, let us know if there is anything to test then.

[Joffcom]

Will do, For now we have pulled that release.

[0x9fff00]

For now we have pulled that release.

That seems to have caused the latest Docker image tag to not have an ARM build (this has happened before, see #5164)

[janober]

Exactly, I was expecting that to happen but it was the lesser of two evils.

[Joffcom]

Afternoon,

The fix for this issue has been merged and will be available in the next release. For now I am going to mark this as closed and if this is still an issue in 0.222.1 once released let me know and we can open it again.

[nebulade]

Great, I can confirm it is working again now as expected. Thanks!

[ftpman]

That's right, it worked here too.
Thanks!

[janober]

Got released with n8n@0.221.1

[janober]

Fix got released with n8n@0.222.1