2 months ago
My Reverb (WebSocket) service returns 502 with 'connection dial timeout' errors specifically on WebSocket upgrade requests (Connection: Upgrade), while regular HTTP GET requests to the same service/port succeed instantly. CPU and memory are near-idle during the failures. Target Port is correctly set to 8080, matching the container's bind port shown in deploy logs. Confirmed with an independent WebSocket client (not just my app) — same failure. Service: reverb-production-03eb.up.railway.app
Attachments
Pinned Solution
2 months ago
Try adding a custom start command to your service. If it's online, it should say "Online" instead of "Completed."
1 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
Try adding a custom start command to your service. If it's online, it should say "Online" instead of "Completed."
Status changed to Solved medim • 2 months ago