Your CNAME record is correctly propagated, but the TXT ownership-verification record is missing, which is why the certificate is stuck on VALIDATING_OWNERSHIP. In your service's Settings under Networking, click "Show DNS records" for that domain to see the required TXT record name and value, then add that TXT record at your DNS provider. Once it propagates, verification and certificate issuance will proceed automatically.

Hi, I need help with a custom domain that's been stuck for a while.

Project: stellar-acceptance (ID: 54541c4c-8473-406c-abb7-b76e91c5b20f)

Service: metodo-mr-manus (ID: 0199ad5c-28ff-4ab3-bb5e-9b994a33adab)

Environment: production

Domain affected: www.mixiq.com.br

The domain status shows:

verified: false

certificate.status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP (stuck, no error message)

DNS record: CNAME www → g6bhawmi.up.railway.app — this is required by Railway and it's already correctly set and shows as propagated according to Railway's own domain-status check.

For comparison, another custom domain on the exact same service (app.mixiq.com.br, CNAME → ht34pox6.up.railway.app) was added the same way and is fully verified with a valid certificate (CERTIFICATE_STATUS_TYPE_VALID).

Since the DNS is confirmed correct and propagated but ownership verification never completes for www.mixiq.com.br, could you please manually re-trigger the domain verification / certificate issuance for this domain, or let me know what's blocking it?

Thanks!

To correct our earlier message, the TXT verification record is present and matches correctly. Your DNS is fully in order. The certificate verification workflow stalled before it could pick up the record, so it never re-ran. We've triggered a certificate re-issuance for that domain, which should complete within a few minutes.