a month ago
Hi Railway team,
The SSL certificate for proximitty.com remains in CERTIFICATE_STATUS_TYPE_ISSUING, while *.proximitty.com on the same service already has a VALID certificate. The service is deployed successfully and running.
Checks completed:
- The apex domain is verified in Railway. Its required CNAME is pwx0pu21.up.railway.app, configured in Cloudflare as DNS only (proxy disabled).
- Both authoritative nameservers, Cloudflare DNS, and Google DNS resolve the apex to 69.46.46.56, matching the Railway target. There is no apex AAAA record.
- DNSSEC validates, and no CAA restrictions were found.
- A request to a synthetic HTTP path under /.well-known/acme-challenge/ reaches railway-edge and returns 404 without redirecting to Cloudflare or Linktree. This only confirms reachability; it is not a successful test of the actual ACME challenge token.
- HTTPS for the apex still fails hostname verification. Direct HTTPS to Railway for dicard.proximitty.com succeeds with certificate verification enabled.
- The wildcard _acme-challenge CNAME is DNS only and resolves to the Railway-provided authorization target.
We requested one certificate retry after verifying DNS. We have not repeatedly retried or deleted/re-added the apex domain. The domain-status API still reports ISSUING with errorMessage: null.
Could you please inspect the ACME order for proximitty.com and confirm the challenge method, the last validation error, and whether issuance is blocked or waiting for another retry?
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The apex domain is verified on our side, its routing record reads as propagated, and our check of the HTTP challenge path reaches our edge with a 200. The certificate itself is still stuck waiting on the certificate authority's authorization step, with no error recorded. That means nothing in your DNS setup is blocking it.
We've started a fresh certificate issuance for the apex domain. It can take a few minutes to complete, and you don't need to remove and re-add the domain.
Status changed to Awaiting User Response brody • about 1 month ago
Status changed to Solved jarangor19 • about 1 month ago
