>>Modern browsers don't like SSL certs that use insecure algorithms.
>>
>>There are also reports of BitDefender being too aggressive:
https://productforums.google.com/forum/#!msg/chrome/-LjiIraWUqk/ITm4JpdQAAAJ>
>I also had to deal with a situation, once, where a certificate was not properly recognized with all browsers. The issue was simply resolved by re-issueing the certificate with another authority.
Yes, sometimes browser makers revoke formerly trusted certs e.g. Symantec, WoSign while other browsers don't. In that case some will work and others won't.
In the OP's case Chrome conveniently shows a useful error code ERR_CERT_WEAK_SIGNATURE_ALGORITHM which is pretty unambiguous.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
