<![CDATA[n8n persistent frontend cache grows across updates and inflates backups]]>On Cloudron 10.0.4 with the current n8n package 4.42.3 (n8n 2.38.7), I found that:
/app/data/user/.cache/n8n/public/assets had grown to 4.5 GB and 82,398 files, while the PostgreSQL database was only 15 MB.

After stopping n8n, deleting the generated public cache and restarting:

  • app data: 4.5 GB ā†’ 76 MB
  • cache files: 82,398 ā†’ 1,565
  • n8n started normally and /healthz returned HTTP 200

It appears that n8nā€™s generateStaticAssets() copies newly hashed frontend assets into its persistent cache on every update without removing assets from previous versions. Since the Cloudron package persists the user home under /app/data/user, these stale files are also included in every backup.

Could the package clean /app/data/user/.cache/n8n/public before starting n8n, or is there another intended solution?

]]>https://forum.cloudron.io/topic/15967/n8n-persistent-frontend-cache-grows-across-updates-and-inflates-backupsRSS for NodeSat, 19 Sep 2026 07:33:15 GMTTue, 15 Sep 2026 21:12:28 GMT60<![CDATA[Reply to n8n persistent frontend cache grows across updates and inflates backups on Tue, 15 Sep 2026 22:08:19 GMT]]>Hello @pathab
Thanks for reporting. We will look into it.

]]>https://forum.cloudron.io/post/129495https://forum.cloudron.io/post/129495Tue, 15 Sep 2026 22:08:19 GMT