I’m using, and still work fine, let’s encrypt certificates for our https and wss services, are servers that expose WebRTC based services using Chrome as client default browser.
Since i’ve updated to new MacOS “Sierra” the browser (Chrome) stop accepting SSL certificates on port different from 443.
If i call the site via https on pert 443 the browser correctly detect the certificate and set it as trusted, but if I try to connect in HTTPS to any other port the certificate valid at port 443 is not anymore valid.
This happens only under macOS Sierra and not on other OSX versions with Chrome, just to explain, same version of Chrome 53.xxxx on MacOS Sierra does not trust Let’s Encrypt certificate if not exposed on port 443 (Not valid CA Chrome says) same Chrome version, 53.xxxx, but on MacOSX El Capitan or previous, accept the Let’s Encrypt certificate as trusted.
What I’ve to do? People are saying that is the certificate not correct for TLS but it worked until macOS has been updated and does not work only under macOS Sierra.
Have any suggest to solve the issue, mainly are let’s encrypt certificates valid certificates for SSL/TLS and can be used with port different from 443?
Looking forward to hearing from you, best regards,