Hello Railway team,

I'm having trouble provisioning a TLS certificate for my custom domain on a Railway service. The certificate issuance fails with an "internal error" message, even after multiple "Try Again" clicks.

Details:

• Project/Service: [Tên project hoặc service ID của bạn, ví dụ: vi ora-be-prod hoặc link project dashboard]
• Custom domain added: vi ora-app.xyz (apex/root domain @)
• DNS provider: Namecheap
• DNS configuration (apex domain):
  • Type: CNAME
  • Host: @
  • Value: 6muhnti4.up.railway.app (or similar, as provided by Railway)
  • TTL: Automatic
• Public Networking status in Railway:
  • vi ora-be-prod.up.railway.app → Works fine (Metal Edge)
  • vi ora-app.xyz → Shows "Failed to issue TLS certificate" with error: "An internal error occurred. Please retry or contact support."
  • Also has a port mapping to 8080 (Metal Edge)
• Steps I've tried:
  1. Added the domain in Railway settings → Got the CNAME target → Set CNAME @ in Namecheap.
  2. Verified DNS propagation using dnschecker.org (CNAME resolves correctly to Railway endpoint in most locations).
  3. Waited >1 hour for propagation and cert issuance.
  4. Clicked "Try Again" multiple times → Still fails with internal error.
  5. No proxy/CDN like Cloudflare is enabled (direct from Namecheap).

Additional info:

• The domain is apex (@), not a subdomain.
• No CAA records or other restrictions on Namecheap side (as far as I know).
• Can access the app via the Railway-provided domain (*.up.railway.app) without issues.

Could you please check on your end:

• If there's a stuck provisioning job or queue issue for this domain?
• Reset the certificate issuance process?
• Confirm if the CNAME is being resolved correctly from Railway's perspective?
• Any known issues with apex CNAME on Namecheap + Metal Edge?

Happy to provide screenshots, project ID, or join a private thread if needed.

Thank you for your help!

Best regards,