2 months ago
Hi!
I'm not familiar with Railway, but seems that we've got some clients trying to push webhook data from us to Railway, but we're hitting 413 Payload too large.
I can't find any documentation on any maximum size constraints (nor whether this is something our customers can configure or not).
Would have to handle this case for Railway separately then (as e.g. Zapier, Freckle, n8n and others have not had any problems with payload sizes).
Best,
Arnold
Pinned Solution
2 months ago
Hey, Railway doesn't impose a platform-level request body size limit that would cause a 413, this error is coming from the application itself.
Could you share the tech stack of the application receiving the webhooks? You can explicitly increase the size limits depending on the framework you're using (express, nginx, django...)
2 Replies
Status changed to Open Railway • about 2 months ago
2 months ago
Hey, Railway doesn't impose a platform-level request body size limit that would cause a 413, this error is coming from the application itself.
Could you share the tech stack of the application receiving the webhooks? You can explicitly increase the size limits depending on the framework you're using (express, nginx, django...)
2 months ago
If you are using next.js server actions, you need to specify the max bodySizeLimit in your next.config.ts . By default, the maximum size of the request body sent to a Server Action is 1MB.
/** @type {import('next').NextConfig} */
module.exports = {
experimental: {
serverActions: {
bodySizeLimit: '2mb', // adjust the size limit as needed
},
},
}Status changed to Solved Anonymous • about 2 months ago