Hey guys,
My GitHub workflow was running smoothly for a while until one day it stopped working. I can’t remember doing anything special that day. Could it have been an update to an n8n version?
In any case, I can’t find a solution. I’ve already looked through several posts on the subject and watched all the relevant videos again, but I’m still stuck.
Your request is invalid or could not be processed by the service
n8n version: 2.2.6 (self hosted)Running n8n via: (self hosted on hostinger)
This is a known issue and is caused by how n8n v2 handles binary data in combination with how the github node processes this data.
It got fixed with version 2.3.0:
master ← belyas:fix/23334-fix-github-node-filesystem-base64-content
opened 05:04PM - 20 Dec 25 UTC
## Summary
This pull request fixes issue #23334, where improper content is sent… to GitHub due to the filesystem-based storage strategy.
When binary data is stored using the `filesystem-v2` mode, `BinaryDataService` sets the data field of the `binaryData` object to the storage mode string itself, while the actual buffer is persisted to disk. In this case, the resolved file path is stored in the id field of the `binaryData` object.
This change adds a safeguard that detects when `binaryData.id` starts with the `filesystem-v2:` prefix. In such scenarios, the data field is not meaningful and should be ignored. Instead, the implementation retrieves the actual binary buffer using the `getBinaryDataBuffer` utility and converts it to `Base64`, which is the format expected by GitHub.
Example of used repository for testing: https://github.com/belyas/test/blob/main/test.txt
<img width="1409" height="692" alt="Screenshot 2025-12-20 at 21 33 51" src="https://github.com/user-attachments/assets/0da5a81e-5649-49c6-933d-dc4ad481f79b" />
## Related Linear tickets, Github issues, and Community forum posts
Issue number: 23334
Fixes #23334
## Review / Merge checklist
- [x] PR title and summary are descriptive. ([conventions](../blob/master/.github/pull_request_title_conventions.md))
- [ ] [Docs updated](https://github.com/n8n-io/n8n-docs) or follow-up ticket created.
- [x] Tests included.
- [ ] PR Labeled with `release/backport` (if the PR is an urgent fix that needs to be backported)
If you can’t/don’t want to upgrade yet, here is a detailed description on how to get around this issue in your current version:
3 Likes
Thank you very much! I have updated the version and not its working again!
system
January 20, 2026, 8:32pm
4
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
