hello i have a problem in n8n v2+
before up to n8n v2 i have n8n v1.
the problem on there is i have the same node, the same api but why the response its diferent between n8n v1 and n8n v2 ? v1 its complete and have return success, but v2 its return error why ?
can someone help me please
just info* the deploy n8n in railway
My structure n8n v1 in railway :
My structur n8n v2 in railway :
Hi @Agellls Be sure to have your worker configured correctly in queue mode. Make sure that the binary property name in your HTTP Request node is the same as what your previous node returned. If there are issues and you are on Railway, you may be experiencing differences between the API response of n8n v1 and n8n v2. Although i never have experienced this kind of issue when updated to v2, let me know if that helps.
Hi @Agellls !
In n8n v2 the execution model changed to a distributed architecture.
Binary data now needs to survive serialization and worker execution.
On Railway, without shared persistent storage, binary files may be lost between the webhook and the HTTP Request node, which explains why the same workflow works in v1 but fails in v2.
Use N8N_BINARY_DATA_MODE=filesystem and ensure shared persistent storage volumes (Railway typically does not support this reliably)
i try add like this in worker and primary n8n. and i try again the return still same its show error

@Agellls In version one, everything was run in one process. In v2 with queue / worker mode on Railway, the webhook and the HTTP node run on separate containers. These two containers don’t share the same filesystem. Exceptionally, even if N8N_BINARY_DATA_MODE = filesystem, it may be the case that the worker does not see the file created by the webhook upload. To double check, try to run v2 temporarily in regular (no-queue) mode on a single service. If it works there, then the issue is the distributed setup, which would require either shared storage between primary/worker or a different storage strategy for binaries.
@Agellls
try
EXECUTIONS_MODE=regular
N8N_BINARY_DATA_MODE=filesystem
N8N_BINARY_DATA_STORAGE_PATH=/tmp
N8N_RESTRICT_FILE_ACCESS_TO=/tmp
2 Likes