Describe the problem/error/question
Hi everyone,
I’m preparing for the upcoming n8n v2 file-access restrictions, and I noticed something that doesn’t seem to behave consistently.
In the Migration Report, nodes that use absolute paths (for example /tmp/...) are flagged with this warning:
“File Access Restrictions”
To prevent this, I added the environment variable:
N8N_RESTRICT_FILE_ACCESS_TO="/tmp/"
I expected the warning to disappear, just like what happens with other migration warnings (for example NODES_EXCLUDE, which disappears once the env variable is set).
However, even after setting N8N_RESTRICT_FILE_ACCESS_TO, the Migration Report still shows warnings for nodes using /tmp/.
So my question is:
Should the Migration Report detect that /tmp/ is explicitly allowed in the environment variable, or is this warning expected to remain even when the directory is whitelisted?
I want to make sure that in n8n v2 my workflows will not break, since many nodes temporarily write or read files in /tmp/.
What is the error message (if any)?
Migration Report warning:
File Access Restrictions - Medium
File access is now restricted to a default directory for security purposes
This warning appears even though the directory /tmp/ is explicitly included in N8N_RESTRICT_FILE_ACCESS_TO.
Please share your workflow
or
Information on your n8n setup
- n8n version: 1.120.4
- Database (default: SQLite): Default
- n8n EXECUTIONS_PROCESS setting (default: own, main): Default
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker (Coolify deployment)
- Operating system: Linux on Coolify (Linux f2bf47cbb8bf 6.8.0-64-generic #67-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15 20:23:31 UTC 2025 x86_64 Linux)
DOCKER COMPOSE:
environment:
- N8N_RESTRICT_FILE_ACCESS_TO=“/tmp/”
- N8N_DEFAULT_BINARY_DATA_MODE=filesystem