a month ago
Hi Railway team - I migrated my services from my old account (kirby@flosys.ai, Hobby) to this new account (kirby@flosys.org) by re-creating the projects. Two custom domains will not issue certificates on the new account: hq.flosys.org and portal.flosys.org.
Both are attached to service "hq" in project flosys-hq on this account (project id 633f6cc8-bd62-4de1-8c93-5366d67f2522, service id 8d6f587d-3e21-471b-a293-3c8d934dd5ef, environment production). DNS CNAMEs at GoDaddy point at the new service's target, targetPort is 8080 and the domain shows syncStatus ACTIVE, but the certificate has been stuck on CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP since 31 August.
I believe the domains are still registered against the old account's service (old project id 49296e8b-f5f2-4eed-b0ec-4c3a24d52acd, service id 11f2cdee-f475-482a-bb2f-6609791dede8), which is why ownership validation never completes. The old services are stopped. Could you release/detach both domains from the old account so the new service can validate and issue certificates? Happy to delete the old projects entirely if that is what it takes. Thank you!
1 Replies
a month ago
Both domains are on your current workspace's "hq" service and no domain release is needed. The CNAME records are correctly propagated, but each domain is missing its TXT verification record, which is why certificates are stuck validating. At GoDaddy, create a TXT record for each domain using the hostname and value shown in your service's Settings under Networking (click "Show DNS records" next to each domain). Once both TXT records propagate, certificate issuance will complete automatically.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 26 days ago