a month ago
Hi Railway team 
I’d like to ask whether it’s possible to increase the maximum HTTP request timeout from 5 minutes to 15 minutes.
We’re running an upload endpoint (POST /upload) that occasionally handles large files (e.g. 500–600 MB stems). In some cases, the request fails with a 502 error after 5 minutes, even though the process continues fine locally.
Is it possible to extend the timeout limit to 15 minutes (manually or via config)?
Thanks a lot for your help! 
Attachments
6 Replies
a month 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!
a month ago
Hello,
The platform maximum HTTP request timeout is 15 minutes, any limit that is lower than that would be a self imposed limit at the application level.
I will open this thread up to the community so they can help you adjust that at the application level.
Best,
Brody
Status changed to Awaiting User Response Railway • 29 days ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 29 days ago
a month ago
Hi, thanks for quick response! I’m using Express (Node.js 20) for the upload service — it acts as a lightweight proxy that streams the request body directly to Sanity’s asset API. Looks like the 5-minute cutoff was caused by Node’s default server.requestTimeout (300 000 ms)
a month ago
Loudbook & Brody,
I’m running an Express service (Node.js 20). To make sure the app itself isn’t the culprit I’ve raised everything I can on the server side:
- req.setTimeout(15 60 1000)
- res.setTimeout(15 60 1000)
- server.requestTimeout = 15 60 1000
- server.headersTimeout = 15 60 1000 + 60_000
Despite that, every long upload still dies at the five‑minute mark. Example:
- requestId: JqTGrhSDTSispzM5PvyhXg
- service: beatsawer-development.up.railway.app
- edgeRegion: us-east4-eqdc4a
- timestamp: 2025-10-15T04:13:53Z
- method/path: POST /upload
- upstreamErrors: [{"error":"i/o timeout","duration":300000}]
- rxBytes: ~295 MB received before the proxy aborts
The handler never logs a timeout or abort on our side, so it looks like the edge/proxy is enforcing a 300 s cap. Could you double-check whether the effective HTTP request timeout in us-east4-eqdc4a is still 300 s, or let me know if there’s something else we should set to actually reach the 15‑minute limit? Happy to share more diagnostics if that helps.
Thanks!
a month ago
As mentioned, the HTTP request timeout on our end is 15 minutes, regardless of the region to which you are deployed.
Any limit lower than that would be a self-imposed limit at the application level; the application is certainly the culprit.