AdGuard Home v0.107.69

AdGuard Home v0.107.69 is here — just a quick pit stop to fix two pesky bugs that tried to sneak past us. No new features this time, but everything should now run a bit smoother (and those bugs have been shown the door).

Full changelog

See also the v0.107.69 GitHub milestone.

Changed

• Node.js 24 is now used to build the frontend.

Deprecated

• Node.js 20 and 22 support.

Fixed

• DHCP settings could not be saved (#8075).
• DNS Rewrite edit modal did not populate with the correct values (#8072).

Removed

• The outdated querylog anonymization script.

AdGuard Home v0.108.0-b.78

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

Full changelog

Security

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

Added

• New DNS rewrite settings endpoints GET /control/rewrite/settings and PUT /control/rewrite/settings/update (#1765). See openapi/openapi.yaml for details.

Changed

• Node.js 24 is now used to build the frontend.
• POST /control/rewrite/add and PUT /control/rewrite/update now accept the optional field "enabled" (#1765). See openapi/openapi.yaml for details.

Configuration changes

In this release, the schema version has changed from 30 to 31.

• Added a new boolean field filtering.rewrites_enabled to globally enable/disable DNS rewrites.

• Added a new boolean field enabled for each entry in filtering.rewrites to toggle individual rewrites.

  # BEFORE:
  'filtering':
    'rewrites':
      - 'domain': test.example
        'answer': 192.0.2.0
    # …
  
  # AFTER:
  'filtering':
    'rewrites_enabled': true
    'rewrites':
      - 'domain': test.example
        'answer': 192.0.2.0
        'enabled': true
    # …

  To roll back this change, set schema_version back to 30.

Deprecated

• Node.js 20 and 22 support.

Fixed

• DHCP settings could not be saved (#8075).
• DNS Rewrite edit modal did not populate with the correct values (#8072).

Removed

• The outdated querylog anonymization script.

AdGuard Home v0.107.68

Let's get “the usual” out of the way: we’ve made some security updates, as we always do, and even managed to make do without any bug fixes this time, for better or for worse. But let’s focus on the main course: new option to enable and disable DNS rewrite rules 🚦

This was one of the earlier feature requests, and we are happy to finally deliver. You can enable and disable DNS rewrite rules all at once or do so on an individual rewrite basis — both by editing YAML files or via UI.

Acknowledgments

A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.68 GitHub milestone.

Security

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

Added

• New DNS rewrite settings endpoints GET /control/rewrite/settings and PUT /control/rewrite/settings/update (#1765). See openapi/openapi.yaml for details.
• New fields "groups" and "group_id" added to the HTTP API (GET /control/blocked_services/all). See openapi/openapi.yaml for the full description.

Changed

• POST /control/rewrite/add and PUT /control/rewrite/update now accept the optional field "enabled" (#1765). See openapi/openapi.yaml for details.

Configuration changes

In this release, the schema version has changed from 30 to 31.

• Added a new boolean field filtering.rewrites_enabled to globally enable/disable DNS rewrites.

• Added a new boolean field enabled for each entry in filtering.rewrites to toggle individual rewrites.

  # BEFORE:
  'filtering':
    'rewrites':
      - 'domain': test.example
        'answer': 192.0.2.0
    # …
  
  # AFTER:
  'filtering':
    'rewrites_enabled': true
    'rewrites':
      - 'domain': test.example
        'answer': 192.0.2.0
        'enabled': true
    # …

  To roll back this change, set schema_version back to 30.

AdGuard Home v0.108.0-b.77

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

Full changelog

Security

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

Added

• 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).

Fixed

• Excessive configuration file overwrites when visiting the Web UI and a non-empty language is set.

AdGuard Home v0.107.67

Some would call this update small — we prefer the term compact. A new DNS filter, some bug fixing, some optimization — what more can a man ask for? Short and sweet 🍰

Acknowledgments

A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.67 GitHub milestone.

Added

• 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).

Changed

• Optimized matching of filtering rules.

Fixed

• 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).

AdGuard Home v0.108.0-b.76

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

Full changelog

Added

• Support for configuring the suggested default HTTP port for the installation wizard via the ADGUARD_HOME_DEFAULT_WEB_PORT environment variable (useful for vendors).

Changed

• Optimized matching of filtering rules.

Fixed

• Lowered the severity of log messages for failed deletion of old filter files (#7964).

AdGuard Home v0.107.66

You may have the best software in the world, but if people can't access it, it's as good as useless. This is why in today's update we made it a priority to fix a couple of authentication errors — so that you can always log in and use AdGuard Home to its fullest. Couple it with the usual security updates and a pinch of other changes, and you have v0.107.66 on your hands! 🙌

Acknowledgments

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

Full changelog

See also the v0.107.66 GitHub milestone.

Security

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

Changed

• 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).

Fixed

• 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.

AdGuard Home v0.108.0-b.75

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

Full changelog

Security

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

Changed

• 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).

Fixed

• 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.

AdGuard Home v0.107.65

This release contains an assortment of changes, most of which are related to DNS cache — check out the changelog for details. Of course, we have also improved the security as usual by updating the Go version. 🔐

Acknowledgments

A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.65 GitHub milestone.

Security

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

Added

• 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.

Changed

Configuration changes

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.

  # BEFORE:
  'dns':
      # …
      'cache_size': 123456
  
  # AFTER:
  'dns':
      # …
      'cache_enabled': true
      'cache_size': 123456

  To roll back this change, set the schema_version back to 29.

Fixed

• Disabled state of Top clients action button in web UI (#7923).

AdGuard Home v0.108.0-b.74

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

Full changelog

Added

• 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.

Changed

Configuration changes

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.

  # BEFORE:
  'dns':
      # …
      'cache_size': 123456
  
  # AFTER:
  'dns':
      # …
      'cache_enabled': true
      'cache_size': 123456

  To roll back this change, set the schema_version back to 29.

Fixed

• Disabled state of Top clients action button in web UI (#7923).