Cloud Instance Down - 502 Bad Gateway for 6 days & Magic Link not arriving

Questions
1

Hi, my n8n instance hosted via Cloudfy has been down for 6 days with a 502 Bad Gateway error. The cloud status dashboard says running, but I cannot access my workflows. Also, I am trying to request a Magic Link to the admin panel using my email, but I am not receiving any emails (checked spam too). Can anyone from the support team help me check if the instance is frozen or restart it?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hi @Nutri_Alana_Soares

Please reach out to Cloudfy for help.
Magic Link will not work as you did not subscribe to n8n cloud

3

Since it has already been 6 days, I’d update the existing support ticket (instead of opening multiple new ones) and include:

  • workspace URL

  • account email (privately)

  • exact error message

  • timestamp of latest failure

  • whether API/editor/admin panel are inaccessible

Hopefully support can inspect and restart or recover the instance directly.

4

I’ve already done that, I always write in the same ticket, but I don’t get a response… my customer workflow is blocked because I don’t have a solution

5

Stalled customer flow changes priority: this isn’t a workflow adjustment, it’s instance recovery.

Without exposing email or workflow, leave the ticket with a straightforward checklist: “all instance routes return 502, including editor/API, and the Magic Link isn’t arriving; I need you to confirm if the container/process is alive behind the proxy and restart or recover the instance”. If any route is still responding, post here only the status/error of that route. If everything is 502 for 6 days, only Cloudfy can unlock it from the infrastructure side.

6

@Nutri_Alana_Soares 6 days with client workflows stopped is critical, escalate it.

In your existing ticket, be very specific:

“All routes return 502, including editor and API”

“Magic Link emails are not arriving”

“Request: confirm if the container is running behind the proxy and restart/recover the instance”

Also note: Magic Link won’t work here because this is Cloudfy, not n8n Cloud, so only Cloudfy support can restart the instance on their infrastructure. Keep pushing on that ticket and mark it as business-critical.