a month ago
Two custom domains across two projects have been stuck at certificate provisioning since June 10, despite verified-correct DNS: portal.homehandpro.com (project 8a618a55-3781-43c1-8002-41b0592563ff) and app.homehandpro.com (project b5300225-3396-4e37-ad72-844821382694). CNAMEs are propagated and confirmed matching (DNS_RECORD_STATUS_PROPAGATED in the API), HTTP routes correctly to your edge (the ACME challenge path returns from your edge), no CAA records, no DNSSEC. Deleting and re-creating both domains issued new targets but certificates remain unissued; the edge still serves the *.up.railway.app wildcard for SNI on both hostnames. Please investigate certificate issuance for these domains.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 26 days ago
a month ago
I have a domain from GoDaddy, but when I connected it to Railway, and I go to the domain vibemusic.site, it still redirects me to the original one where it says railway.app. How can I fix it? I just want my domain to be visible.
Status changed to Solved acbrown123 • 26 days ago
a month ago
Solved: the missing piece was the _railway-verify. TXT record with the value from the API's status.verificationToken. Note this record does NOT appear in status.dnsRecords — that list shows only the CNAME, which is misleading. Thanks @onyillto - found your answer on another thread.
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Solved acbrown123 • 26 days ago