Environment:
- n8n 2.1.x (self-hosted, npm)
- Windows
- n8n running as a Windows service
- File access restricted via N8N_RESTRICT_FILE_ACCESS_TO
- UNC network share (SMB), e.g. \192.168.x.yyyyyy\folder…
Problem:
The “Read File(s) From Disk)” node returns 0 output items with no error
when reading files from a UNC network share, even though:
- The file definitely exists
- The UNC path is whitelisted
- The same path works with Execute Command (PowerShell ReadAllBytes)
- No permission error is thrown
- “Always Output Data” is enabled
Example:
Path:
\192.168.x.zzhdgfh\folder\…\file.xlsx
Result:
- Node executes successfully
- No binary output
- No error details
- Downstream nodes receive 0 items
Workaround:
Reading the same file via Execute Command using PowerShell
([IO.File]::ReadAllBytes) works reliably, including for files with
spaces and accented characters.
Question:
Is this a known limitation or bug of the Read File(s) node
with UNC paths / SMB shares on Windows?
Is there a recommended way to make the node reliably read files
from network shares when n8n runs as a Windows service?