Preventing Data Loss During Self-Hosted Updates? Is there a solution for this?

Questions
1

Hi n8n community,

I’m running a self-hosted n8n instance on a cloud server on xcloud.host .

image
image2417×1319 180 KB

It works great, but I have an issue during updates.

When I update n8n from the platform the service is down for about 3-5 minutes. During this downtime window, any incoming data obviously will not go through.

image
image3261×1197 194 KB

This data loss is a problem for my critical automations.

Is there a simple, recommended solution or “best practice” for a self hosted setup to prevent this data loss?

For example, is there any way to externally queue requests while the container is restarting, or perhaps an n8n setting I’m missing that helps with this?

Thanks for any ideas or insights!

Razi

1 Like
2

Nobody? i’m sure i’m not the only one asking this? :sweat_smile:

3

hello @Adeative_Media

Well. Better to set n8n in queue mode with multiple main instances. Then you will be able to update them individually

Configuring queue mode | n8n Docs

4

If you’re using EasyPanel, it has built-in Zero Downtime Deployments,
it’s the easiest solution I know that works with standard n8n instances.

5

Thanks for the reply guys, so if i understand correctly i need to have 2 different n8n installed on my server?