All search engines and YouTube "Did Not Connect: Potential Security Issue"
Hey all,
I updated Windows the other night and ever since then, Firefox will give me certificate errors for only Youtube and all search engines. I tried Refreshing Firefox and reinstalling it, but that didn't fix the issue. I've scanned my computer for malware and found nothing. I've attached an image of what is being shown below. I looked at common issues with the "Error code: SEC_ERROR_UNKNOWN_ISSUER" message as well, but nothing has worked.
Just trying to see if there's something I'm missing here, really have no clue what to do and why only these websites are effected.
Thanks for any and all help.
วิธีแก้ปัญหาที่เลือก
cor-el said
Who is the issuer of the certificate if you click the button in "View certificate" button ? You can also possibly attach the base64 encode certificate data, so we can inspect it. Click the blue SEC_ERROR_UNKNOWN_ISSUER text.
I was able to find a thread from someone with the same issue, and it was resolved through turning off a proxy setting in Options -> Network Settings. Dunno how this affected me personally, but it might be because I switched to Xfinity or something. Regardless, the issue is resolved now, so thanks for the response!
อ่านคำตอบนี้ในบริบท 👍 0การตอบกลับทั้งหมด (3)
For some reason the original message didn't attach my image, so here it is.
Who is the issuer of the certificate if you click the button in "View certificate" button ?
You can also possibly attach the base64 encode certificate data, so we can inspect it. Click the blue SEC_ERROR_UNKNOWN_ISSUER text.
วิธีแก้ปัญหาที่เลือก
cor-el said
Who is the issuer of the certificate if you click the button in "View certificate" button ? You can also possibly attach the base64 encode certificate data, so we can inspect it. Click the blue SEC_ERROR_UNKNOWN_ISSUER text.
I was able to find a thread from someone with the same issue, and it was resolved through turning off a proxy setting in Options -> Network Settings. Dunno how this affected me personally, but it might be because I switched to Xfinity or something. Regardless, the issue is resolved now, so thanks for the response!