YouTube Upload Node Works on n8n Cloud, But Fails with 400 Error on Railway

aiautobargain
HOBBY

3 days ago

Hi,

I’ve encountered a persistent issue with the YouTube upload automation in n8n.

  • When I run the exact same workflow on the official n8n Cloud (the 15-day free trial), everything works perfectly and the YouTube video uploads without any problems.

  • However, when I deploy the same workflow on Railway (self-hosted), I always get a 400 error from the YouTube upload node (or even when using direct HTTP requests).

Troubleshooting already attempted:

  • Set N8N_DEFAULT_BINARY_DATA_MODE=filesystem

  • Checked all YouTube node parameters (title, description, privacy, category, etc.)

  • Verified OAuth authentication and reconnected the Google account multiple times

  • Restarted and redeployed the Railway service

  • Ensured the binary file is valid (downloads and plays fine)

  • Tried both YouTube Node and direct HTTP request (resumable upload) methods

  • No issues with other nodes or services in the workflow

But:
The error only occurs on Railway.
It never happens on the official n8n Cloud.

Questions:

  • Is there a known issue with Railway (or similar cloud platforms) and the n8n YouTube node/binary file handling?

  • Are there any additional settings or workarounds to make YouTube uploads work reliably on Railway?

Any advice or guidance would be greatly appreciated.
Thank you!

Solved$10 Bounty

2 Replies

Railway
BOT

3 days ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

Railway

Hey there! We've found the following might help you get unblocked faster: - [🧵 N8N - Google API Oauth: Access blocked: authorisation error 400: invalid_request](https://station.railway.com/questions/n8n-google-api-oauth-access-blocked-8fcc96ce) - [🧵 Error 400 in Google Cloude](https://station.railway.com/questions/error-400-in-google-cloude-99457ec5) - [🧵 Failure of Inbound Webhook POST's - Not Reaching Service Container (Printify -> n8n)](https://station.railway.com/questions/failure-of-inbound-webhook-post-s-not-da223a89) If you find the answer from one of these, please let us know by solving the thread!

aiautobargain
HOBBY

2 days ago

Thank you for your response.
However, I’ve already checked and verified all of these basic points:

  • OAuth credentials and permissions are set up correctly.

  • All node parameters (title, description, category, etc.) have been thoroughly checked.

  • The binary file downloads and plays fine.

  • The error only occurs on Railway. The same workflow works perfectly on n8n Cloud and local environments.

  • Environment variables (including N8N_DEFAULT_BINARY_DATA_MODE=filesystem) are properly configured.

  • I have also tried re-authenticating the Google account and redeploying the service multiple times.

These are all basic troubleshooting steps that have been covered.
If there are any advanced suggestions or specific known issues with Railway and YouTube uploads in n8n, I would appreciate more detailed guidance.

Thank you!

Status changed to Solved aiautobargain • 2 days ago

Status changed to Solved chandrika • about 15 hours ago

YouTube Upload Node Works on n8n Cloud, But Fails with 400 Error on Railway - Railway Help Station