Hey can you share more details which DNS provider are you using, and if they are being proxied?

If youadded the domains recently, the certs should be generated automatically under 72 hrs

hi its namecheap . Like I said it was issued almost instantly for www but for proofkit.net it fails continuously.

Can you share a ss showing the exact message you are receiving, and the DNS config in namecheap? Would be faster to debug in that case.

sure here it is. I tried again multiple times. seems like railway side problem. because verifications I ran on terminal all returns 200 for txt records.

Did you try removing proofkit.net from railway and corresponding record from namecheap and then adding back again the in railway and the new records in namecheap?

Just to rule out any temporal issue.

I tested it. 5 hours later ( it was showin its being verified) it failed again showing internal error again. I have 10 other projects more. I dont think this isabout namecheap or how I set it up. looks solid bug from railway. hopefully can find someone from team here.

I am still waiting? Railway team??

Sorry for the long wait. We've re-triggered certificate issuance for proofkit.net. Your CNAME record is pointing to an outdated target. Check the Railway dashboard for the current CNAME value and update it in Namecheap. Once that propagates, the certificate should issue automatically.

Solving for now, but please reopen if you are still having issues.