4 days ago
Domain: www.honeymoonfactory.org - service web, project honeymoon-factory (2efe20fa-d903-4832-8c6f-0eee920967df), US West.
Stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for 15+ hours. API dnsRecords show requiredValue == currentValue (dotirms0.up.railway.app) with DNS_RECORD_STATUS_PROPAGATED, yet the edge still serves the fallback *.up.railway.app certificate. The Railway-generated domain (web-production-11230.up.railway.app) works fine (200).
Verified externally: letsdebug.net = zero problems for http-01; certspotter = NO certificate ever issued for this hostname; CNAME target resolves; /.well-known/acme-challenge/ reaches the edge; no CAA records.
Already tried: multiple delete/re-add cycles (updating the GoDaddy CNAME each time, TTL 600) and the moderator clean protocol (remove DNS record + domain, wait 15 minutes, re-add). Still stuck.
Several similar threads opened today (custom domain stuck validating, stale edge state, ERR_SSL_PROTOCOL, CloudFront TLS failures) - looks platform-side. Please force certificate issuance or clear the stuck internal state for this hostname. Thanks!
3 Replies
4 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 4 days ago
4 days ago
You need to add a TXT record to _railway-verify.www.honeymoonfactory.org. You can get the content for it from the verificationToken property under status.
4 days ago
UPDATE — the TXT fix worked for the certificate, but the hostname is still not routed. After adding the TXT record railway-verify.www with the verificationToken, the certificate issued within minutes (now CERTIFICATE_STATUS_TYPE_VALID, Let's Encrypt cert served for www.honeymoonfactory.org — thank you!). However every request with Host: www.honeymoonfactory.org still returns the edge fallback 404 "Application not found" (server: railway-hikari, x-railway-fallback: true). Probed directly: the same request against the domain's CNAME target (41zh0vpu.up.railway.app) and against the service domain (web-production-11230.up.railway.app, which serves 200 under its own host) both return the fallback 404 — so the hikari routing table simply has no entry for this hostname. Already tried: multiple redeploys after VALID, customDomainUpdate, customDomainIssueCertificate, and a full delete/re-create of the custom domain (new id 8481f8f6-a310-441e-8857-3d711fe7f227, DNS updated + PROPAGATED, cert VALID again). RAILWAY_PUBLIC_DOMAIN env even shows www.honeymoonfactory.org. Could you force a routing/edge sync for www.honeymoonfactory.org -> service 510dbf12-7476-49f8-9432-7e2e51ce71d8 (project 2efe20fa-d903-4832-8c6f-0eee920967df)? Thanks!