6 days ago
Hello Railway Support Team,
I am writing to report a persistent platform-level networking issue with my healing-studio deployments and to request a refund or credit compensation for the resources wasted due to this error.
According to the automated diagnosis on my dashboard, my application starts correctly and binds to 0.0.0.0:8080, but your proxy fails to reach the container. The diagnosis explicitly states: "Contact Railway support, as this appears to be a platform-level networking issue."
Because of this platform-side proxy failure, I have had over 20 consecutive failed deployments, which has unnecessarily consumed my account resources and proxy fees.
Could you please help resolve the networking issue on this node and credit back the charges incurred from these failed healthcheck timeouts? I have attached a screenshot of the automated diagnosis for your reference.
Thank you.
3 Replies
6 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 6 days ago
aa0968111723-prog
4 days ago
Hello Railway Support Team,
I am writing to follow up on this thread regarding my healing-studio deployments.
I just deployed the same code to the US East region, and it deployed successfully. This completely confirms that the 20+ consecutive healthcheck failures were entirely caused by the proxy/networking issue specifically on your asia-southeast1-eqsg3a node, and not an issue with my application code.
Because my account resources and proxy fees were unnecessarily consumed by your platform's node failure in the Asia region, I am requesting a refund/credit compensation for those wasted failed deployments.
Additionally, although the deployment is now successful in the US East region, visiting my domain (director.today) shows an "Application Not Responding" error (Request ID: iPS5nlkMRm2ZooERo3UVLg). Could you please check if this is a DNS routing delay due to the region change, or if there is something else blocking the traffic?
Thank you for your help with the refund and checking the current routing issue.