21 days ago
Our production pinhub-api service is healthy at https://pinhub-api-production.up.railway.app/api/healthz (HTTP 200), but its custom domain api.pinhub.golf remains at 'Waiting for DNS update'. The CNAME for api and TXT for _railway-verify.api exactly match Railway's Show DNS records. Both resolve from the delegated authoritative nameserver ns15.domaincontrol.com and public resolvers 1.1.1.1 and 8.8.8.8. There are no CAA or DS restrictions. HTTPS to api.pinhub.golf still presents a *.up.railway.app certificate (hostname mismatch), and a diagnostic insecure request returns 404. Could Railway re-check ownership verification and trigger custom-domain routing/certificate issuance without deleting and re-adding the domain? We need valid HTTPS and HTTP 200 at https://api.pinhub.golf/api/healthz.
1 Reply
Status changed to Awaiting Railway Response Railway • 21 days ago
20 days ago
Your CNAME and verification TXT record are both correct and visible to us, but the domain had not yet been marked verified. We've started a new certificate issuance for the domain without removing it, and it may take a few minutes before HTTPS serves a valid certificate.
Status changed to Awaiting User Response brody • 20 days ago
13 days 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 • 13 days ago