6 days ago
Project: EduPass (d123eab5-04c9-4f34-95d8-979501da3c38), service edupass-v2 (52a9db42-b390-4ab8-9cbc-9a14b89b134f), production environment.
Custom domain sistema.karrtechnology.dev is attached to the service but browsers consistently show NET::ERR_CERT_COMMON_NAME_INVALID — the certificate served is for *.up.railway.app, not the custom domain.
DNS is correctly configured in Cloudflare: CNAME record pointing to the Railway-provided target, DNS-only (grey cloud, no proxy). We've had this issue persist across several different subdomains attached over time (previously app.karrtechnology.dev, edupass.karrtechnology.dev, now sistema.karrtechnology.dev), all with the same symptom, well beyond the normal ~1 hour issuance window.
Could you check server-side why certificate issuance isn't completing for this domain? We'd like to avoid re-adding/removing the domain further given Let's Encrypt's rate limits.
1 Replies
6 days ago
Your CNAME is correctly propagated, but the TXT verification record needed for domain ownership verification is missing. Certificates cannot issue until both the CNAME and the TXT record are in place. In Cloudflare, add a TXT record with the host and value shown on the custom domain panel in your service's settings, then allow a few minutes for propagation and certificate issuance.
Status changed to Awaiting User Response Railway • 6 days ago