Problem with node Github - N8N_DEFAULT_BINARY_DATA_MODE=filesystem

Questions
1

Hi, I have a problem with the GitHub node when trying to save a file. The problem started appearing when I added this variable to my docker-compose.

N8N_DEFAULT_BINARY_DATA_MODE=filesystem

I’m working with large files, and thanks to this, there’s a noticeable improvement in performance. However, some scenarios stopped working.

An error message about an invalid format (base64) appears.

image
image1253×640 23.3 KB

If I remove this variable filesystem and restart the n8n instance, everything starts working again, there are no error messages.

Does anyone have any suggestions on what I can change to fix this?

Thanks!

Information on your n8n setup

  • n8n version: 1.82.3
  • Database (default: SQLite): Postgres
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
2

I have not tested, but based on the error I would assume you must convert the file contents to base64.

Try this node:

2 Likes
3

Thanks for the response, I can use the node you mentioned - and it will work, using the http node and directly querying GitHub and transmitting the file will also work.

However, I would like to know why using filesystem causes errors, but using the memory storage system does not.

Could it be a bug in the GitHub node?

1 Like
4

So, filesystem will now be default and memory storage will be deprecated. (I believe)

Filesystem mode will only output a relative path if trying to access the binary object. Memory storage will provide the file data. It’s inefficient at large scales.

This will become default and main way to access file objects:

1 Like
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.