New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mozilla CA Store doesn't have AdGuard Certificate #4813
Comments
I forgot to mention that it is possible to install certificate manually into Firefox |
@MichaelDavidGK Hi there!
|
hi (●’◡’●)ノ
I also said above in a comment that you can install the cert manually |
I tried this version of Firefox as well.
Ok thank you. |
@MichaelDavidGK any update? |
hi, sorry for late update. Anyway after reinstall of AdGuard (stable 7.14, haven't checked beta): Happens on stable firefox 116.0.3 as well I also noticed that AdGuard doesn't set proxy automatically upon install/reinstall of certificate, unlike it is specified in manual installation. Could that be an issue? |
@MichaelDavidGK ,
|
Works after reinstalling cert manually and restarting browser. Seems it was Windows issue (on fresh install of latest ISO, no less...) Feel free to close it I guess |
We're glad to hear your issue was gone. Thanks for a feedback, I'm closing this task. |
AdGuard version
7.15.0
Browser version
Firefox Dev 117.0b9
OS version
Win 11 22H2
What filters do you have enabled?
AdGuard Base filter, AdGuard Tracking Protection filter, AdGuard Annoyances filter
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Firefox informing or preventing accessing sites due to safety issues.
It happens even when HTTPS Certificate is installed on Windows.
Most likely it is being raised due to that Mozilla CA Store doesn't have AdGuard Certificate for HTTPS filtering as indicated in error message.
While for some sites user can bypass it (imgur), for some they cannot (google).
Screenshots are attached.
Expected Behavior
Firefox allowing to open sites without issues
Screenshots
Additional Information
No response
The text was updated successfully, but these errors were encountered: