Cloudron Forum

8Gb for this instance, more than enough, especially knowing that nothing has changed in terms of workflows and stuffs. The 4.23.x is stable though.

nope, nothing more than what I showed you. Here is the full log (quite short...), the server loops on this over and over.

2026-05-26T00:00:10.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.212:5678
2026-05-26T00:00:12Z 
2026-05-26T00:00:12Z 
2026-05-26T00:00:12Z Node loader n8n-nodes-base is already registered.
2026-05-26T00:00:12Z Error: Node loader n8n-nodes-base is already registered.
2026-05-26T00:00:12Z Error: Node loader n8n-nodes-base is already registered.
2026-05-26T00:00:12Z Error: Exiting due to an error.
2026-05-26T00:00:12Z Exiting due to an error.
2026-05-26T00:00:12Z Initializing n8n process
2026-05-26T00:00:12Z at /app/code/bin/n8n:63:2
2026-05-26T00:00:12Z at /app/code/bin/n8n:63:2
2026-05-26T00:00:12Z at /app/code/bin/n8n:63:2
2026-05-26T00:00:12Z at CommandRegistry.execute (/app/code/src/command-registry.ts:82:4)
2026-05-26T00:00:12Z at CommandRegistry.execute (/app/code/src/command-registry.ts:82:4)
2026-05-26T00:00:12Z at CommandRegistry.execute (/app/code/src/command-registry.ts:86:25)
2026-05-26T00:00:12Z at LoadNodesAndCredentials.init (/app/code/src/load-nodes-and-credentials.ts:111:11)
2026-05-26T00:00:12Z at LoadNodesAndCredentials.init (/app/code/src/load-nodes-and-credentials.ts:111:11)
2026-05-26T00:00:12Z at Start.catch (/app/code/src/commands/start.ts:435:14)
2026-05-26T00:00:12Z at Start.exitWithCrash (/app/code/src/commands/base-command.ts:231:28)
2026-05-26T00:00:12Z at Start.init (/app/code/src/commands/base-command.ts:124:3)
2026-05-26T00:00:12Z at Start.init (/app/code/src/commands/base-command.ts:124:3)
2026-05-26T00:00:12Z at Start.init (/app/code/src/commands/start.ts:211:3)
2026-05-26T00:00:12Z at Start.init (/app/code/src/commands/start.ts:211:3)
2026-05-26T00:00:15Z ==> Ensure directories
2026-05-26T00:00:15Z ==> Setting permissions
2026-05-26T00:00:15Z => Installing https@1.0.0
2026-05-26T00:00:16Z found 0 vulnerabilities
2026-05-26T00:00:16Z up to date, audited 2 packages in 507ms
2026-05-26T00:00:16Z ⠙⠹⠸⠼
2026-05-26T00:00:16Z ⠼
2026-05-26T00:00:16Z ⠼==> Starting N8N
2026-05-26T00:00:19Z Last session crashed
2026-05-26T00:00:20.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.212:5678
2026-05-26T00:00:29Z

The only thing I can found is slightly different from yours, although it touches some n8n node package I don't know.

*2026-05-26T00:01:05Z ⠼==> Starting N8N
2026-05-26T00:01:08Z Last session crashed
2026-05-26T00:01:10.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.212:5678
2026-05-26T00:01:18Z 
2026-05-26T00:01:18Z 
2026-05-26T00:01:18Z Node loader n8n-nodes-base is already registered.
2026-05-26T00:01:18Z Error: Node loader n8n-nodes-base is already registered.
2026-05-26T00:01:18Z Error: Node loader n8n-nodes-base is already registered.
2026-05-26T00:01:18Z Error: Exiting due to an error.*

@dev-cb I cannot update my instance and try as prod workflows are running. But I have another instance which migrated to 2.24.0 without any trouble. The only difference between the two is the presence of NODE_FUNCTION_ALLOW_BUILTIN=* on the first one (the one that crashes).

I have the exact same issue since yesterday. The migration to 4.24.0 crashes the server.