Normally that is the intermediate certificate for the DST root. When the response comes back from Lets Encrypt (LE) with the certificate it contains a list of links to the intermediate certificates that LE uses, right now the extension just takes the first certificate from that list and bundles that with the certificate that you requested. I need to release a version with more debugging turned on, to properly investigate what goes wrong. I can’t see any way (from the video) that this could happen by I just renewed a few of my own sites manually yesterday to see if I could reproduce the error. If I were you, I’d probably report thi**s weirdness to the site extension author. Issuer: O = Digital Signature Trust Co., CN = DST Root CA X3 And that issuer, as of today, is still the Identrust/DST one: **I checked the linked Azure Site Extension, and it should be taking the issuer from the CA ( ). It’s also weird that it is using the ISRG intermediate at all. IN THE THREAD from the COMMUNITY someone wrote this: 99 Android 6.0.1 and it said my site was not secure, I tried it on firefox and it said I was not secure, but I then upgraded firefox and it worked. I then tried it on my Android Device using Chrome. On chrome my app worked, on IE it worked also. I followed the directions from this video: It may help to read this thread, they said I should alert you
0 Comments
Leave a Reply. |