Hello Railway Support,

My custom domain app.sassuria.fr is stuck during domain verification / SSL certificate issuance despite the required DNS records being publicly available.

Project: elegant-flexibility

Project ID: f8aa3f4b-0c6a-4f32-8b82-4152e6a1d0a9

Environment: production

Service: sassuria-agent

Domain: app.sassuria.fr

Domain ID: f2825ad4-7f9a-4f05-9a29-7fed8a41423f

Target port: 8080

railway domain status app.sassuria.fr reports:

Sync status: ACTIVE

Verified: no

Certificate status: CERTIFICATE_STATUS_TYPE_ISSUING

Railway expects:

CNAME: app → jlkhtf7u.up.railway.app

TXT: _railway-verify.app → railway-verify=648464b5cb7112b43f9e95aa5b7feec97ee836ce5eb9781deefa6f10625e71fc

Both DNS records are configured. I also verified the TXT record using an external public DNS lookup, which returns the exact value expected by Railway.

The domain was created on 2026-08-30 and is still not verified.

I also ran:

railway domain certificate retry app.sassuria.fr

The CLI returned:

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

The custom domain currently presents an invalid TLS certificate (NET::ERR_CERT_COMMON_NAME_INVALID), preventing an external webhook provider from validating the HTTPS endpoint.

Could you please inspect the domain verification/certificate workflow on Railway's side and re-trigger/re-issue the certificate if necessary?

I have intentionally not deleted/recreated the domain because the required DNS records are already correctly published.

Thank you.