SSL error on the site with custom domain

Hi gents,

I have two sites published through the sites / pages feature. One (noizeramp.com) works fine...

```
→ curl -v https://noizeramp.com
* Trying 18.214.166.21...
* TCP_NODELAY set
* Connected to noizeramp.com (18.214.166.21) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=noizeramp.com
* start date: May 24 23:10:23 2020 GMT
* expire date: Aug 22 23:10:23 2020 GMT
* subjectAltName: host "noizeramp.com" matched cert's "noizeramp.com"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
...
```

... and the other (caterokbags.ru) returns:

```
→ curl -v https://caterokbags.ru
* Trying 18.214.166.21...
* TCP_NODELAY set
* Connected to caterokbags.ru (18.214.166.21) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS alert, internal error (592):
* error:14004438:SSL routines:CONNECT_CR_SRVR_HELLO:tlsv1 alert internal error
* Closing connection 0
curl: (35) error:14004438:SSL routines:CONNECT_CR_SRVR_HELLO:tlsv1 alert internal error
```

I waited half a day. Do I have to wait more for the SSL certs to configure?

They are identically configured with DNS provider. In case that matters, both are verified as my own websites with TXT records. Both are contacted through the same IP (18.214.166.21). Yet one responds and the other fails with the SSL handshake error.

Can anyone kindly suggest what am I doing wrong? What kind of info do we need to troubleshoot this?

Start with the curl -v traces for noizeramp.com and caterokbags.ru, then compare the custom-domain DNS and TXT-record configuration described in the issue. Determine why one domain completes the TLS handshake while the other returns an internal error; done means identifying a concrete configuration or service-side cause and documenting the required fix.

Written by the indexing model from the issue text.