-
Notifications
You must be signed in to change notification settings - Fork 7
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
Certificate verification fails on sites with recently updated certs #1833
Comments
Я с подобным сталкивался в версии 7.15.1 в момент обновления фильтров + в течение 8-10 минут после их обновления. |
@zubrRB А есть какие-нибудь проги, которые работают с сетью (антивирусы, фаерволы, отладчики)? |
Это я сталкивался в 7.15.1 и всегда в такие момент замечал по трею, что это происходило после обновления фильтров. |
AdguardTeam/AdguardFilters#167736 |
HTTPS filtering does not work, site does not accept AG certificate. |
Problem with Let's Encrypt certificates. |
Caused by the new "Certificate Transparency verification" code in CL1.12. It was added because AdGuard uses the same checks as browsers do, and Chrome does this check. However, there was error in implementation - expired CT log list was applied. This problem will be fixed in the current release cycle, you may want to switch to beta to workaround this problem. |
Thank you for the explanation, sfionov! 😊 |
Not closing until products are released |
Original reports Windows and Macos:
AdguardTeam/AdguardFilters#167902
AdGuard for Mac v2.12.2.1415 release
macOS Ventura
Chrome
AdGuard for Windows v7.15.1 (4386)
Yandex Browser
Reproduced in Macos 13.3 with AdGuard 2.12.1.1398
Not sure if it is related to UDP connections.
The text was updated successfully, but these errors were encountered: