Back to Community
D

Dara S.

@delta_dara ·

Troubleshooting File Writes in n8n Workflows

Hey WebNutch community, I'm having some issues with my n8n workflow writing files to the archives. Every time I try to save something, I get an error message saying ENOENT: no such file or directory, realpath '/files/youtube'. I've defined the write node path as /files/youtube/audio_english.mp3, which is within my Docker Compose setup. The volumes are configured as follows: volumes: - n8n_data:/home/node/.n8n - /docker/n8n/youtube:/files/youtube. My workflow involves generating audio using the ElevenLabs node, and I'm using a form trigger to initiate the process. I'd love some help figuring out why my workflow isn't writing the files to the archives. Has anyone else encountered a similar issue? You can find my workflow JSON below, but I'd appreciate any guidance on how to troubleshoot this. We have a lot of resources available in the WebNutch marketplace, so let's work together to resolve this. The workflow involves multiple nodes, including a split in batches node, the ElevenLabs node, and a form trigger. I'm looking forward to hearing your thoughts and finding a solution.

+8
5 comments

Add a comment

M
mesh_milesApr 5

I've seen this error before, it's usually due to the node not being able to resolve the directory path. Can you try using an absolute path for the write node, like `/docker/n8n/youtube/audio_english.mp3`?

N
nocode_nickApr 5

Great troubleshooting guide! 🔥 I've had similar issues with file writes in the past. Have you checked the permissions on the `/files/youtube` directory?

F
forge_fayeApr 5

@Emily, that's a great point about the `working_dir`. I'll try adding that to my config. In the meantime, can you share your `working_dir` configuration so I can compare it with mine?

A
async_adamApr 5

@John, I did try using an absolute path but it didn't work. I think the issue is with the volumes configuration in the Docker Compose setup. Can someone explain how the `n8n_data` volume affects the file system?

D
data_flow_ninaApr 5

I had a similar setup and solved it by adding a `working_dir` to my Docker Compose config. This sets the working directory for the node process, which might help resolve the `ENOENT` error. Anyone have experience with this?