19 days ago
My custom domain fplxp.cogs.tech (project e054a77e-7a74-4d7e-af0e-7b86f8ba9ed4, service fpl-xp, Hobby plan) has been stuck in VALIDATING_OWNERSHIP for ~24 hours, across three registrations (current domain id 6dd53bfa-2447-4274-8492-4cff706b615a).
Your API reports the CNAME as DNS_RECORD_STATUS_PROPAGATED (currentValue == requiredValue = bjvm3qfe.up.railway.app), with certificateErrorMessage/certificateErrorType both null — no failure recorded, it just never completes.
DNS is Cloudflare, DNS-only (grey cloud), identical to five working custom domains on this account. No CAA, no DNSSEC, no stale verification records.
Port 80 reaches your edge (301 with x-railway-edge); HTTPS serves the *.up.railway.app fallback cert; hostname routing hasn't activated (x-railway-fallback: true).
Possibly relevant: the service had App Sleeping enabled from creation, so it was asleep during most validation attempts. I've since disabled sleeping (service awake, serving 200s) — cert still pending so far.
I've already tried delete/re-add twice and a redeploy; aware of the LE duplicate limit so I've stopped retrying.
Looks like the certificate workflow is stuck and needs a manual kick — could someone take a look?
1 Replies
19 days ago
The CNAME for traffic routing is propagated correctly, but the domain is missing its TXT verification record, which is why verification has not completed and the certificate pipeline has not advanced. Both records are required. The TXT record host and value are shown in the domain's settings under your service's Networking section in the dashboard - publish that TXT record at your DNS provider (Cloudflare, DNS-only mode as with your other domains), and once it propagates, verification and certificate issuance will proceed automatically.
Status changed to Awaiting User Response Railway • 19 days ago
Status changed to Solved chriscogbill • 19 days ago