Custom domain routing broken - 421 Misdirected Request / Application not found
tianqijiang
HOBBYOP

4 months ago

My service (project: Linkingknowledge, service: Linko Prod) is running normally (gunicorn up on port 8080), but all requests to both custom domains (linko.study, www.linko.study) and the default Railway domain (knowledge-circle-production.up.railway.app) return:

  • HTTP 404 {"status":"error","code":404,"message":"Application not found"}
  • Response headers show x-railway-fallback: true
  • Custom domain requests hit a Fastly/Varnish TLS certificate mismatch (421)

The application container is healthy — this appears to be an Edge Network routing issue. No configuration changes were made on my end. This started during the current Edge Network partial outage shown on status.railway.com.

Service ID: 7cf4eedb-ad52-4c14-b44b-12305cf1c921

Project ID: 3f3930d2-c272-4da5-a131-0c156df0fe76

Environment: production

Solved

2 Replies

4 months ago

Ack, looking into it right now.


Status changed to Awaiting User Response Railway 4 months ago


4 months ago

Seems like a Fastly <> CF issue


Status changed to Solved tianqijiang 4 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...