In app platform a custom domain was configured but no HTTPS certificate generated, how come?

I created an app based on a docker container image from a digital ocean registry. The apps works fine on the domainname provided by the app platform. This domain name is something like https://<name-of-app>-<hash>.ondigitalocean.app/. As said the app works fine.

In settings I enabled a ‘custom’ domain, lets call it: https://myapp.example.com . A the domain name is managed by digitalocean and I can see that the platform created a CNAME record myapp.example.com IN CNAME <name-of-app>-<hash>.ondigitalocean.app 1800. However in the settings I can see that this new domain is stuck ‘configuring’ for days now. I guess it is stuck in the creation of the https certificate.

When visiting https://myapp.example.com I see that I get a response: “The site does not support a secure connection. myapp.example.com uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH” (message from a chrome backed browser - other browsers give similar message. SSLlabs reports it cannot communicate with the server securely well.)

I tried several different apps, but all seem to fail. Also it does not matter if i tried ‘basic’ setups (testing) or ‘production’ setups. It is in the AMS3 region.

I suggest something is wrong in the cert manager of either digital ocean app platform bound to the region. (hmm I could try another region as well indeed)