1. My Railway custom domain returns `405 Method Not Allowed` specifically for `PUT` requests, while the default `.up.railway.app` domain handles them correctly. 2. Is there any platform-level edge routing or security configuration that restricts `PUT` methods for custom domains on Railway?

Inngest 405 errors - Railway Central Station

Inngest 405 errors

Anonymous

HOBBYOP

2 months ago

My Railway custom domain returns 405 Method Not Allowed specifically for PUT requests, while the default .up.railway.app domain handles them correctly.
Is there any platform-level edge routing or security configuration that restricts PUT methods for custom domains on Railway?

$10 Bounty

2 Replies

Status changed to Awaiting Railway Response Railway • 2 months ago

Anonymous

HOBBYOP

2 months ago

It's Urgent Please anyone help

ilyass012

FREE

2 months ago

hey,

based on railway's official docs a cause of 405 on railway is using http instead of https , railway does a 301 redirect from http to https and that causes the client to downgrade the request method. worth checking if the url inngest is using for your custom domain has https:// explicitly, because the .up.railway.app url probably already does; source: https://docs.railway.com/networking/troubleshooting/405-method-not-allowed

note that tjis docs specifically mention post requests but the underlying cause (301 redirect) applies regardless of method, so it's worth trying before digging deeper

Welcome!