Hi Railway Support Team,

I'm requesting a refund for my $5 Hobby plan payment. Here's the situation:

ISSUE SUMMARY:

• Paid for Railway Hobby plan ($5/month) to deploy a Node.js WebSocket server

• Deployment shows as "successful" in Railway dashboard

• Application logs show server starts correctly and responds to internal requests

• However, the external URL consistently returns "Application failed to respond"

TECHNICAL DETAILS:

• Repository: mindhud/TESTE1GLOBAL (TesteUpserver folder)

• Server listens on 0.0.0.0 with process.env.PORT

• Health endpoint (/health) works internally but not externally

• Same exact code works perfectly on Render.com

EVIDENCE:

• Deploy logs show "SERVIDOR WEBSOCKET INICIADO COM SUCESSO"

• Internal health checks pass: "TESTE LOCAL: Servidor responde OK"

• External access fails: Railway's own error page appears

• This appears to be a Railway infrastructure issue (proxy/load balancer)

RESOLUTION ATTEMPTED:

• Multiple redeployments

• Code modifications for Railway compatibility

• Different configurations

• Issue persists despite "successful" deployments

Since the service doesn't work as expected and this appears to be a platform issue rather than code issue, I'm requesting a full refund of the $5 charge.

Thank you for your assistance.

COMPETITOR COMPARISON:
To verify this wasn't a code issue, I deployed the exact same codebase to Render.com as a test. The application worked perfectly on the first attempt - no modifications needed. This confirms the issue is with Railway's infrastructure, not the application code.

Since a competitor can successfully run the same code without any issues, this demonstrates that Railway's platform has a technical problem that prevents proper service delivery.