Subject: Custom domain stuck — certificate not issuing / not routing

Hi — I have a custom domain that's been stuck for several days and I've

exhausted the usual fixes. Could you look into the certificate provisioning?

Details:

• Project: aiva-portal (id: 51b27f1a-a8e8-47da-9006-39867e3d3f44)

• Service: aiva-portal (id: 6492972d-999e-4c15-828a-6b13ec4fd4ce)

• Environment: production

• Custom domain: app.aivavi.ai

• Required CNAME target Railway gave me: 6st8n6pu.up.railway.app

What's correct:

• DNS is correct — app.aivavi.ai resolves to 6st8n6pu.up.railway.app

(verified via Google DNS / 8.8.8.8).

• No CAA records are blocking Let's Encrypt on aivavi.ai.

• The Railway-provided domain (aiva-portal-production.up.railway.app) works

fine over HTTPS, so the service and deployment are healthy.

The problem:

• https://app.aivavi.ai fails the TLS handshake (no valid certificate) —

curl returns HTTP 000 with an SSL cert error.

• http://app.aivavi.ai (ignoring cert) returns 404 from the edge, as if the

domain isn't routed to the service.

What I've already tried:

• Added the CNAME exactly as instructed.

• Removed the custom domain and re-added it (got the new 6st8n6pu target,

updated DNS to match) — still stuck.

• Waited several days.

Could you re-provision / force-issue the certificate for app.aivavi.ai and

confirm it's routed to the service? Thank you!