Your custom domains are missing the required TXT verification records. Your CNAME records are set up correctly, but you also need to add a TXT record for each domain to verify ownership. Check your service's custom domain settings in the Railway dashboard for the exact record names and values, then add them in your DNS provider. Certificates will be issued automatically once the TXT records propagate.

Is this $1000 bounty ?

Fixed.

Fix for Custom Domains Stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP

This is a common Railway edge/cache issue with certificate issuance.

Fastest Solution (Works for Most People):

1. Remove both domains from the service:
   • Go to your service → Domains tab
   • Delete erp.toruna.com.tr and api.toruna.com.tr
2. Redeploy the service (or trigger a new deployment)
3. Wait 2–3 minutes, then re-add the domains one by one.
4. Railway will generate a new CNAME target for each. Update your DNS records with the fresh values.
5. Wait another 5–15 minutes for the certificate to issue.

Extra Tips:

• Double-check that your CNAME records point exactly to the new target Railway gives you.
• Use a tool like dig or https://dnschecker.org to confirm propagation.
• If you're using Cloudflare, make sure the proxy (orange cloud) is turned off (grey cloud) during initial validation.

This forces Railway to create a fresh edge binding and restart the certificate process.

If it's still stuck after re-adding and waiting 30 minutes, tag the team or provide the Domain IDs again — they can usually clear the stuck state on their end.