15 days ago
Status check done — here's where things stand:
Certificate status: unchanged. pilot.trailstock.co still reads "validating ownership," and the custom URL still doesn't answer. (My deployment-status query had two syntax/schema stumbles along the way, but I got the answer I needed anyway.)
One new data point worth having: I confirmed the pilot service itself is healthy right now — the generated Railway address just returned HTTP 200. That rules out the last plausible non-support explanation I hadn't checked: Railway's proxy refusing to issue a certificate because the backend behind it is down. The backend is up and serving; only the domain validation is stalled.
So the picture is exactly as documented in runbook §16: fresh domain object attached, DNS matching Railway's requirement exactly and confirmed resolving at independent resolvers, validation requested repeatedly, service healthy, plan upgraded — and Railway's validator still hasn't moved. That's now ~25 hours across three object generations with every controllable input verified.
The Railway support ticket remains the one action that can unstick this — the timeline in the runbook is current through this check, so it's ready to paste. Meanwhile the pilot keeps running fine on its temporary address, and the moment Railway moves I'll re-add the wildcard and verify the custom URL end to end.
5 Replies
15 days ago
Your CNAME is propagated and pointing at the correct target, but the TXT ownership-verification record is missing, which is why the certificate is held at "validating ownership." Add a TXT record at the host _railway-verify.pilot (your DNS provider appends the zone) with the value railway-verify=4a5e90d8e9c6f5ef4b4e94d86b82855cafeb4094bb43de99c00a4a9a136d8a78. Verification and certificate issuance resume automatically once that record propagates.
Status changed to Awaiting User Response Railway • 15 days ago
15 days ago
❌ pilot.trailstock.co is still not in the config — no custom domains showing yet
Still appears to be stuck on validation
The support ticket is your path forward. Have you heard back from Railway's support team yet on that thread you filed? They should be able to manually re-validate the domain or investigate why the validator is stuck.
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
The domain is attached to your service and ownership verification has passed. The certificate is not stuck on validation - it has hit a Let's Encrypt rate limit from repeated issuance attempts, so new attempts will fail until that window clears. Once the rate limit resets, issuance should proceed automatically since your CNAME is correct and verification is complete.
Status changed to Awaiting User Response Railway • 15 days ago
15 days ago
*.trailstock.co is stuck in validation. What needs to happen?
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
The wildcard domain is attached to your service and the traffic CNAME is propagated correctly, but the ownership-verification TXT record at _railway-verify is missing entirely, so verification cannot pass and no certificate can issue. Add a TXT record with the host _railway-verify (your DNS provider appends the zone) and the value railway-verify=e55f97191906cc5388ce92582bb4725881500788ac5fed46acb09b2e3a92988c. Verification and certificate issuance resume automatically once that record propagates.
Status changed to Awaiting User Response Railway • 15 days ago
8 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 • 8 days ago