Project: qromo (e6edbdce-0b76-4765-9822-7c25e04c8962)

Environment: production

Service: qromo-app (56f2625f-edd7-4833-bd88-98fda519d0ad)

Custom domain: saltacassa.villavardabistrot.it

Assigned CNAME target: uwyixmmv.up.railway.app

The domain has been stuck on "Waiting for DNS update" for over 2 hours

and the TLS certificate has never been issued.

DNS is correct and fully propagated. Verified from the authoritative

nameservers (Netsons) and from public resolvers (8.8.8.8, 1.1.1.1,

9.9.9.9, 208.67.222.222):

saltacassa.villavardabistrot.it. 180 IN CNAME uwyixmmv.up.railway.app.

uwyixmmv.up.railway.app. -> 69.46.46.96

There are no CAA records on the zone that would block Let's Encrypt.

Current behaviour:

• http://saltacassa.villavardabistrot.it -> 301 redirect to https (edge responds)

• https://saltacassa.villavardabistrot.it -> serves the default *.up.railway.app

  certificate (hostname mismatch) and returns 404

So the edge is reachable, but the hostname is not attached to the service.

I already removed and re-added the domain once (that is when the target

changed from j3mrrx6i to uwyixmmv) and updated the DNS record accordingly.

The behaviour did not change.

The service itself is healthy and serves correctly on its Railway domain:

https://qromo-app-production.up.railway.app

Could you check why the domain verification is not completing on your side?