a month ago
Custom domain app.vyrenox.com remains stuck in VALIDATING_OWNERSHIP even though the required DNS records now exactly match Railway and are fully propagated.
Project: Vyrenox Enterprise OS
Environment: production
Service: vyrenox-backend
Domain: app.vyrenox.com
Current verified diagnostics:
- Required CNAME is correct and publicly propagated.
- Required TXT ownership verification record now exactly matches Railway's current token.
- TXT propagation confirmed through 1.1.1.1, 8.8.8.8 and Cloudflare DoH.
- No CAA restriction.
- No DNSSEC blocking.
- Origin service is RUNNING and responds HTTP 200.
- Effective service port is 8080.
- Requests to app.vyrenox.com reach Railway but return 404 Application not found with x-railway-fallback: true.
- Railway still reports verified=false.
- certificateStatus remains CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP.
- Custom-domain routing is still inactive.
- Network/application logs show no relevant errors.
Please manually reconcile/re-trigger ownership verification, domain routing and certificate issuance for the EXISTING custom domain app.vyrenox.com.
Please do not require us to delete/recreate the domain unless Railway engineering confirms that it is technically necessary, because the CNAME and TXT are already correct and publicly propagated.
1 Replies
a month ago
Your custom domain is now fully operational: DNS is propagated, ownership is verified, the TLS certificate is valid, and edge routing is serving traffic with no fallback. The verification and certificate issuance have completed since the state you described, so no manual intervention is needed.
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