Hi Railway Support,

I'm experiencing what appears to be the same issue described in the recently solved thread “Custom domain stuck at ISSUING / Verified no despite correct DNS”, where Railway Support triggered a server-side certificate re-issuance.

Project: lucky-courtesy

Environment: production

Service: doc-reader-ia

Custom domain: api.docle.com.br

Target port: 8080

The Railway dashboard continues to display:

Waiting for DNS update

However, the Railway CLI reports:

Sync status: ACTIVE

Verified: no

Certificate status: CERTIFICATE_STATUS_TYPE_ISSUING

The certificate has remained stuck in ISSUING since yesterday.

The required DNS records are correctly configured and publicly propagated:

CNAME:

api.docle.com.br → 8hrud320.up.railway.app

TXT:

_railway-verify.api.docle.com.br → railway-verify=efd286b37438fc3922dde757e9a4c4c57444b0f6e56bf2d343be1620874af072

Both records have been verified directly against Google Public DNS (8.8.8.8) and return the expected values.

I have also confirmed:

No CAA record is restricting certificate issuance.

DNSSEC is enabled and the validation chain was successfully analyzed with DNSViz, with no apparent errors.

Railway reports the domain sync status as ACTIVE.

The CNAME and TXT records match exactly what Railway currently reports as required.

I also attempted:

railway domain certificate retry api.docle.com.br

but Railway returned:

Certificate retry is only available after certificate issuance fails. Current status: CERTIFICATE_STATUS_TYPE_ISSUING.

Since this appears to match the recently solved case where Railway triggered a server-side certificate re-issuance, could you please check whether the verification/certificate workflow for this domain is stuck and trigger a server-side re-verification or certificate re-issuance if appropriate?

I would prefer not to remove and re-add the custom domain, since the DNS records are already correctly configured and publicly propagated.