custom domain taking a long while to issue TLS cert

Possibly unnecessary backstory I have a custom domain up and running for about a week or so. Due to CNAME @ conflicting my transactional email provider's SPF @, I was only able to explicitly add it as www.bandbudgie.com (note the www subdomain). I've since set up my transactional emails to send from a different subdomain. My Issue I've gone back into the service with a domain... and added the bandbudgie.com (no subdomain) as my second domain name on this service. It (seemingly?) hooked up with my namecheap DNS and changed status to "Issuing TLS certificate" (screenshot attached). However it's been like this for a almost 2 days now? I understand that it can take up to 72 hours... but none of my other services had taken this long. In the meantime - I'm getting the scary "Your connection is not private" screens. Also attached is the Certificate Viewer (if that's at all helpful?). For what it's worth - There seems to be a LetsEncrypt cert for Railway issued in December - around the time I was setting up emails. Could this be part of the problem? projectId: 1e4b0651-0174-42a1-aac8-4081f16bb807 Service: brochure

Solution:

Could you try removing the custom domain from Railway and removing the CNAME from namecheap and then try readding it?

Jump to solution