22 days ago
Hi Railway team,
The SSL certificate for our custom domain has been stuck in "Issuing" since the domain was added. It never completes, and the edge still serves the default *.up.railway.app certificate, so browsers show a security error on our production site.
Details:
- Project: 2b2c990f-4af4-47fd-8ea8-5437285696f0
- Environment: production (402b0b6c-744d-4d30-ab43-a9bd7fe5d962)
- Service: site (a16b5e48-3308-40b1-a3b5-10ccc97e4a05)
- Custom domain: seminovos.grupovirage.com.br (id
dd4bfcf1-a17b-4164-9cdc-644c9f5f76c4)
- Domain added: 2026-10-27 19:58 UTC
What we have checked:
- DNS: CNAME seminovos -> 1wobjxa3.up.railway.app on all authoritative nameservers (ns1/ns2/ns3.locaweb.com.br), on Google (8.8.8.8) and on Cloudflare (1.1.1.1).
- Cloudflare 1.1.1.1 had a cached empty answer earlier. We purged it on 2026-10-28, and it resolves correctly now.
- The Railway API shows the DNS record as DNS_RECORD_STATUS_PROPAGATED and verified = true.
- There are no CAA records on grupovirage.com.br.
- Port 80 reaches Railway (301 to HTTPS, x-railway headers present).
- We called customDomainIssueCertificate four times on 2026-10-28, between 12:40 and 15:10 UTC. certificateStatus stays CERTIFICATE_STATUS_TYPE_ISSUING, certificateErrorMessage is null, and the certificates list is empty.
- crt.sh shows no certificate issued for this hostname since 2026-08-30 (that one came from our old server), so this is not a Let's Encrypt rate limit.
Our staging domain in the same project (staging-seminovos.grupovirage.com.br) works fine.
Could you please reset or re-trigger certificate issuance for this domain? We would prefer not to delete and re-add the domain, because the CNAME target might change and the DNS is managed by a third party.
Thank you!
0 Replies
22 days ago
It looks like you already have a thread open about this: Let's Encrypt TLS certificate rate limit issue on custom domain. We're automatically closing this one, and we'll reply to you there soon. If you have anything more to add about this topic, please post it in that thread.
Status changed to Duplicate Railway • 22 days ago