Hi Railway Support,

I'm experiencing a persistent SSL certificate provisioning failure for a custom domain

on one of my Railway projects. The domain CNAME is verified as valid, but Railway never

issues an SSL certificate — it has been stuck for over 6 hours.

--- Environment ---

Project: lucky-harmony

Project ID: 38c0feae-7716-4c93-9af7-9199b758a417

Environment: production (750c7a5f-2811-4a15-a85a-419b0d20e4ec)

Service: web (718d3c62-ddf1-48d5-85d3-e0ff3cd2b330)

Custom Domain: erp.meatscanner.io

Domain ID: 6a16a3bc-40cd-408b-a6dc-f5e1adfb09f3

CNAME target: 93ehezzv.up.railway.app (CNAME check = VALID / "Full steam ahead!")

--- Symptoms ---

1. CNAME resolves correctly and Railway's own CNAME check returns VALID.

2. SSL certificate served is still CN=*.up.railway.app (Railway wildcard),

not a domain-specific cert.

3. The ACME HTTP-01 challenge path returns 404:

GET http://erp.meatscanner.io/.well-known/acme-challenge/test

→ {"status":"error","code":404,"message":"Application not found"}

This suggests Railway's edge cannot route HTTP for this domain before

the SSL cert exists (chicken-and-egg deadlock).

4. No new certificate request for erp.meatscanner.io has ever appeared on

crt.sh — Railway has never successfully submitted an ACME challenge

to Let's Encrypt for this domain.

--- What I have tried ---

- Deleted and re-added the custom domain 5 times (domain IDs: 61de247d,

188c7668, dd51b5b6, a0c46bc3, 6a16a3bc)

- The domain was previously registered as a Vercel alias for ~45 days

(Vercel A record: 76.76.21.21). I removed it via `vercel alias rm

erp.meatscanner.io` and updated DNS to Railway CNAME.

- Waited 6+ hours after each attempt.

--- Comparison (working) ---

A different custom domain on a different Railway project works fine:

dashboard.meatscanner.io → project: meatscanner (82ce882b)

SSL provisioned correctly within minutes.

The issue appears specific to the lucky-harmony project. Could you please

investigate why SSL provisioning never initiates for this domain, and

whether the project has a known issue with the ACME provisioning pipeline?

Thank you.