a month ago
Hi! I have a custom domain that won't get an SSL certificate, even though everything looks correct on my side.
Service: adsure-leads-db (Pro plan)
Domain: link.pedroquadrado.com
Current CNAME target: i4kwggrm.up.railway.app (DNS resolves correctly, confirmed via Google DNS)
Status in dashboard: "Waiting for DNS update" — the served cert stays *.up.railway.app and never becomes the domain cert.
What I've verified:
DNS is correct and propagated (CNAME → i4kwggrm.up.railway.app, TTL 300).
We're on the Pro plan (was previously blocked by the Hobby 2-domain limit, upgraded since).
crt.sh shows no certificate ever issued for link.pedroquadrado.com.
I've waited 30+ min after a fresh registration; no cert.
I re-registered this domain a few times while troubleshooting, so I suspect I may have hit a Let's Encrypt rate limit, or the provisioning is stuck. Could you check why the certificate isn't issuing and force-provision it? Thank you!
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 30 days ago
a month ago
You need to add a TXT record for _railway-verify.link.pedroquadrado.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.