502 Error then Lost All Workflows After Restore & Restart on Render (self-host) – Need Urgent Help

Hi Community,

I’m a beginner with n8n and self-hosting. Yesterday, I ran into a major problem with my n8n instance on Render. I have already submitted a support request to Render.com (I’m on a Pro plan), but it’s been over 12 hours and I haven’t received any response. I hope someone here might be able to help or share similar experiences.

  1. The issue started yesterday while I was running a workflow to upload image files to Google Drive. Suddenly, a message appeared in the dashboard about a server connection problem. I tried refreshing the page, but after that I only saw a 502 error.
  2. I used Render’s “Restore a disk” feature to restore from the most recent backup (from that same day).
  3. After the restore, I restarted the service.
  4. When I opened the link to access my n8n dashboard, I was prompted to set up n8n as if it was a brand new instance (asking for name, email, password, etc.).
  5. After logging in, I discovered that all my old workflows, credentials, and data were missing—the dashboard was empty like a fresh install.
    6.This logs and error messages (including “Exited with status 134”) for reference.
    Logs : Instance failed: x7wfs
    Exited with status 134 while running your code. Check your service logs for more information.
    June 14, 2025 at 6:05 PM

Has anyone experienced this kind of issue?
Is there any way to recover my previous workflows and data?
I would really appreciate any advice or guidance. I’m still waiting for a reply from Render, but I wanted to check here in case anyone else has ideas or solutions.

Additional Info:

  • n8n is self-hosted on Render.
  • I purchased a 1GB disk and my instance type is 0.5 CPU, 512 MB RAM.
  • I set the disk mount path to /home/node/n8n (following a course/tutorial), but later found out the official documentation recommends /home/node/.n8n.
  • There was no downtime or issue reported on Render’s status page at the time.
  • The problem occurred specifically during a workflow uploading images to Google Drive.

Thank you so much for any help!
Jo

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