Railway re-deployments break community nodes

Questions
, ,
1

Hi everyone,

I’m having issues with my n8n deployment on Railway. Every time I re-deploy my n8n instance, to get the latest updates, I log in and the community nodes are broken, I need to manually install them all again. Am I doing something wrong? Is there another way to update the n8n instance within Railway that doesn’t break the community nodes? Thank you!

2

Hi @didac_fg, can you please try adding this variable to your ENV list:

N8N_REINSTALL_MISSING_PACKAGES=true

This happens because community nodes are installed directly on the hard disk, and when the n8n instance starts up, it can’t find them. Setting that environment variable tells n8n to automatically reinstall any missing files, including your previously installed community nodes (during startup).

3

I got the re-deployments working by using the variable you suggested.

But, do you know how to use the n8n suggested approach of persisting the contents of the ~/.n8n/nodes directory in Railway as per their support page - Troubleshooting | n8n Docs?

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.