a month ago
Hi, all custom domains across ~13 of my projects are stuck without SSL
certificate issuance after a domain rebrand done today.
Symptoms across all affected domains:
- DNS records show status DNS_RECORD_STATUS_PROPAGATED via your GraphQL API
- customDomains.status.certificates returns [] (empty)
- openssl s_client shows servers respond with default *.up.railway.app cert
- No CAA records blocking Let's Encrypt
- HTTP /.well-known/acme-challenge/* returns 404 (no challenge pending)
- Tried delete+recreate custom domain + redeploy service — no effect after 3+ hours
Concrete example (most urgent):
- Domain: assinatura.luqsys.com.br
- Project ID: cb50a088-db00-49c9-b9a9-7f1de601db75 (assinaturaspro)
- Service ID: 58e72a4f-d40a-4130-a521-ce3950c10d9e (web)
- DNS correctly points to alias: 52loxi4v.up.railway.app
- Cert never issued
Other affected: bankpro.luqsys.com.br, farmpro.luqsys.com.br, frotapro.luqsys.com.br,
contabilidadepro.luqsys.com.br, pdvpro.luqsys.com.br, pontopro.luqsys.com.br,
solarpro.luqsys.com.br, viagempro.luqsys.com.br, milhaspro.luqsys.com.br,
obrapro.luqsys.com.br, aluguelpro.luqsys.com.br, motor.luqsys.com.br,
angela.luqsys.com.br, claudinei.luqsys.com.br
Could someone from the team trigger a cert reissue on these? Thanks.
1 Replies
Status changed to Open Railway • 27 days ago
a month ago
Make sure you're adding the required TXT records for all your domains. For example, assinatura.luqsys.com.br would require a TXT record on _railway-verify.assinatura.luqsys.com.br and claudinei.luqsys.com.br would need it on _railway-verify.claudinei.luqsys.com.br. (_railway-verify.<HOSTNAME>) You can get the content for the TXT record from the verificationToken property under status in the API.
Status changed to Awaiting User Response Railway • 27 days ago
20 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 20 days ago