17 days ago
My Railway service is deployed successfully and listens on port 8080,
but the Railway-generated domain returns:
HTTP 404
x-railway-fallback: true
Application not found
Domain:
portfoliodaniel26-production.up.railway.app
The service deployment is successful and the target port is 8080.
A curl OPTIONS request to /api/login also returns the Railway fallback
instead of reaching my Express application.
Request ID:
3oaVFHJmQKuVZKML8u2xcg
Could you please check the edge routing/domain binding for this service?
Pinned Solution
17 days ago
There isn't a problem with your service, it's working correctly. You just had a typo in your URL.
9 Replies
17 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 17 days ago
17 days ago
Make sure the service is online and healthy, and that you've got the URL correct.
Status changed to Solved danielloliveira17 • 17 days ago
17 days ago
eu apertei errado, nao resolveu ainda
Status changed to Open Railway • 17 days ago
17 days ago
The service is online and the latest deployment is successful.
The service is listening on port 8080 and the Railway-generated domain is:
https://portfoliodaniel26-production.up.railway.app
However, requesting the URL returns:
HTTP 404 Not Found
x-railway-fallback: true
{"status":"error","code":404,"message":"Application not found"}
I also tested the endpoint with an OPTIONS request, and it returns the same Railway fallback instead of reaching my Express application.
Request ID:
3oaVFHJmQKuVZKML8u2xcg
Could you please check whether the generated domain is correctly routed/bound to my service?
17 days ago
Can you click on your service, and show the exact URL displayed?
Attachments
17 days ago
yes, what´s a problem??
danielloliveira17
yes, what´s a problem??
17 days ago
There isn't a problem with your service, it's working correctly. You just had a typo in your URL.
Status changed to Solved 0x5b62656e5d • 17 days ago