Technically, some browsers cache intermediate certificates which they already saw on connections to other sites. Then these browsers typically don’t bother the missing intermediate certificate sent by the server but use their cached copy, and everything looks right. Only browsers which don’t have the cached certificate are out of luck, which happens typically if you don’t use that browser regularly. Then it looks as if that browser had a bug because your site can be visited by other browsers and perhaps a lot of people flawlessly.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
On Android 6.0.1 the Certificate is untrusted | 10 | 15808 | December 28, 2015 | |
Certificate not trusted on android | 21 | 13007 | April 2, 2017 | |
Let's Encrypt cert not trusted by Android | 4 | 11717 | May 7, 2018 | |
Untrusted on mobile (newbe) | 3 | 2137 | December 29, 2015 | |
SSL on Mobile isn't trusted | 12 | 4106 | August 3, 2016 |