2 hours ago
I'm trying to configure the custom domain data.aguaclarareach.org for our PlaCoDA application hosted on Railway.
Railway continues to display "Waiting for DNS update", with a green checkmark for the CNAME record but a yellow warning triangle for the TXT verification record.
Our DNS is managed by Squarespace. Both records have been configured exactly as specified by Railway:
CNAME: data.aguaclarareach.org → e3m6n8qw.up.railway.app
TXT: _railway-verify.data.aguaclarareach.org → railway-verify=ea33df51acfcb2b22b9a0672a6d8b820659c15c85d27b2628169ee5b1aca42ff
We independently verified both records using Google's public DNS service. Both resolve correctly, and more than an hour has passed since the records were created.
When accessing https://data.aguaclarareach.org, Chrome reports NET::ERR_CERT_COMMON_NAME_INVALID, suggesting that the SSL certificate has not been provisioned correctly.
It appears that Railway's domain verification or certificate provisioning process may be stuck.
Could you please manually retry domain verification and SSL certificate provisioning for this custom domain?
Thank you for your help!
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
an hour ago
Both of your records are correct: the CNAME is propagated, and the TXT record at _railway-verify.data returns the expected verification value in public DNS.
We've started a fresh domain verification and certificate issuance for this domain, which can take a few minutes to complete.
Status changed to Awaiting User Response chandrika • about 1 hour ago
an hour ago
Domain verification has now completed and the SSL certificate for your custom domain has been issued, so it should load over HTTPS without the certificate warning. If your browser still shows the old error, a hard refresh or a new tab will pick up the new certificate.