From yesterday some of our clients are having issue loading the site. It shows the site is insecure. It is not the same for everyone. It loads fine for some and breaks for others. In some cases the page loads, but APIs sent on post method breaks. This is so weird. Please help us resolve this.
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
An unexpected error occurred:
SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:765)
Please see the logfiles in /var/log/letsencrypt for more details.
Your server is sending the long Android-compatible certificate chain. There are currently two chains available, both with different compatibility.
This chain is compatible with Android < 7.1, but is known to break OpenSSL < 1.1 (and other smaller TLS libraries). What TLS libraries (and versions) are your clients using? You might need to switch to the shorter chain, which is compatible with older OpenSSL, but incompatible with old Android.
I hope the silence here is a good thing or that you are/well be, at least, well rested and ready to tackle this problem soon
We are here should you need us.
Our clients are mostly from mobile users. So, we need to support all android & iOS users.
Also, what do you mean by "need to be applied on every client". Does it mean, we should do modifications in every client device?
Is it possible that phantomJS could breaks in this process? It is not loading css & font files.
That may not even be possible any longer when using a single LE cert trust path.
There are two trust paths and they each serve a different aged set of devices.
the longer path is useful in serving older Android devices but may cause problems with iOS
the shorter path is useful in serving modern devices but will cause problems with older Androids
We have multiple domains that our clients access. We can't point each one to 2 different domains.
Isn't there any other way we can make it work? If not, could you please suggest another free CA.