Hey there! We've found the following might help you get unblocked faster:

• 📚 405 Method Not Allowed

• 🧵 405 Method Not Allowed

• 🧵 405 Method Not Allowed

• 🧵 405 Not Allowed Method

If you find the answer from one of these, please let us know by solving the thread!

Hello,

405 is the status code your application is returning, not our proxy.

I'll go ahead and open this up to the community so they can help you debug your application and or configuration.

Best,

Brody

Hello Brody,

Thank you for your reply. However, with all due respect, your conclusion is incorrect, and it contradicts the evidence from my browser's network logs.

The 405 error is no longer the primary issue. The primary issue is that all API requests from my frontend to my backend are now hanging indefinitely with a (pending) status.

Please see the attached screenshot from the Safari Network Inspector. It shows my frontend application making a simple GET request to https://melodycompare-backend-production.up.railway.app/api/health. As you can see, the request never completes. It does not receive a 405 error, a 200 success, or any other response. It hangs forever.

This is definitive proof that the request is being lost or blocked within Railway's networking layer before it ever reaches my application. If my application were returning an error, we would see that error code in the network log.

I have spent several days working with multiple AI assistants to perfect my application code and configuration according to your documentation. The problem is not with my application; it is with the Railway platform's inability to route traffic to my service.

Please escalate this ticket to a senior engineer and investigate your internal proxy logs for my project. Pushing this to the community is not an acceptable solution when the evidence clearly points to a platform-level failure.

Thank you.