2 months ago
Hi,
A custom domain has been stuck on CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
for several hours, even though Railway itself reports the DNS record as
PROPAGATED and matching.
Domain: social.wptaskify.com
Service: social-api
Project ID: dfe71e11-3a37-4829-92f6-f55738b46853
Environment: 291400f2-8f10-4023-8eb9-de1f1bdc21ca
Account: logicaldottech@gmail.com
What the API reports:
certificateStatus : CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
dnsRecord status : DNS_RECORD_STATUS_PROPAGATED
requiredValue : yxen3ai4.up.railway.app
currentValue : yxen3ai4.up.railway.app (matches)
What I verified independently:
-
The CNAME resolves correctly from 8.8.8.8 and 1.1.1.1 to yxen3ai4.up.railway.app
-
There is no CAA record on wptaskify.com, so Let's Encrypt is not blocked
-
HTTPS to the domain returns the default *.up.railway.app certificate,
so no cert has been issued for it
-
I had the same problem on a second domain (different registrar and different
DNS provider) before deleting it, which suggests it is not DNS-side
I have already tried redeploying the service. Could you force certificate
issuance for this domain?
Thanks.
Pinned Solution
2 months ago
You need to add a TXT record on _railway-verify.social.wptaskify.com. If you’re using the API, you can find the content for the record from the verificationToken property under status.
2 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
You need to add a TXT record on _railway-verify.social.wptaskify.com. If you’re using the API, you can find the content for the record from the verificationToken property under status.
2 months ago
Thanks that was it. The TXT record was the missing piece. The certificate has
been issued and social.wptaskify.com is live now.
Status changed to Solved mayori • 2 months ago