Re-install community nodes after restart?

[Ian_Gillis]

Describe the problem/error/question

When I restart my docker container (dyno on Heroku), it always says there is an error with a community node I’ve installed. The db doesn’t change before/after restart as far as I can tell.

It can be fixed by re-installing the community node, but I don’t want to require a manual step every time the application restarts

What is the error message (if any)?

Please share your workflow

n/a

Share the output returned by the last node

n/a

Information on your n8n setup

• n8n version:
• Database (default: SQLite): PostresQL
• n8n EXECUTIONS_PROCESS setting (default: own, main): main
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system:

[n8n]

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:

[aya]

Hi @Ian_Gillis, could you maybe share your docker setup? And what version of n8n are you suing?

[Ian_Gillis]

I just used the Heroku setup that n8n published: GitHub - n8n-io/n8n-heroku

It looks like that’s pulling latest from DockerHub – is it possible that’s the issue? Something like:

• Heroku does a nightly restart (or similar)
• There’s almost always a new version of latest
• For some reason, upgrading resets your installed community nodes

Mostly just conjecture, I don’t know how community node installation actually works.

[Ian_Gillis]

Read through the code and I still don’t fully understand why the package/node is considered missing. It looks like the db is consistent.

But I did find this config N8N_REINSTALL_MISSING_PACKAGES so going to try setting it and see if that helps.