Hello Railway Support Team,

I am attempting to configure a root-level wildcard custom domain (*.mihotel.xyz) on my backend service. Because the validation loop got permanently stuck on my initial attempt, I followed troubleshooting advice and spun up an entirely fresh project to bypass any possible project-level network caching.

However, even on this brand-new project with a completely pristine token chain, the validation is immediately stuck back on "Certificate Authority is validating challenges."

I have verified the DNS configuration on Cloudflare. All records are set to DNS Only (Grey Cloud) to allow unhindered challenge mapping. A public DNS lookup confirms that the challenge record maps directly to the active Railway verification machine:

nslookup -type=CNAME _acme-challenge.mihotel.xyz 1.1.1.1

Result: _acme-challenge.mihotel.xyz canonical name = 9t9x9wfq.authorize.railwaydns.net.

The _railway-verify TXT record is also correctly configured and matching. I have also verified that there are no conflicting CAA records on the domain root preventing Let's Encrypt from proceeding.

Since the entire DNS chain resolves flawlessly from public resolvers but the dashboard remains frozen, it appears the ACME certificate pipeline is stalled on the infrastructure level. Could an engineer please manually trigger a fresh certificate evaluation or force the issuance on your end?

Thank you!