3 days ago
Hello Railway Community,
I need help resolving a custom-domain verification problem affecting my VaultPro application.
Project details:
Project: VaultPro
Service: vaultpro
Environment: production
Domain: vaultpro.org
Railway URL: https://vaultpro-production.up.railway.app
GitHub repository: 365ddevotional-cloud/vaultpro
DNS provider: Cloudflare
Current problem:
My Railway deployment is successful and the service is Online. However, Railway still reports Domain verified: false and SSL certificate: ISSUING.
Cloudflare records:
CNAME @ -> d22ldemt.up.railway.app
TXT _railway-verify -> Railway verification token
Proxy: DNS Only
Railway reports that the CNAME has propagated, but TXT verification remains unspecified.
Google Search Console also recently reported indexing errors, including a 404. This may be a separate issue.
Please help me determine:
- Why Railway has not verified the domain.
- Whether Railway recognizes the TXT verification record.
- Why SSL issuance has not completed.
- What steps will resolve this without disrupting the existing application or DNS records.
Thank you for your assistance.
Moses Afolabi
1 Reply
Status changed to Awaiting Railway Response Railway • 3 days ago
3 days ago
Your DNS is set up correctly: the CNAME has propagated, and your _railway-verify TXT record is live and matches the expected token exactly. Your verification check ran before that record was in place and wasn't re-run, so the domain stayed unverified and the certificate stayed at issuing.
We've started a fresh verification and certificate issuance for your domain. It may take a few minutes to finish. You don't need to change your DNS records or your running service.
The Search Console 404 is a separate issue from verification.
Status changed to Awaiting User Response brody • 3 days ago