Custom domain stuck waiting for DNS update; certificate not issued
oscarloliveiv
FREEOP

12 days ago

Project: ample-magic

Service: one-more-day

Environment: production

Custom domain: onemoredayaa.com

Target port: 8080

The public CNAME and the _railway-verify TXT record have both been independently confirmed as correct and fully published. Railway still shows “Waiting for DNS update” in Service Settings → Networking. The public endpoint https://onemoredayaa.com/api/healthz reaches Railway but receives Railway’s generic/wrong certificate (ERR_CERT_COMMON_NAME_INVALID), so the domain-specific certificate has not been issued.

Please re-trigger custom-domain ownership verification and certificate issuance on Railway’s side. We have intentionally not deleted/re-added the domain to avoid certificate rate limits.

Project ID: f451ad56-e940-4999-b794-2e71245b4769

Service ID: a46ff70a-8575-4da6-a557-415d5a3ad082

Environment ID: 2da85c57-ca50-471c-84ab-01b97e01bc76

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 12 days ago


chandrika
EMPLOYEE

12 days ago

Your DNS records are correct. The certificate workflow had stalled, so we've re-triggered verification and certificate issuance for onemoredayaa.com. It should complete within a few minutes.


Status changed to Awaiting User Response Railway 12 days ago


Status changed to Solved chandrika 12 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...