3 months ago
Hi,
After I upgraded to Metal Edge, Stripe Webhooks returns a timeout.
This is strange and really hard to debug though, because my manual request using Postman seems to work just fine.
Does anyone have any idea what could have been the problem in this case?
2 Replies
3 months ago
maybe this is something you want to get in contact with stripe for?
3 months ago
Hey , brody , can you help me , with this issue pls
https://station.railway.com/questions/unable-to-connect-to-the-mysql-workbench-7a532fab
kaliappan20
Hey , brody , can you help me , with this issue plshttps://station.railway.com/questions/unable-to-connect-to-the-mysql-workbench-7a532fab
3 months ago
Please do not hi-jack other people's threads.
Yeah this is really strange, it just seems as if Stripe wouldn't connect to the service if the Metal Edge is enabled
3 months ago
let me know how it goes!
so here's the thing… I used the domain since like probably more than a year ago.
back then, when a domain is assigned to a service, I wasn't asked (or maybe I didn't choose) on which port that I need to set for that domain
now, I click on the "edit" button on the domain assignment in the service option…
and I simply updated the domain option to use the port that is detected by Railway, like so:
now it works without any problem, Stripe was able to reach the webhook endpoint hosted on my service on Railway without any timeout
I wasn't sure why my domain was online and reachable even if there was no port number assigned to it, but it seems to work ok now
3 months ago
glad you solved it
3 months ago
awesome
3 months ago
!s
Status changed to Solved brody • 3 months ago