Deploy failed on Render

Questions
1

Hey n8n team.
I am using Render to seld host n8n.
All my builds are failing since April 8.
Never had a problem before. Plus the error is misleading because there is enough memory. I even cranked up the resource and it still fails.
Can you please help?

Screenshot_2025-04-18_at_4.51.19_PM
Screenshot_2025-04-18_at_4.51.19_PM1340×681 113 KB

2

Hi,

Did you (or they) upgrade the N8N software recently? Or do you fix your n8n versions manuallyy

Reg
J.

3

Hi. The only thing I tried to do was adding some node js packages. So I added these following env vars but the first time I did it, it deployed successfully and the package was available.
This last successful deploy was on April 4th.
Then I tried on April 9th to add another node.js package and this is when it started to fail.
I thought it was the reason it was failing, so I removed all node.js package, synced my n8n fork, redeploy and since then I have this issue.
I also tried to upgrade the instance itself thinking it was a memory issue, and it didn’t help at all.
I also don’t have heavy processes running 24/7 there.

4

Hi, not sure what the best approach is. you are using stable versions right? Not like dev releases.

Personally I would revert back to the last known working / stable and restart from there.

I think troubleshooting these issues is best done with n8n

Reg
J.

5

Hi. I am simply update my fork repository with n8n-io/m8n:master
I tried redploying in on a fresh install and same problem happens.
I rolled out to the last commit that worked and it does not fail (test(Gmail Node): Add tests for Gmail node v1 (no-changelog) (#12461))

6

@jcuypers Hey Jiri, have you seen my past message?

7

I experience exactly the same error. The only thing I did is synced my forked repo and now it does not build.

I’ve reverted to old version. And it builds all good.

Working commit that i’m using right not: ad29235
Not working commit: c6ceee2

8

Hi, just exprienced the same error here. synced forked repo, does not build, exactly the same errors in the screenshots above. Also self-hosted on render. Any updates or resolution to this?

9

update: Resolved the error deployment by:

  1. Adding a new environment variable: NODE_OPTIONS = --max-old-space-size=2048
  2. Modifying the build command from pnpm install to pnpm install --prefer-offline, to use local cache to save memory/build time.

Able to deploy and live successfully thereafter.