This hotfix addresses the bug that was introduced with the previous update, namely the bug that prevented users from entering anything into the search box in the Query log. We also took this opportunity to include another fix for the incorrect functioning of the client modifier.

Acknowledgments

A special thanks to our community moderators team, @AdguardTeam/community-moderators, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.59 GitHub milestone.

Fixed

• Rules with the client modifier not working (#7708).

• The search form not working in the query log (#7704).

Changes compared to the previous beta, v0.108.0-b.64. See CHANGELOG.md for all changes.

Full changelog

Added

• The ability to check filtering rules for host names using an optional query type and optional ClientID or client IP address (#4036).

• Optional client and qtype URL query parameters to the GET /control/check_host HTTP API.

Fixed

• Rules with the client modifier not working (#7708).

• The search form not working in the query log (#7704).

• Clearing the DNS cache on the DNS settings page now includes both global cache and custom client cache.

Here’s a philosophical question for you: if a release contains more bugfixes than usual, is it good or is it bad? 🤔
Luckily, we are developers and not philosophers, so let’s state some facts and leave thought experiments to those wiser than us. And the facts are, we've fixed a bunch of bugs in this update, but also added a neat little feature that we'd like to elaborate on.

An improved tool to check DNS queries

If you are serious about protecting your privacy and dealing with ads, chances are you have loads of rules, both as filter lists and as parts of a custom ruleset. Now, any time you're tweaking your filter arsenal, there is an easy way to check if a certain DNS query will be blocked. We've built upon the already-existing tool and added options to indicate DNS record type and specific client, either by IP address or by ClientID. Enter the information and behold all the rules that match your request. Bonus feature: you can unblock any domain right then and there. Happy blocking!

Acknowledgments

A special thanks to our open-source contributors: @bankjirapan, @dervomsee, and @viraniac, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.58 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.1.

Added

• The ability to check filtering rules for host names using an optional query type and optional ClientID or client IP address (#4036).

• Optional client and qtype URL query parameters to the GET /control/check_host HTTP API.

Fixed

• Clearing the DNS cache on the DNS settings page now includes both global cache and custom client cache.

• Invalid ICMPv6 Router Advertisement messages (#7547).

• Disabled button for autofilled login form.

• Formatting of elapsed times less than one millisecond.

• Changes to global upstream DNS settings not applying to custom client upstream configurations.

• The formatting of large numbers in the clients tables on the Client settings page (#7583).

Changes compared to the previous beta, v0.108.0-b.63. See CHANGELOG.md for all changes.

Acknowledgments

A special thanks to our open-source contributors: @bankjirapan, @dervomsee, and @viraniac, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.1.

Fixed

• Invalid ICMPv6 Router Advertisement messages (#7547).

• Disabled button for autofilled login form.

• Formatting of elapsed times less than one millisecond.

• Changes to global upstream DNS settings not applying to custom client upstream configurations.

• The formatting of large numbers in the clients tables on the Client settings page (#7583).

The year 2025 is only picking up steam, but some of us already need a time out 🕙 Speaking of timeouts, in the new version we've added the ability to specify the upstream timeout in the Web UI, alongside with some bug fixes and security updates.

Acknowledgments

A special thanks to our open-source contributor @janpieper, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.57 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.6.

Added

• The ability to specify the upstream timeout in the Web UI.

Changed

• The Fastest IP address upstream mode now correctly collects statistics for all upstream DNS servers.

Fixed

• The hostnames of DHCP clients not being shown in the Top clients table on the dashboard (#7627).

• The formatting of large numbers in the upstream table and query log (#7590).

Changes compared to the previous beta, v0.108.0-b.62. See CHANGELOG.md for all changes.

Acknowledgments

A special thanks to our open-source contributor @janpieper, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.6.

Added

• The ability to specify the upstream timeout in the Web UI.

Changed

• The Fastest IP address upstream mode now collects statistics for the all upstream DNS servers.

Fixed

• The hostnames of DHCP clients not being shown in the Top clients table on the dashboard (#7627).

• The formatting of large numbers in the upstream table and query log (#7590).

We are steadily picking up the pace in the new year, starting with this small update. 🏃 Inside are some fresh bugfixes, a new API, and an updated Go version to shore up some vulnerabilities.

Acknowledgments

A special thanks to our open-source contributor @Hermholtz, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.5.

Added

• The new HTTP API POST /clients/search that finds clients by their IP addresses, CIDRs, MAC addresses, or ClientIDs. See openapi/openapi.yaml for the full description.

Deprecated

• The GET /clients/find HTTP API is deprecated. Use the new POST /clients/search API.

Fixed

• Request count link in the clients table (#7513).
• The formatting of large numbers on the dashboard (#7329).

Changes compared to the previous beta, v0.108.0-b.61. See CHANGELOG.md for all changes.

Acknowledgments

A special thanks to our open-source contributor @Hermholtz, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.5.

Added

• The new HTTP API POST /clients/search that finds clients by their IP addresses, CIDRs, MAC addresses, or ClientIDs. See openapi/openapi.yaml for the full description.

Deprecated

• The GET /clients/find HTTP API is deprecated. Use the new POST /clients/search API.

Fixed

• Request count link in the clients table (#7513).
• The formatting of large numbers on the dashboard (#7329).

Time for another release! We encourage all Windows users to play close attention as it addresses a bug that has been affecting some Windows installations. For the rest of AdGuard Home aficionados, we've updated Go version to shore up some vulnerabilities and have dealt with a couple leaks 🚰

Acknowledgments

A special thanks to our open-source contributor, @MaggieFero, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.55 GitHub milestone.

Security

• The permission check and migration on Windows has been fixed to use the Windows security model more accurately (#7400).

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.4.

• The Windows executables are now signed.

Added

• The --no-permcheck command-line option to disable checking and migration of permissions for the security-sensitive files and directories, which caused issues on Windows (#7400).

Fixed

• Setup guide styles in Firefox.

• Goroutine leak during the upstream DNS server test (#7357).

• Goroutine leak during configuration update resulting in increased response time (#6818).

Changes compared to the previous beta, v0.108.0-b.60. See CHANGELOG.md for all changes.

Acknowledgments

A special thanks to our open-source contributor @MaggieFero, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

Security

• The permission check and migration on Windows has been fixed to use the Windows security model more accurately (#7400).
• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.4.

Added

• The --no-permcheck command-line option to disable checking and migration of permissions for the security-sensitive files and directories, which caused issues on Windows (#7400).

Fixed

• Goroutine leak during the upstream DNS server test (#7357).
• Goroutine leak during configuration update resulting in increased response time (#6818).