a month ago
Service: invexa (project Invexa)
Custom domain: www.invexascan.com
Status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP (stuck since 2026-09-01, now 3+ days)
DNS & Configuration:
- CNAME record: Confirmed propagated → oq5xc3az.up.railway.app ✓
- CAA records: Clean (verified via dns.google) ✓
- Domain history: Never used elsewhere ✓
Current behavior:
- HTTPS requests return Railway "Not Found" edge error
- Browser shows cert mismatch: *.up.railway.app served instead of www.invexascan.com
What I've verified:
- All standard troubleshooting (CNAME, CAA) checks out
- No platform-wide incidents or maintenance affecting the service
Certificate validation is stuck beyond the 72-hour threshold. Can the team inspect the actual certificate/DNS state and manually retry the validation if needed?
Project ID: 6ef232ee-5607-419d-8623-e4945c36b146
Service ID: 03987c1a-beca-4ff7-8086-8935bb83f084
1 Replies
a month ago
Your custom domain's certificate is stuck at validating ownership because the TXT verification record is missing. The CNAME for traffic routing is correctly propagated, but domain verification also requires a TXT record at the hostname shown in your service's networking settings (the _railway-verify subdomain) with the verification value displayed there. Once you add that TXT record at your registrar and it propagates, verification will complete and the certificate will issue.
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 • 26 days ago