N8n unable to start after new update

Questions
1 
TypeError: Missing parameter name at 7: https://git.new/pathToRegexpError
2025-11-23T15:56:28.302754271Z     at name (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:153:13)
2025-11-23T15:56:28.302757234Z     at lexer (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:168:21)
2025-11-23T15:56:28.302759444Z     at lexer.next (<anonymous>)
2025-11-23T15:56:28.302762059Z     at Iter.peek (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:188:32)
2025-11-23T15:56:28.302764131Z     at Iter.tryConsume (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:195:24)
2025-11-23T15:56:28.302766416Z     at Iter.text (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:213:26)
2025-11-23T15:56:28.302768568Z     at consume (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:285:23)
2025-11-23T15:56:28.302770707Z     at parse (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:320:18)
2025-11-23T15:56:28.302772711Z     at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:503:40
2025-11-23T15:56:28.302774989Z     at Array.map (<anonymous>)

After updating my n8n instance using coolify, the n8n service is unable to start and returns this error.
I checked the n8n database on psql, the webhook related urls looks correct. I am not sure how to resolve this error.

Has anyone faced any similar issues?
If there is insufficient information please let me know. I can provide more information.

2

The error message “Missing parameter name” suggests an issue with how n8n is parsing a URL path, possibly related to a webhook. Since you’re using Coolify, the update process might have introduced a conflict.

You could try rolling back to your previous n8n version to see if that resolves the issue. If that works, then you can try updating again, but this time, carefully review the release notes for any breaking changes or configuration adjustments that might be needed.

If the problem persists, sharing your n8n version and any custom configurations you have would be helpful for further troubleshooting.