2 days ago
Hello Railway support,
The custom domains api.tumblebase.com and app.tumblebase.com on our Gymnastics project are stuck in ownership validation.
Rechecked on 18 September 2026: the API dashboard requires CNAME api -> ix10sr39.up.railway.app and an ownership TXT record at _railway-verify.api. Both exactly match public DNS, but the dashboard still reports Waiting for DNS update and HTTPS fails hostname validation. Earlier checks on both domains found matching CNAME and ownership TXT records, with certificate status VALIDATING_OWNERSHIP.
Certificate retry was refused because that operation was only available after FAILED. No domains have been deleted or recreated and no certificate validation has been bypassed. The Railway-generated service address works over valid HTTPS and serves the healthy application.
Please investigate/recheck ownership validation and certificate issuance for the existing domains. The affected membership service is attached to this request; the web service in the same Gymnastics production environment is also affected.
Thank you,
Mike
3 Replies
Status changed to Awaiting Railway Response Railway • 1 day ago
2 days ago
Your CNAME and ownership TXT records are correctly in place for both domains. Ownership verification had not re-run after the records propagated, so we have kicked off a certificate re-issue for both. It may take a few minutes to complete.
Status changed to Awaiting User Response brody • 1 day ago
Status changed to Solved mike-tempest • about 16 hours ago
an hour ago
Thanks Brody, the certificate re-issue worked. Rechecked today (20 September): https://app.tumblebase.com/login and https://api.tumblebase.com/health both return HTTP 200 with valid HTTPS.
The marketing site at https://www.tumblebase.com also returns HTTP 200 with valid HTTPS. The only remaining 'Waiting for DNS update' entry is the bare tumblebase.com domain on the marketing service. That domain is intentionally hosted elsewhere and already returns a permanent 301 redirect to https://www.tumblebase.com/, so this appears to be an unused Railway domain attachment rather than the same certificate issue.
Could you confirm whether we can remove that unused bare-domain entry from Railway while keeping www.tumblebase.com attached and the existing external redirect in place?
Thanks for resolving the app and API domains.
Mike
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
Yes, removing the bare domain entry from that service will not affect the www subdomain or its certificate, as each custom domain attachment is independent. You can remove it from the domain's settings on the service, or via the CLI with railway domain delete.
Status changed to Awaiting User Response Railway • about 1 hour ago