Edge routing not propagated — custom domain returns "Application not found"
hhbtrust
PROOP

25 days ago

Edge routing for

corner-merchant.campintl.io is not

propagated.

Direct probe details:

$ openssl s_client -connect

corner-merchant.campintl.io:443 \

-servername

corner-merchant.campintl.io

Cert served: CN=*.up.railway.app

(Railway wildcard fallback)

Issuer: Certainly

Intermediate R1

$ curl -k https://corner-merchan

t.campintl.io/api/health

HTTP/2 404

x-railway-fallback: true

content: {"status":"error","code

":404,"message":"Application not

found"}

For comparison,

verdikt.campintl.io serves

CN=verdikt.campintl.io

correctly (its own provisioned

cert) and routes to its service.

Project ID: 2ace7e7a-d337-4a27-9

24c-fcdcee0b52b3

Service ID: e9e4d53e-8396-42dc-b

9d0-d7c42cf84a1d

Domain:

corner-merchant.campintl.io

CNAME target:

ceosqpzg.up.railway.app (DNS

verified globally)

Dashboard shows CERTIFICATE_STATUS

_TYPE_VALIDATING_OWNERSHIP for

12+ hours. The actual issue: edge

config never propagated for

this domain → service mapping. The

cert can't provision because

Railway's edge doesn't know to

route this hostname yet.

Need: edge config push for this

custom domain.

Solved$20 Bounty

Pinned Solution

domehane
FREE

25 days ago

Hello hhbtrust,

your cname is propagated which is good, but did you also add the txt record that railway shows in the dashboard? railway requires both the cname and the txt record for ownership verification, a missing txt record will cause exactly what you're seeing: stuck on validating ownership, wildcard fallback cert, and 404 with x-railway-fallback. check your dns provider and make sure that txt record is there too

Hope this help you :)

3 Replies

Status changed to Open Railway 25 days ago


domehane
FREE

25 days ago

Hello hhbtrust,

your cname is propagated which is good, but did you also add the txt record that railway shows in the dashboard? railway requires both the cname and the txt record for ownership verification, a missing txt record will cause exactly what you're seeing: stuck on validating ownership, wildcard fallback cert, and 404 with x-railway-fallback. check your dns provider and make sure that txt record is there too

Hope this help you :)


hhbtrust
PROOP

25 days ago

Amazing. I appreciate it.


Status changed to Solved mykal 25 days ago


hhbtrust

Amazing. I appreciate it.

25 days ago

In the interest of improving the platform for you and all other users, would you mind taking the time to let us know how we could have made this process clearer for you, specifically regarding the need to add the given TXT record to your domain?


Status changed to Awaiting User Response Railway 25 days ago


Railway
BOT

18 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 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...