AdGuard Home - Package Updates

Package Updates

[1.13.1]

Update AdGuardHome to 0.108.0-b.65
Full Changelog
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.
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.

Package Updates

[1.13.2]

Update AdGuardHome to 0.108.0-b.66
Full Changelog
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.24.2][go-1.24.2].
Node 20 support, Node 22 will be required in future releases.
Filtering for DHCP clients (#7734).
Validation process for the HTTPS port on the Encryption Settings page.
Node 18 support.

Package Updates

[1.13.3]

Update AdGuardHome to 0.108.0-b.67
Full Changelog
Any simultaneous requests that are considered duplicates will now only result in a single request to upstreams, reducing the chance of a cache poisoning attack succeeding. This is controlled by the new configuration object pending_requests, which has a single enabled property, set to true by default.
Incorrect label on login page (#7729).

Package Updates

[1.14.0]

Switch to stable version 0.107.61 . The unstable verison contains experimental features which are breaking TLS .

Package Updates

[1.14.1]

Update AdGuardHome to 0.107.62
Full Changelog
Clients with CIDR identifiers showing zero requests on the Settings Client settings page ([#2945]).
Command line option --update when the dns.serve_plain_dns configuration property was disabled ([#7801]).
DNS cache not working for custom upstream configurations.
Validation process for the DNS-over-TLS, DNS-over-QUIC, and HTTPS ports on the Encryption Settings page.
Searching for persistent clients using an exact match for CIDR in the POST /clients/search HTTP API.

Package Updates

[1.14.2]

Update AdGuardHome to 0.107.63
Full Changelog
The hostnames of DHCP clients with multiple labels not being recognized.
Status reported by the systemd service implementation in cases of auto-restart after a failed start.

Package Updates

[1.14.3]

Package Updates

[1.14.4]

Update AdGuardHome to 0.107.65
Full Changelog
A separate checkbox in the Web UI to enable or disable the global DNS response cache without losing the configured cache size.
A new "cache_enabled" field to the HTTP API (GET /control/dns_info and POST /control/dns_config). See openapi/openapi.yaml for the full description.
In this release, the schema version has changed from 29 to 30.
Added a new boolean field dns.cache_enabled to the configuration. This field explicitly controls whether DNS caching is enabled, replacing the previous implicit logic based on dns.cache_size.
To roll back this change, set the schema_version back to 29.
Disabled state of Top clients action button in web UI ([#7923]).

Package Updates

[1.14.5]

Update AdGuardHome to 0.107.66
Full Changelog
Support for configuring the suggested default HTTP port for the installation wizard via the ADGUARD_HOME_DEFAULT_WEB_PORT environment variable (useful for vendors).
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.25.1][go-1.25.1].
Optimized matching of filtering rules.
Our snap package now uses the core24 image as its base.
Outgoing HTTP requests now use the User-Agent header AdGuardHome/v0.107.66 (where v0.107.66 is the current version) instead of Go-http-client/1.1 ([#7979]).
Lowered the severity of log messages for failed deletion of old filter files ([#7964]).
Authentication errors in the Web UI when AdGuard Home is behind a proxy that sets Basic Auth headers ([#7987]).
The HTTP API GET /control/profile endpoint failing when no users were configured ([#7985]).
Missing warning on the Encryption Settings page when using a certificate without an IP address.

Package Updates

[1.14.6]

Update AdGuardHome to 0.107.67
Full Changelog
New fields "groups" and "group_id" added to the HTTP API (GET /control/blocked_services/all). See openapi/openapi.yaml for the full description.
The HaGeZi's DNS Rebind Protection filter for protecting against DNS rebinding attacks ([#102]).
Support for configuring the suggested default HTTP port for the installation wizard via the ADGUARD_HOME_DEFAULT_WEB_PORT environment variable (useful for vendors).
Optimized matching of filtering rules.
Excessive configuration file overwrites when visiting the Web UI and a non-empty language is set.
Lowered the severity of log messages for failed deletion of old filter files ([#7964]).

Cloudron Forum