AdGuard Home - Package Updates
- 
[1.11.0] - set checklist
 
- 
[1.12.0] - Update AdGuardHome to 0.108.0-b.64
- Full Changelog
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.24.1][go-1.24.1].
- 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).
 
- 
[1.13.0] - Update base image to 5.0.0
 
- 
[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 clientandqtypeURL query parameters to theGET /control/check_hostHTTP API.
- Rules with the clientmodifier 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.
 
- 
[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.
 
- 
[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 singleenabledproperty, set totrueby default.
- Incorrect label on login page (#7729).
 
- 
[1.14.0] - Switch to stable version 0.107.61 . The unstable verison contains experimental features which are breaking TLS .
 
- 
[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 --updatewhen thedns.serve_plain_dnsconfiguration 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/searchHTTP API.
 
- 
[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.
 
- 
[1.14.3] - Update AdGuardHome to 0.107.64
- Full Changelog
- TTL override calculation ([#7903]).
- Validation process for DNSCrypt settings ([#7856]).
 
- 
[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_infoandPOST /control/dns_config). Seeopenapi/openapi.yamlfor the full description.
- In this release, the schema version has changed from 29 to 30.
- Added a new boolean field dns.cache_enabledto the configuration. This field explicitly controls whether DNS caching is enabled, replacing the previous implicit logic based ondns.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]).
 
- 
[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_PORTenvironment 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 core24image as its base.
- Outgoing HTTP requests now use the User-AgentheaderAdGuardHome/v0.107.66(wherev0.107.66is the current version) instead ofGo-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/profileendpoint failing when no users were configured ([#7985]).
- Missing warning on the Encryption Settings page when using a certificate without an IP address.
 
- 
[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). Seeopenapi/openapi.yamlfor 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_PORTenvironment variable (useful for vendors).
- Optimized matching of filtering rules.
- Excessive configuration file overwrites when visiting the Web UI and a non-empty languageis set.
- Lowered the severity of log messages for failed deletion of old filter files ([#7964]).
 
- 
[1.14.7] - Update AdGuardHome to 0.107.68
- Full Changelog
- New DNS rewrite settings endpoints GET /control/rewrite/settingsandPUT /control/rewrite/settings/update. Seeopenapi/openapi.yamlfor details.
- New fields "groups"and"group_id"added to the HTTP API (GET /control/blocked_services/all). Seeopenapi/openapi.yamlfor the full description.
- POST /control/rewrite/addand- PUT /control/rewrite/updatenow accept the optional field "enabled". See- openapi/openapi.yamlfor details.
- In this release, the schema version has changed from 30 to 31.
- Added a new boolean field filtering.rewrites_enabledto globally enable/disable DNS rewrites.
- Added a new boolean field enabledfor each entry infiltering.rewritesto toggle individual rewrites.
- The outdated querylog anonymization script.
 
- 
[1.14.8] - Update AdGuardHome to 0.107.69
- Full Changelog
- DHCP settings could not be saved ([#8075]).
- DNS Rewrite edit modal did not populate with the correct values ([#8072]).
- The outdated querylog anonymization script.
 
 
