Hi team — a custom domain on my service has been stuck issuing its TLS certificate (CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP) for ~3 days. Everything on the DNS side is correct and I've already tried deleting + recreating the domain twice.

Details:

Project: capable-vision (e67a0c9b-e2c8-413a-8ed4-8cc075576010)

Service: Proposals (9af2818c-5a12-46c8-89e2-0137a85865ab)

Environment: production (9f8a956e-75af-4282-9569-82e41d3b9147)

Custom domain: docs.pointdot.com.au (acbe9a6b-b65f-4c99-a000-e14652731c47), created 2026-06-03

Status: certificateStatus = CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP, verified = false

What I've verified on my side:

DNS: CNAME docs.pointdot.com.au -> agidr9vw.up.railway.app. Your dashboard shows currentValue == requiredValue, status PROPAGATED.

Globally propagated: Google 8.8.8.8, Cloudflare 1.1.1.1, OpenDNS 208.67.222.222 and Quad9 9.9.9.9 all return agidr9vw.up.railway.app.

No CAA records on pointdot.com.au (no CA restriction).

No conflicting A/AAAA/TXT on docs.

HTTP (port 80) reaches your edge and correctly routes the custom domain to my running service — /.well-known/acme-challenge/ returns my app's normal 404, identical to the working proposals-production-f83e.up.railway.app domain.

Already tried: deleted + recreated the custom domain twice (new target each time), updated the CNAME accordingly, waited through multiple propagation windows. No change.

Could you please manually re-trigger / investigate Let's Encrypt issuance for this domain? It appears stuck in ownership validation despite correct, globally-propagated DNS and correct service/environment binding. Happy to provide anything else. Thanks!