a month ago
Project: pismo-logistics-staging
Service: pismo-logistics-launchpad
Environment: production
Custom domain: staging.pismologistics.com
Target port: 8080
The Railway-generated domain and application are healthy:
https://pismo-logistics-launchpad-production.up.railway.app/api/health
The required DNS records are correctly configured and publicly resolvable:
CNAME:
staging.pismologistics.com -> euutpanr.up.railway.app
TXT:
railway-verify.staging.pismologistics.com contains the exact verification value provided by Railway.
The records resolve correctly through Google Public DNS and the authoritative nameserver. There are no restrictive CAA records or conflicting A/AAAA records.
However, Railway still displays “Waiting for DNS update.” HTTPS fails with a certificate hostname mismatch:
SEC_E_WRONG_PRINCIPAL / ERR_CERT_COMMON_NAME_INVALID
The Railway application itself is healthy and its readiness endpoint returns HTTP 200.
Could Railway please retrigger the custom-domain verification and SSL certificate issuance for staging.pismologistics.com?
1 Replies
a month ago
Your CNAME record is correct and propagated, but the TXT verification record is at the wrong hostname. It needs a leading underscore: the record name should start with _railway-verify. (note the underscore prefix), not railway-verify. without one. Once you update that at your DNS provider, verification and certificate issuance will proceed.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago