Hi, my custom domain will not get a TLS certificate and has been stuck on CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for over 24 hours.

Details:

• Project: wijnveiling-scanner (id 3bbb3bab-ae3e-41a4-abd0-ff2d6e6cde3b)
• Environment: production
• Service: web (id 26c048ff-7c54-49f9-beb8-392565256bd2)
• Custom domain: veiling.eikenrode.nl (custom domain id abf97006-f585-4a54-a3a4-df5d4a5adf75)
• Required CNAME target: a8ny3j7x.up.railway.app

Everything on my side is verified correct:

• The authoritative nameserver (ns0.transip.net) returns exactly one CNAME: veiling.eikenrode.nl -> a8ny3j7x.up.railway.app. (single record, correct value).
• Google (8.8.8.8) and Cloudflare (1.1.1.1) both resolve to a8ny3j7x.up.railway.app.
• Your own dashboard shows dnsRecords status DNS_RECORD_STATUS_PROPAGATED and currentValue now matches a8ny3j7x.up.railway.app.
• The ACME HTTP-01 path (/.well-known/acme-challenge/) is answered by railway-edge (404 for a random token, as expected), so the challenge path reaches your edge fine.
• There is no CAA record blocking Let's Encrypt and no AAAA/IPv6 record.

Despite this, the certificate never issues and the edge keeps serving the wildcard *.up.railway.app certificate, so https://veiling.eikenrode.nl fails with an SSL host-name mismatch.

I already tried deleting and re-adding the custom domain (which changed the CNAME target from bn2wephv to a8ny3j7x, and I updated DNS accordingly), but it landed back on VALIDATING_OWNERSHIP. This looks like a stuck cert-issuance pipeline or a Let's Encrypt failed-validation rate limit on your side.

Could you please force a certificate re-issue / clear the stuck ownership validation for this domain? Thanks!_STATUS_TYPE_VALIDATING_OWNERSHIP for over 24 hours.

Details:

• Project: wijnveiling-scanner (id 3bbb3bab-ae3e-41a4-abd0-ff2d6e6cde3b)
• Environment: production
• Service: web (id 26c048ff-7c54-49f9-beb8-392565256bd2)
• Custom domain: veiling.eikenrode.nl (custom domain id abf97006-f585-4a54-a3a4-df5d4a5adf75)
• Required CNAME target: a8ny3j7x.up.railway.app

Everything on my side is verified correct:

• The authoritative nameserver (ns0.transip.net) returns exactly one CNAME: veiling.eikenrode.nl -> a8ny3j7x.up.railway.app. (single record, correct value).
• Google (8.8.8.8) and Cloudflare (1.1.1.1) both resolve to a8ny3j7x.up.railway.app.
• Your own dashboard shows dnsRecords status DNS_RECORD_STATUS_PROPAGATED and currentValue now matches a8ny3j7x.up.railway.app.
• The ACME HTTP-01 path (/.well-known/acme-challenge/) is answered by railway-edge (404 for a random token, as expected), so the challenge path reaches your edge fine.
• There is no CAA record blocking Let's Encrypt and no AAAA/IPv6 record.

Despite this, the certificate never issues and the edge keeps serving the wildcard *.up.railway.app certificate, so https://veiling.eikenrode.nl fails with an SSL host-name mismatch.

I already tried deleting and re-adding the custom domain (which changed the CNAME target from bn2wephv to a8ny3j7x, and I updated DNS accordingly), but it landed back on VALIDATING_OWNERSHIP. This looks like a stuck cert-issuance pipeline or a Let's Encrypt failed-validation rate limit on your side.

Could you please force a certificate re-issue / clear the stuck ownership validation for this domain? Thanks!