I can't connect to all sites, the error code is "SEC_ERROR_UNKNOWN_ISSUER", can you help me?
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: putrisarinadia50, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
Firefox for Android
Steps to reproduce:
I can't connect to all sites, the error code is "SEC_ERROR_UNKNOWN_ISSUER", can you help me?
I'm currently using FF version 63.0.3 on Windows 10, I've tried deleting cert8.db, running FF in safe mode, even reinstalling FF, but still no luck. I also only use SMADAV 2023 and Windows Defender as an antivirus. Only official Mozilla sites can be accessed.
the official website site still has no response about this error, maybe you can visit here https://smadav-2023.blogspot.com/
As I recall, this problem started when I accidentally switched to a site. Can you help me?
And sorry if my grammar is bad, English is not my first language.
Comment 1•3 years ago
|
||
Clearing the security flag as this isn't the kind of security issue that puts Firefox users at risk if it's public
I'm currently using FF version 63.0.3 on Windows 10
This is very old (4.5 years). Can you not run an up-to-date version of Firefox? That would probably help.
Updated•3 years ago
|
| Reporter | ||
Comment 2•3 years ago
|
||
it's understandable that my computer is a bit old school but I can still operate Mozilla quite well on that version, maybe I'll try to update the latest version now, thank you for the help you have answered, thank you very much for helping
Comment 3•3 years ago
|
||
Hi @putrisarinadia, does this issue still occur on your end after the latest update ? I was able to reach that website without issues, I do not have that AV installed, maybe theres something from the AV that blocks certain websites ?
Comment 4•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 5•2 years ago
|
||
Closing this issue as incomplete for now and we will reopen if the issue still occurs on the reporters side.
Description
•