Coolify deployment problems

[matisportowiec]

Hey,

I have a Coolify n8n + Postgress instance and it runs good.

I was trying to add a backup flow and now I can’t make it work.

My errors:

[ { "exitCode": 0, "stderr": "", "stdout": "Permissions 0644 for n8n settings file /home/node/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.\nUser settings loaded from: /home/node/.n8n/config\n\nThere is a deprecation related to your environment variables. Please take the recommended actions to update your configuration:\n - N8N_RUNNERS_ENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a future version. Please set N8N_RUNNERS_ENABLED=true to enable task runners now and avoid potential issues in the future. Learn more: https://docs.n8n.io/hosting/configuration/task-runners/\n\nAborting execution as a filesystem error has been encountered while creating the output directory. See log messages for details.\n\nFILESYSTEM ERROR\n====================================\nEACCES: permission denied, mkdir '/backups/04-14-25/credentials/temp/'\nError: EACCES: permission denied, mkdir '/backups/04-14-25/credentials/temp/'\n at Object.mkdirSync (node:fs:1372:26)\n at ExportCredentialsCommand.run (/usr/local/lib/node_modules/n8n/dist/commands/export/credentials.js:44:34)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at ExportCredentialsCommand._run (/usr/local/lib/node_modules/n8n/node_modules/@oclif/core/lib/command.js:302:22)\n at Config.runCommand (/usr/local/lib/node_modules/n8n/node_modules/@oclif/core/lib/config/config.js:424:25)\n at run (/usr/local/lib/node_modules/n8n/node_modules/@oclif/core/lib/main.js:94:16)\n at /usr/local/lib/node_modules/n8n/bin/n8n:71:2" } ]

I’ve tried adding those as Coolify enviromental variables, but with no lock. I’ve accessed the n8n terminal and tried to set it like:

export N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true
export N8N_RUNNERS_ENABLED=true

But still the error is the same

[jcuypers]

Hi,

In order for the first error to go away you need to set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false

for the second error, is this output from a workflow script?

reg,
J.

[matisportowiec]

Hey, yes - this is what I am getting back after I try to export:

It worked for the env when I edited the docker deploy file. Still trying to fix the disk write though.

[jcuypers]

Hi, If the second error comes from a workflow there are two options :

1. either use backups/ instead of /backups (the first one would write into /home/node/ where you would have rights the other one on the root dir

(But still storing backups on the same machine would be weird)

2. map a local volume to /backups when the container is started.

Regards
J.

[matisportowiec]

Ok, I’ve managed to fix it with --output=/home/node/backups/.

Later it uploads to the Google Drive, so they are safe + easy to copy if needed. Thanks!

[jcuypers]

A mark as solution would be nice. Thanks