17 days ago
Service name: Rizin-Your-Pesonal-Life-Coach Project ID: c00fb7a9-33fd-4930-9893-67d434fbbb70 Service ID: 4b5ac656-6602-4b82-a826-4b26538af065
The app is running correctly on port 8080 — deployment logs confirm "serving on port 8080" with no errors. Internal networking shows green. However the public URL https://rizin-your-pesonal-life-coach-production.up.railway.app is not accessible — returns connection error.
Steps already taken:
- Verified PORT=8080 in environment variables
- Redeployed multiple times
- Restarted the service
- Removed duplicate domain entry
- App logs are clean with no crashes
This appears to be Railway's public proxy layer not routing traffic to the running container. Please investigate urgently — this is a production app with active users.
2 Replies
Status changed to Open Railway • 17 days ago
17 days ago
Something I'd try is to make the application listen to an arbitrary port (eg, 3000), and make the URL map to 3000 as well and see if it fixes anything.
0x5b62656e5d
Something I'd try is to make the application listen to an arbitrary port (eg, 3000), and make the URL map to 3000 as well and see if it fixes anything.
17 days ago
App returns 502 after successful deployment. DNS is correct (Cloudflare proxying to 0me57ir7.up.railway.app). Static assets load with 200 but the main document returns 502. App logs show "serving on port 8080" successfully but then the database connection pool gets exhausted during migrations. We serialized the startup tasks in the latest deploy (completed 30 min ago) but still getting 502. Railway internal networking shows green. Logs show no crash but the public proxy returns 502. What else can we check?
Status changed to Solved edriss19000 • 17 days ago