25 days ago
Service rsms-mall-api (ID 4a448250-bd8b-42c3-96e5-dbd9d4286dd9), deployment marked ACTIVE/successful, container starts and listens on the injected PORT (8080), not crash-looping, no healthcheck configured — but the public domain returns nothing (connection times out at the edge, no request ever reaches the container). Sibling service on the same account/region works fine. Regenerating the domain didn't help.
11 Replies
25 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 25 days ago
0x5b62656e5d
Can you share the URL?
25 days ago
domain : rsms-mall-api-production.up.railway.app , link: https://mall-app-kappa.vercel.app
25 days ago
I'm able to access the Railway URL just fine. Try using a VPN or 1.1.1.1 as DNS.
Attachments
0x5b62656e5d
I'm able to access the Railway URL just fine. Try using a VPN or `1.1.1.1` as DNS. 
25 days ago
I'm sorry I sent the working service , the problem is here rsms-mall-api-production.up.railway.app
0x5b62656e5d
That's the URL I accessed. the `/health` route returns `OK`.
25 days ago
no you accessed on ops not mall
25 days ago
The domain resolves to 69.46.46.73. That IP is unreachable — TCP connect hangs, no SYN-ACK — from my location (Egypt) and from an independent server on a different continent. Meanwhile rsms-ops-api-production.up.railway.app (69.46.46.33, adjacent IP, same account, same region) returns 200 in ~1s from both of those. It works from your side but not from at least two independent networks.
Regenerating the domain gave back the same 69.46.46.73. Can you check that edge IP, or move the service to a different edge node / region so it gets a fresh IP?
25 days ago
It's not client-side. I tested from three independent networks on different continents (my machine in Egypt, a US-based server, and a separate EU host) — all three can reach 69.46.46.33:443 (rsms-ops-api, same Railway account/region) but none can complete a TCP handshake to 69.46.46.73:443 (rsms-mall-api). A VPN just routes around a broken path; it doesn't explain why one of your edge IPs is unreachable from multiple networks while its neighbor isn't. Please look at 69.46.46.73 specifically, or migrate service 4a448250-bd8b-42c3-96e5-dbd9d4286dd9 to a new edge.
25 days ago
Not sure what else to say except you could be experiencing a regional/ISP block. I'm able to access your mall site just fine from Toronto, Canada.