2 months ago
🚨 CRITICAL ISSUE - Need Urgent Help
Project: miarb-production (ID: bdf3c3b1-dc9c-4c57-ad5b-34f35ea7fd89)
Service: 8c85aba6-4906-450a-9a79-02bb540bc0b3
PROBLEM:
My service deploys successfully and logs show:
"[API] Online en puerto 3000"
BUT every HTTP request returns:
{"status":"error","code":404,"message":"Application not found"}
CONFIGURATION:
- Node.js 20.20.2 (.nvmrc)
- Express.js server (CommonJS)
- Procfile: web: npm start
- PORT environment variable set
WHAT I'VE TRIED:
- Multiple redeploy attempts
- Rewrote server.js with http.createServer
- Verified PORT env variable
- Cleaned node_modules and forced rebuild
- Different server configurations
The service shows as ONLINE in dashboard but routes aren't working.
Is this a known issue with Railway's routing/proxy layer?
#bug #404 #routing
1 Replies
2 months ago
Your service is deploying and running successfully, but it has no domain assigned to it, so there is no route for HTTP traffic to reach it. You can generate a Railway domain from your service's Settings under the Networking section, and requests will begin routing to your app once the domain is active.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago