HI,
I'm a newby with NAS in general and computer usage.
I have a terramaster F2 425 and have installed some apps, with docker-manager and docker-engine.
My issue is that I'm unable to use the n8n "Read/Write to file" node because the Nas doesn't allow it, example of error message received in n8n = The file "/data_n8n_echange/test.txt" is not writable.
I have tried multiple times to create a file from the n8n application without success, I have checked the folder permissions and even tried giving chmod 777 to them, can someone please help.
Thank you in advance.
enable file creation from n8n worflow
Re: enable file creation from n8n worflow
Hi,
If this '/data_n8n_echange/test.txt' refers to the root directory of the NAS system, it is recommended that you move to the '/Volume[num]/folders/' directory to prevent filling up the root directory space and causing abnormalities.
You can also try adding PUID=0 to the container's environment variables to match your user.
If this '/data_n8n_echange/test.txt' refers to the root directory of the NAS system, it is recommended that you move to the '/Volume[num]/folders/' directory to prevent filling up the root directory space and causing abnormalities.
You can also try adding PUID=0 to the container's environment variables to match your user.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: enable file creation from n8n worflow
Hi and thank you for your answer.
No it's not a root directory, it's in /volume1/cabinet_psy/ sub folders, all the directories, under /volume1/cabinet_psy/, have been given RW to All users.
I'm able to create a file with SSH but the n8n node keeps on getting the error message mentioned in my original message.
By saying PUID=0 do you mean that by default the n8n will use ID 0 or do you mean I should first find out the id in my n8n container via terminal? I'm connected as an admin in the docker engine and at first I added user:root in my n8n container but it didn't solve the issue of writing from the workflow node.
Thank you once again for your help.
No it's not a root directory, it's in /volume1/cabinet_psy/ sub folders, all the directories, under /volume1/cabinet_psy/, have been given RW to All users.
I'm able to create a file with SSH but the n8n node keeps on getting the error message mentioned in my original message.
By saying PUID=0 do you mean that by default the n8n will use ID 0 or do you mean I should first find out the id in my n8n container via terminal? I'm connected as an admin in the docker engine and at first I added user:root in my n8n container but it didn't solve the issue of writing from the workflow node.
Thank you once again for your help.
Re: enable file creation from n8n worflow
You may consider providing the yml file to us for testing (via 'send private message').
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: enable file creation from n8n worflow
This usually happens when the Docker container running n8n doesn’t have proper write access to the mounted NAS folder. Even if the NAS folder has 777 permissions, the container user might still lack rights. Check your Docker volume mapping and ensure the folder is correctly mounted to /data_n8n_echange, and verify the container user ID (UID/GID) matches the NAS folder ownership.
Re: enable file creation from n8n worflow
It sounds like a permissions or volume-mount issue rather than just chmod. In Docker setups, n8n can only write to directories that are properly mounted and accessible inside the container. Make sure the /data_n8n_echange path is correctly mapped as a volume in your Docker configuration and points to a writable folder on your NAS. Also verify the container user has the right UID/GID permissions matching the NAS folder. Sometimes restarting the container after changes helps. Checking logs can also provide more specific clues about what’s failing.
