5 days ago
Custom domains periscopehq.ai and www.periscopehq.ai on service web (project industrious-courtesy) have been stuck at certificateStatus: VALIDATING_OWNERSHIP for 24h+. DNS shows PROPAGATED in the dashboard (CNAMEs to the provided targets, DNS-only via Cloudflare, resolves to your edge 69.46.46.x). No CAA records; /.well-known/acme-challenge/ is reachable and answered by railway-edge. Requests return x-railway-fallback: true 404. Please force certificate issuance or share the ACME error.
2 Replies
5 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 5 days ago
5 days ago
Try to remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again. Re-adding the domain usually fixes the stuck state. And since you are using Cloudflare, I suggest you use the automatic DNS setup button when you add your domain through the dashboard.
4 days ago
fwiw that 404 on /.well-known/acme-challenge/ isn't evidence of anything, the token path only exists for the few seconds a validation is actually running, so probing it by hand always 404s. do the remove and re-add darseen said above here, it clears most stuck VALIDATING_OWNERSHIP states. the one other thing worth checking while you wait the 10 min: dnssec on periscopehq.ai at your registrar. if it's enabled but the keys don't match cloudflare's, every other check shows green and propagated while cert issuance silently fails forever, and it fits a 24hr hang better than a transient stuck state does.