2 days ago
Custom domain certificate issuance is stuck platform-side. Domain: luna.teamjoyce.com, project Luna 2.0 (857db10a-8993-4f10-89b4-a3670cc281c0), service ui (593baf4c-c02e-4d04-acf7-8f42ca1f6e06), env 7b15feda-0f03-41f1-975b-ed20576adc61. Domain was added/deleted 3 times over 12 hours (July 4 22:00 UTC – July 5 11:00 UTC); every attempt sat in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP indefinitely while your API showed the CNAME as DNS_RECORD_STATUS_PROPAGATED (target 68pl9c3t.up.railway.app). Independent evidence it's not on my side: Let's Debug test #3046705 (http-01) returns fully issuable — no CAA, no DNSSEC, edge reachable; and crt.sh shows zero Let's Encrypt orders ever finalized for this hostname during the window. Previous host (Vercel) released its domain claim mid-window; no change. The domain is currently removed while I await your fix — please check your cert worker/order state for this hostname and tell me when it's safe to re-add.
Attachments
1 Replies
2 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 2 days ago
2 days ago
You need to add a TXT record for _railway-verify.luna.teamjoyce.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.