a month ago
Custom domain https://www.theforgeapp.io returns Railway “Application failed to respond” (HTTP 502, header x-railway-fallback: true).
The service domain works (200):
https://the-forge-v2-production.up.railway.app
Service: the-forge-v2
Environment: production
Region: US West
Request IDs:
- xi2BWuTFT3-hamQH2h0iww
- 1RFRTkpmTiuiyAqBLPU1MQ
DNS (GoDaddy):
CNAME www → current Railway target (vvwzi60.up.railway.app / whatever is shown in Networking)
App:
- Start command: node dist/index.js
- Listens on port 8080
- Custom domain mapped to port 443
- Logs show the process started and the default Railway URL serves traffic
DNS, certificate, and domain verification appear correct. Refreshing the custom domain often does not produce an application request log, which looks like the edge proxy never reaches the container.
This matches other reports where “edge routes were not installed,” causing 502 fallback on the custom domain only. Please check/repair edge routing for www.theforgeapp.io.
1 Replies
a month ago
Your custom domain's target port is set to 443, while your app listens on 8080 (which is why the service domain works). In your service's networking settings, change the target port for the custom domain to 8080 and the 502 will resolve.
Status changed to Awaiting User Response Railway • about 1 month ago
23 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 23 days ago