504 Gateway Timeout on Webhook Calls – Investigation Request

sejodjoseonHOBBY

10 days ago

We are encountering an issue with incoming webhook requests from an external e-signature provider to our Railway-hosted API.

Context:

  • Service function: Our API receives webhook callbacks notifying us of signature status updates.

  • Recent issue: The signature provider reports that their webhook requests are now consistently returning a 504 Gateway Timeout from our endpoint.

  • Manual testing: When we simulate the same request manually (e.g., using curl) from a local machine, the webhook responds correctly and the API behaves as expected.

  • Hosting setup: The API is deployed on Railway, and the webhook URL is publicly accessible.

Questions:

  1. Could Railway’s infrastructure or edge gateway be selectively returning 504 errors depending on the origin IP or region?
    We’d like to understand if there’s any throttling, blocking, or timeout rules based on origin that could explain this discrepancy (working from curl but not from the provider).

  2. Is there any way for us to access gateway-level or platform-level logs (beyond our app logs) to check whether:

    • The request is reaching our instance at all.

    • It is being blocked, timed out, or dropped before hitting our service.

Any support or insights would be greatly appreciated =)

Solved$10 Bounty

2 Replies

brodyEMPLOYEE

10 days 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 • 10 days ago

lofimitHOBBY

10 days ago

I know that Railway doesn't usually do IP or region-based blocking or throttling by default. Your plan is pretty solid for this kind of service so I don't think it has anything to do with your server's resources, they would have to bomb your service or have a really small timeout limit for it to be consistent.

Could it be that the other server is blocking or ignoring requests coming from Railway’s IPs or doesn’t like something in the request headers Railway sends?

I could try helping more but extra information and debugging would be needed. Try adding logging at the start of your webhook handler to see if requests arrive, create a simple test endpoint on Railway for them to call to check if it’s your app or the network, and if no logs show up for those webhooks, they’re probably blocked before reaching your app.

sejodjoseonHOBBY

8 days ago

Thanks for the support – the issue is resolved!
As I suspected, it turned out to be a problem on the signature provider's side. Everything is working fine on Railway’s end
I just had to make sure the issue wasn’t on my side.
Appreciate your help!

Status changed to Solved chandrika • 8 days ago