Cannot access n8n after update - 404 Page Not Found + Restart fails with 500 error

Questions
1

Hi everyone,
I was running n8n version 2.4.8 on my VPS (Cloudfy) and tried to update to the latest version (2.9.0).
Since the update, I cannot access the n8n interface anymore - I get a “404 Page Not Found” error.
When I try to restart n8n from the Cloudfy panel, I get this error:
“Failed to restart infrastructure: 500 - {“error”:“Could not apply changes”}”
I tried rolling back to version 2.4.8 but the restart still fails with the same 500 error.
The status shows “Running” but the interface is completely inaccessible and my workflows are not executing.
Has anyone experienced this issue? Any suggestions on how to fix it?
Thanks in advance!

2

Hi @caiojun

That 500 “Could not apply changes” error isn’t coming from n8n—it is the Cloudfy control panel failing to execute server commands.It is a server routing issue on their platform.

You need to open a ticket directly with Cloudfy support and let them know the dashboard is failing to restart your infrastructure.

hope this will help!

1 Like
3

Thanks @A_A4 !! I’m trying to contact Cloudfy because it really is their problem. Best

1 Like
4

yeah this is definitely a Cloudfy platform issue, the 500 error on restart is their infrastructure layer not n8n itself. while you wait for their support you could ask them to check if there’s a port conflict or if the container got into a bad state during the update, sometimes these managed platforms need to manually clear out the old container before the new version can spin up properly. if they can give you SSH access that would let you debug more directly but on managed VPS platforms you’re usually stuck waiting for their team unfortunately

5

Tks a lot mate! Im just waiting for the solution on vps platform! Should fix in the next few days!

6

Hi @caiojun!
Please mark the answer as the solution that helped you solve this issue, it helps others find the answer more easily and also supports community contributors.

7

Just to let you guys know, the vps platform sent me this:

”The cause of the 404 error was instability in an update due to a global interruption in AWS services that occurred last week, impacting thousands of companies worldwide.”

It get back to normal today!

Thanks guys

1 Like
8

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