a month ago
railway up consistently fails at the upload step for my ~90MB payload, but the exact same payload deployed successfully last month.
Project: 6646a23b-27d3-4034-90c0-9574aff8b66d
Service: calculadora — 72379c29-6e38-463a-ab52-8d9507b6bef6
Error (5 consecutive attempts, 2026-07-16 between 22:46 and 22:58 UTC):
Indexing...
Uploading...
Failed to upload code with status code 500 Internal Server Error
Failed deployment IDs:
c40c1476-62ab-4213-87bd-3a868914ef45
e1368716-2142-464f-b14a-c515ecaee914
76fe09a5-74ae-4018-be6a-c49ea5a703e2
7cc0d874-7a2f-41d2-abc7-be1b38f2daca
db1dfa52-34d6-4656-920c-043d62bc8fb3
The payload: a Dockerfile plus a 98MB JAR and a 4.4MB SQLite file (~103MB raw, ~90MB as tar.gz).
This same payload deployed fine on 2026-06-21 via railway up from the same machine: deployment 0e2d3b6e-edde-42a1-8027-809c16ae7cae (SUCCESS, still RUNNING today). The JAR differs by only 415 bytes between then and now.
Size is the discriminator. From the same folder, service and CLI, I removed only the JAR (payload → 4.2MB) and the upload succeeded immediately, reaching the build stage: deployment 041493b1-96c1-47ae-a44c-36de24747dfc. It then failed at COPY api-regime-geral.jar, as expected, since I had removed that file.
Already ruled out:
CLI version — fails identically on 5.20.0 and 5.26.2
Command config — same error with --project/--service/--environment flags and with the directory linked
Network middlebox — my antivirus does TLS interception; I disabled it for one attempt and got the same 500
Platform incident — status page shows fully operational
Account/subscription — another service in the same project deployed successfully at 22:19 UTC the same evening
Question: is there a new size limit on railway up? I couldn't find one documented. If there is, can it be raised, or is there a recommended path for artifacts this size?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
There is no documented upload size limit for railway up, and your workspace's build image size limit (100 GB) is well above your payload. Your 90 MB compressed upload should work. As a workaround, you can avoid the CLI upload path entirely by deploying from a GitHub repository or by pushing a pre-built Docker image to a registry and deploying that image directly, both of which bypass the railway up upload step. If you reply with the outcome after trying one of those paths, we can dig further if needed.
Status changed to Awaiting User Response sam-a • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 27 days ago