Hi Railway team,

I'm running into a stuck HTTPS cert issuance on two custom

domains for my Equipment Wire production site. Been stuck

in VALIDATING_OWNERSHIP for over 3 hours.

Domains:

• equipwire.ca (custom domain ID: 57b7d6ad-d61a-47c1-a0a8-3b6e031c9743)
• www.equipwire.ca (custom domain ID: 3acbcf6e-e2a7-4422-b1f2-e933d5909fd7)

Project ID: 3bb0f3de-189e-4c42-9939-6079b0798735

Service ID: 46bdc001-d78c-4add-98b1-4c4dd0e38c1c

Environment ID: c5516852-8068-4ae9-b4b3-db5f33798887

Both domains were added at 2026-09-09 21:15 UTC.

DNS is fully propagated globally:

• equipwire.ca CNAME → 4h6inc9j.up.railway.app (correct)
• www.equipwire.ca CNAME → 3dbgfmfe.up.railway.app (correct)
• No CAA records blocking Let's Encrypt
• Railway edge is serving requests (HTTP 301 redirect to HTTPS works)
• HTTPS returns no response due to missing cert

Certificate status still shows CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP

for both domains after multiple calls to customDomainIssueCertificate

mutation (both returned success:true, but status hasn't changed).

Can you please:

1. Check Let's Encrypt error logs for these domains on your end
2. Force a fresh cert issuance
3. Or advise if there's something wrong with my setup I'm missing

This is production - my users can't reach the site at

the domain they know. Currently having to fall back to

equipwire-production.up.railway.app.

Thanks,

Dan

Core Rock Construction

corerockconstruction@gmail.com