AdGuard Home v0.107.52

In this release we have fixed a number of bugs, migrated our front-end to TypeScript and updated our front-end libraries to improve the quality of development and your user experience.

Acknowledgements

A special thanks to our community moderation 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.52 GitHub milestone.

Security

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

Added

• The ability to disable logging using the new log.enabled configuration property (#7079).

Changed

• Frontend rewritten in TypeScript.

• The systemd-based service now uses journal for logging by default. It also doesn't create the /var/log/ directory anymore (#7053).

  NOTE: With an installed service for changes to take effect, you need to reinstall the service using -r flag of the install script or via the CLI (with root privileges):

  ./AdGuardHome -s uninstall
  ./AdGuardHome -s install

  Don't forget to backup your configuration file and other important data before reinstalling the service.

Deprecated

• Node 18 support, Node 20 will be required in future releases.

Fixed

• Panic caused by missing user-specific blocked services object in configuration file (#7069).

• Tracking /etc/hosts file changes causing panics within particular filesystems on start (#7076).

AdGuard Home v0.108.0-b.57

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

Acknowledgements

A special thanks to our community moderation team, @AdguardTeam/community-moderators, 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 Go 1.22.5.

Added

• The ability to disable logging using the new log.enabled configuration property (#7079).

Changed

• Frontend rewritten in TypeScript.

• The systemd-based service now uses journal for logging by default. It also doesn't create the /var/log/ directory anymore (#7053).

  NOTE: With an installed service for changes to take effect, you need to reinstall the service using -r flag of the install script or via the CLI (with root privileges):

  ./AdGuardHome -s uninstall
  ./AdGuardHome -s install

  Don't forget to backup your configuration file and other important data before reinstalling the service.

• The HTTP server's write timeout has been increased from 1 minute to 5 minutes to match the one used by AdGuard Home's HTTP client to fetch filtering-list data (#7041).

Deprecated

• Node 18 support, Node 20 will be required in future releases.

Fixed

• Unnecessary validation call on the encryption page.
• Missing version in the footer.
• Panic caused by missing user-specific blocked services object in configuration file (#7069).
• Tracking /etc/hosts file changes causing panics within particular filesystems on start (#7076).

AdGuard Home v0.107.51

A small bugfix and security release. We are working on new features in future releases.

Full changelog

See also the v0.107.51 GitHub milestone.

Security

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

Changed

• The HTTP server's write timeout has been increased from 1 minute to 5 minutes to match the one used by AdGuard Home's HTTP client to fetch filtering-list data (#7041).

AdGuard Home v0.108.0-b.56

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

Acknowledgements

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

Full changelog

Fixed

• Broken private reverse DNS upstream servers validation causing update failures (#7013).

AdGuard Home v0.107.50

They say, if it isn't broken — don't fix it. Unfortunately, this is not the case with the last AdGuard Home update 😓 A small portion of users haven't been able to start AdGuard Home at all, and so we are rolling out this hotfix.

Acknowledgements

A special thanks to our community moderation 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.50 GitHub milestone.

Fixed

• Broken private reverse DNS upstream servers validation causing update failures (#7013).

AdGuard Home v0.107.49

Fast approaching summer promises everyone its warmth, and all kinds of bugs are crawling from under the rocks and twigs to enjoy the sun 🌞. Here's a patch to make sure that they stay in the grass and nowhere near AdGuard Home.

Acknowledgements

A special thanks to our community moderation team, @AdguardTeam/community-moderators, contributor @looklose, 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 Go 1.22.3.

Added

• Support for comments in the ipset file (#5345).

Changed

• Private rDNS resolution now also affects SOA and NS requests (#6882).

• Rewrite rules mechanics were changed due to improved resolving in safe search.

Deprecated

• Currently, AdGuard Home skips persistent clients that have duplicate fields when reading them from the configuration file. This behaviour is deprecated and will cause errors on startup in a future release.

Fixed

• Acceptance of duplicate UIDs for persistent clients at startup. See also the section on client settings on the Wiki page.

• Domain specifications for top-level domains not considered for requests to unqualified domains (#6744).

• Support for link-local subnets, i.e. fe80::/16, as client identifiers (#6312).

• Issues with QUIC and HTTP/3 upstreams on older Linux kernel versions (#6422).

• YouTube restricted mode is not enforced by HTTPS queries on Firefox.

• Support for link-local subnets, i.e. fe80::/16, in the access settings (#6192).

• The ability to apply an invalid configuration for private RDNS, which led to server inoperability.

• Ignoring query log for clients with ClientID set (#5812).

• Subdomains of in-addr.arpa and ip6.arpa containing zero-length prefix incorrectly considered invalid when specified for private RDNS upstream servers (#6854).

• Unspecified IP addresses aren't checked when using "Fastest IP address" mode (#6875).

AdGuard Home v0.108.0-b.55

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

Acknowledgements

A special thanks to our community moderation team, @AdguardTeam/community-moderators, contributor @looklose, 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 Go 1.22.3.

Added

• Support for comments in the ipset file (#5345).

Changed

• Private rDNS resolution now also affects SOA and NS requests (#6882).

• Rewrite rules mechanics was changed due to improve resolving in safe search.

Deprecated

• Currently, AdGuard Home skips persistent clients that have duplicate fields when reading them from the configuration file. This behaviour is deprecated and will cause errors on startup in a future release.

Fixed

• Acceptance of duplicate UIDs for persistent clients at startup. See also the section on client settings on the Wiki page.

• Domain specifications for top-level domains not considered for requests to unqualified domains (#6744).

• Support for link-local subnets, i.e. fe80::/16, as client identifiers (#6312).

• Issues with QUIC and HTTP/3 upstreams on older Linux kernel versions (#6422).

• YouTube restricted mode is not enforced by HTTPS queries on Firefox.

• Support for link-local subnets, i.e. fe80::/16, in the access settings (#6192).

• The ability to apply an invalid configuration for private rDNS, which led to server not starting.

• Ignoring query log for clients with ClientID set (#5812).

• Subdomains of in-addr.arpa and ip6.arpa containing zero-length prefix incorrectly considered invalid when specified for private rDNS upstream servers (#6854).

• Unspecified IP addresses aren't checked when using "Fastest IP address" mode (#6875).

AdGuard Home v0.107.48

After the last update it became possible for banned users to make DNS queries over encrypted protocols. This behavior, of course, was not intended, and is fixed by this hotfix.

We apologize for this oversight and will do our best to avoid repeating such mistakes in the future.

Full changelog

See also the v0.107.48 GitHub milestone.

Fixed

• Access settings not being applied to encrypted protocols (#6890)

AdGuard Home v0.107.47

Another security and bug fix update, but this time we also fix a 🕒 time zone selection issue and a few other annoying bugs!

Acknowledgements

A special thanks to our community moderation 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.47 GitHub milestone.

Security

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

Changed

• Time Zone Database is now embedded in the binary (#6758).

• Failed authentication attempts show the originating IP address in the logs, if the request came from a trusted proxy (#5829).

Deprecated

• Go 1.22 support. Future versions will require at least Go 1.23 to build.

• Currently, AdGuard Home uses a best-effort algorithm to fix invalid IDs of filtering-rule lists on startup. This feature is deprecated, and invalid IDs will cause errors on startup in a future version.

• Node.JS 16. Future versions will require at least Node.JS 18 to build.

Fixed

• Resetting DNS upstream mode when applying unrelated settings (#6851).

• Symbolic links to the configuration file begin replaced by a copy of the real file upon startup on FreeBSD (#6717).

Removed

• Go 1.21 support.

AdGuard Home v0.107.46

As promised in the notes for the previous release, this update brings some quality-of-life improvements as well as a few bug fixes 🔧.

Full changelog

See also the v0.107.46 GitHub milestone.

Added

• Ability to disable the use of system hosts file information for query resolution (#6610).

• Ability to define custom directories for storage of query log files and statistics (#5992).

Changed

• Private rDNS resolution (dns.use_private_ptr_resolvers in YAML configuration) now requires a valid "Private reverse DNS servers", when enabled (#6820).

  NOTE: Disabling private rDNS resolution behaves effectively the same as if no private reverse DNS servers provided by user and by the OS.

Fixed

• Statistics for 7 days displayed by day on the dashboard graph (#6712).

• Missing "served from cache" label on long DNS server strings (#6740).

• Incorrect tracking of the system hosts file's changes (#6711).