a month ago
We are connecting www.vocantera.es to our public website hosted on Railway. We expected Railway to verify domain ownership and automatically issue an HTTPS certificate after configuring the required DNS records in IONOS. However, the domain has remained unverified since October 16, preventing us from completing the custom-domain setup. The issue was still present on October 20, and we would appreciate assistance investigating and completing the verification process.
Affected resources
- Workspace: fdelvalle66's Projects
- Project: dynamic-truth
- Environment: production
- Service: web
- Service ID:
daf676d7-9e0c-4e59-a3e2-77c2161899ef - Custom domain: https://www.vocantera.es
- Domain ID:
91df1f82-e1b2-4b30-8efc-b6f7d175f036 - Existing Railway service URL: https://web-production-4741c.up.railway.app
The service's default Railway domain is reported as ACTIVE. This is a custom-domain verification problem, not a confirmed application deployment failure. No failed deployment ID has been identified.
Timeline and current status
The Railway CLI reports the domain was created on October 16, 2026, at 14:52:11 UTC.
On October 20, 2026, the CLI still reported:
Sync status: ACTIVE
Verified: no
Certificate status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIPThe exact time of the latest observation was not recorded.
The Railway dashboard also displayed "Waiting for DNS update".
DNS verification performed
Our DNS provider is IONOS.
We verified the records using Google Public DNS (8.8.8.8) and directly against all four authoritative IONOS nameservers:
ns1049.ui-dns.bizns1067.ui-dns.orgns1049.ui-dns.comns1125.ui-dns.de
All four authoritative nameservers returned the same expected records.
CNAME:
www.vocantera.es
→ xupjawh7.up.railway.appTXT:
_railway-verify.www.vocantera.esThe TXT value matched the complete verification value provided by Railway. The verification token is omitted from this public-facing report.
These checks confirm that the expected DNS records were being served by the authoritative nameservers and Google Public DNS. We cannot determine why Railway has not accepted ownership verification.
Railway CLI diagnostics
We successfully linked the CLI to the dynamic-truth project, production environment, and web service.
The following command confirmed the custom domain is associated with the correct service:
railway domain list --service webIts entry showed:
Domain: www.vocantera.es
Type: custom
Port: 8080
Sync: ACTIVEWe also executed:
railway domain status www.vocantera.es --service webThe result confirmed that ownership remains unverified and the certificate is still validating ownership.
We attempted to retry certificate issuance:
railway domain certificate retry www.vocantera.es --service webRailway returned:
Certificate retry is only available after certificate issuance fails. Current status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP.Therefore, the retry was not performed.
We have not deleted or recreated the domain, redeployed the service to troubleshoot this problem, or made further DNS changes after these checks.
Why we are contacting Railway Support
Contacting Railway Support was first recommended by an AI assistant after repeated DNS checks showed the expected records, while ownership verification remained pending for several days.
The concrete blocker is that the certificate retry command is unavailable in the current state, and the available dashboard and CLI actions have not provided a way to restart or diagnose the ownership verification process.
An internal Railway agent also reported that its available tools could not force domain reverification or certificate issuance.
Requested assistance
Could your team please:
- Inspect the internal ownership verification state for this custom domain.
- Determine why verification remains pending despite the matching DNS records.
- Check whether any additional DNS, CAA, DNSSEC, or certificate authority requirements are preventing validation.
- Restart or repair the verification and certificate provisioning process if appropriate.
- Explain any further action required from us.
We suspect the verification workflow may be stalled, but this has not been confirmed.
Please avoid deleting or recreating the domain, changing DNS records, or redeploying the application without discussing those actions with us first. We would like to complete the verification without unnecessary downtime or changes to the currently running service.
Thank you for your assistance.
Prepared with Railway's support template (v1).
0 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved fdelvalle66 • about 1 month ago