Cloudron Forum

Beware: The latest release/update changes the license.

https://github.com/nocodb/nocodb/discussions/12891

They're moving to a Sustainable Use License.

I don't think I've changed much if any of our stock cloudron-n8n instances, and here's what our migration report is saying about upgrading to v2.

Does anyone else want to share theirs? You can find it under Settings > Migration Report > Instance Tab

Do any of the staff use n8n on a daily basis? There are quite a few architectural (and breaking) changes being introduced with 2.0. It's definitely going to need to be tested heavily before deployment. Which raises a good question, if someone has auto update enabled in Cloudron, will 2.0 be automatically deployed or will it require manually updating via Cloudron? Could wake up to a lot of unhappy customers.

Also note, I am waiting for 9.0.14 to be stable release before I can update and then download a backup. Currently it's not possible to download a backup in 9.0.13 from Cloudflare R2.

Just an update - I have changed absolutely nothing but I'm seeing the nightly backup size get smaller.

@joseph said in Bloated n8n backup:

du -hcs .

Sorry, I misread this. I navigated to cd app/data/ and it's 906MB. My other post was running that from app/code

Actually I'm going to hold off on updating to 9.0.14 because I don't want to risk it turning into a different problem. I'll wait for 9.0.14 to come out of pre-release or do it this weekend when activity is low.

@joseph said in Bloated n8n backup:

du -hcs .

I get 1.5G.

Be mindful since posting the above I have restarted my Cloudron instance which had been up (for 5 days) since automatically updating to 9.0.13.

Cloudflare won't let me download files over 1G directly so I'll look to update to 9.0.14 now.

When I try to download the backup from the Cloudron interface I get this error:

{
  "status": "Conflict",
  "message": "only tgz backups can be downloaded"
}

Is this because they are encrypted? .tar.gz.enc

I will try the Cloudflare UI. But still curious to understand why that error occurs.

@Joseph yes, the size matches.

There appears to be no rhyme or reason to these backup sizes after updating. Nightly is showing a smaller file size now.

The reason it is noticeable is updating an app is taking 15-20 minutes because of the snapshot+upload to Cloudflare R2. 6GB takes a lot longer than 800mb.

It looks like they will continue to bug fix v1 while v2 is distributed. How is that going to be handled by the Cloudron updater? Will we be able to stay on v1 with Cloudron if we don't want to or cannot upgrade to v2 but need the v1 patches?

Just got auto-updated to Cloudron 9.0.13 a few weeks ago and my n8n backups have gone absolutely bonkers.

They jumped from a consistent 800MB-1GB range to 6.37GB. File count stayed the same (5877 files), so something else is getting backed up now.

Dug into the container and found /usr is 2.8GB and /app is 2.4GB - that's basically the entire 6GB right there.

Did something change with backup scope in Cloudron 9? Is this a known issue? My backup storage costs just tripled overnight for what looks like redundant system files that shouldn't be in there.

Anyone else seeing this?

@nebulon given the significant issues that are cropping up with n8n breaking things with each release, how do we ensure we only pull the latest stable from GitHub which is where issues are raised and tracked? I've switched to manual updating because of breaking changes that come up from time to time.

@Joseph this is why I posted in support.

Hi team,

I've noticed that Cloudron keeps pulling pre-release versions of n8n?

Is there a setting somewhere to stop this and only pull latest versions?

@imc67 said in Per-application access rules:

@umnz said in Per-application access rules:

@imc67 I'm not sure what you mean, Cloudron does have a Trusted / Blacklisted IPs and Fail2Ban support.

https://docs.cloudron.io/security/

You are answering your own question: look at the subject of this future request and then the docs. What you mentioned is on server level .... not app level

Oops, my bad! Take my +1 instead lol.

@nebulon thanks for the insights.

Is it normal for Postgres to look like this all the time? It was like this at 256, 512, 1GB and now 4GB of RAM. The system information doesn't match the RAM allocation that's being reported.

@imc67 I'm not sure what you mean, Cloudron does have a Trusted / Blacklisted IPs and Fail2Ban support.

https://docs.cloudron.io/security/

What are your thoughts on removing the app proxy limit as a vehicle to help market/promote Cloudron and get people into the ecosystem?

@Package-Updates @girish I checked the n8n repository and 1.108.1 is pre-release? Any reason that got picked up by the package updater as stable/latest?