Fresh install says Could not insert node 'n8n-nodes-base.scheduleTrigger' is an unknown node type

[Michal_Hantl]

Describe the issue/error/question

On a fresh install via npm package I get this:

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

Although in the menu the schedule trigger is there so that seems weird.
When I installed it through docker on my other computer it worked fine.

Please share the workflow

Just adding the above node to an empty workflow.

Information on your n8n setup

• n8n version:
  0.222.0

• Database you’re using (default: SQLite):
  SQLite

• Running n8n with the execution process [own(default), main]:
  own I guess

• Running n8n via [Docker, npm, n8n.cloud, desktop app]:
  npm

[Jon]

Hey @Michal_Hantl,

Welcome to the community

Can you tell me a bit more about your setup? Are you accessing n8n through localhost or through a reverse proxy?

Do you also have user management enabled or any community nodes installed?

[Michal_Hantl]

I simply did the npx n8n thing and got that error in the canvas when trying to add the simple node.

I’m accessing the app through localhost.

I also updated the n8n package just to make sure and npm is at v18.

Do you also have user management enabled or any community nodes installed?

No idea, I did not do any further setup beyong installing n8n globally and running it.

[Michal_Hantl]

Maybe this is a good time to learn about debugging n8n.
Don’t worry about this too much as it seems too weird to happen out of the box.
We can keep the post open just in case it happens to more than me.

[Michal_Hantl]

Just checked the app again and everything is missing - checking a template looks like this:

This might be interesting to debug if you want. Maybe be something wrong during install or wrong dependencies… Let me know what commands do you want me to run.

In the meantime I’ll be using the docker image which seems to be working.

[Jon]

Can you try using Node 16 to see if you get the same issue?

[Jon]

Hey @Michal_Hantl,

Have managed to reproduce the issue and we have pulled that release for now. Best bet would be to use the last version of n8n.

[jan]

Sorry, we had some problems with our release comment workflow. The fix for that issue got released a while ago with 0.222.0. Please check with the latest n8n version.