Youtube Upload node issue in Railway

Questions
1

I have n8n template deployed in my railway and having issues with my workflow that has a Youtube Upload node. there are only 2 main nodes in my workflow.

  • First is trigger,
  • 2nd is the Http Get node for the mp4 file which outputs into binary,
  • Third is the Youtube Upload node.
    Credentials are okay. There’s a ‘ghost’ upload in my youtube channel for the video after execution - with the description and title each time I run it but YT does not receive the video. I get the error after execution (error on the YT Upload node)

Converting circular structure to JSON → starting at object with constructor ‘TLSSocket’ | property ‘_httpMessage’ → object with constructor ‘ClientRequest’ — property ‘socket’ closes the circle

I’ve tried different things, like setting 2 variables in my Primary instance. and adding a Code node between my Http Get and YT Node to only output the binary.data

To add, this same workflow works on the n8n cloud version. Is there a bug with this node in Railway or am I missing something?

Added 3 variables as suggested by chatgpt
N8N_BINARY_DATA_MODE
filesystem
N8N_DEFAULT_BINARY_DATA_MODE
filesystem
N8N_EXECUTIONS_PROCESS
own

  • n8n version: 1.86.1
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own, main (not sure)
2

Hi @Patz Welcome to n8n :n8n: community :tada:

Without a sample workflow or the errors you’re encountering—it’s a bit difficult to provide specific help.

Could you share a sample of your current workflow and maybe a small snippet of the data you’re working with? That would help a lot!

3

Screenshot of the error.Maybe this is a generic error which if it is, I’m not sure what the exact one would be.

image
image357×194 12.6 KB

4

I’m having the exact same problem, works fine on n8n cloud platform, fails to upload YouTube after deploying to railway. railway’s hosting IP is shared, and if someone else ever hosts a flagged project on the same IP, your new domain will be implicated as well; I’m trying to proxy the domain with Cloudflare so the IP will be out of railway. But it hasn’t worked so far. Maybe we can try this together!