Hi. Thanks for the link.
But where/how to fix it in n8n config?
We recently introduced a new binary data mode which got created by @kik00. It no longer saves the binary data in the database as base64 encoded string, rather as files on the disk. You can give that a try.
It can activated by setting the environment variable:
N8N_DEFAULT_BINARY_DATA_MODE=filesystem
3 Likes
Thanks for this info!
It does help, to quite an extent (in e.g. HTTP/Google Drive nodes).
In some cases, still facing issues (in e.g. Compress/Decompress node).
@jan
Could you also tell how to now access the raw binary data in Function node?
Earlier, we used to be able to just access $binary.data.data or items[0].binary.data.data. But these options aren’t available now, apparently.
I do see an id in the data property but not the full local path of the file.
It can now be accessed via:
await this.helpers.getBinaryDataBuffer(itemIndex, binaryPropertyName)
1 Like
Hello everyone, I am jumping into this topic cause I am occurring the same error.
I am running the local version with npm.
My question is How can I edit the local file for fix this error?
thanks!
Hi @Gabriele_Bracciali, I am very sorry you’re having trouble 
Quite a bit of time has passed since this topic was last touched and it’s not fully clear to me what exactly you’re trying to change unfortunately. Perhaps you can open a new topic and provide all information required to understand and reproduce the problem you are currently seeing?
Thank you!
This was also added to another post so I have been working on it there, Will close this topic for now.
1 Like