same root cause as other reports -the ACME challenge path returning 404 is expected,Railway uses DNS-01 not HTTP-01 for cert validation. the provisioner is just stuck.remove stock.scmaine.com from your service, wait 30s, re-add it. that forces a fresh cert request cycle. DNS is already correct so it should provision within a few minutes.if it stalls again past 10 min, it's a rate-limit backoff on Railway's cert provider (Let's Encrypt caps at 5 failures/hour per domain).nothing you can do client-side at that point - needs a manual re-trigger from Railway staff.