2 hours ago
Hello Railway Support,
Our custom domain www.schaf-architektur.com is stuck on "Waiting for DNS update".
We have verified the following:
- CNAME and TXT records exactly match Railway's requirements.
- Both records are publicly accessible through Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1).
- No restrictive CAA records were found.
- No DNSSEC DS record was found.
- The application works correctly on its Railway-generated domain.
However, www.schaf-architektur.com returns NET::ERR_CERT_COMMON_NAME_INVALID.
Project: Architektur Schaf
Service: pleasing-spontaneity
Environment: production
Port: 8080
Could you please investigate the domain verification and SSL certificate issuance and retry the verification if necessary?
Thank you!
1 Reply
Status changed to Awaiting Railway Response Railway • about 2 hours ago
an hour ago
The custom domain added to your service doesn't match the domain you're configuring DNS for. The hostname saved in the service's Networking settings has a typo (a letter is missing from "architektur"), so the certificate is being requested for that misspelled name and no domain entry exists for the correctly spelled one, which is why the browser reports a name mismatch.
To fix it, add the correctly spelled hostname in the service's Settings, Networking section and remove the misspelled one. The new entry will come with its own CNAME target and TXT verification value, so update both records at your DNS provider to match exactly what the dashboard shows for the new entry. Once both records check out, the certificate will be issued for the correct name.
Status changed to Awaiting User Response Railway • about 1 hour ago