AdGuard Home (Beta) release

[dalisoft]

Hi @AdguardTeam and contributors.

Can we get somehow schedule for Beta releases? There a bugs, security issues and since 30 September we didn't get updates. Monthly likely not. Would be better to users can understand schedule of beta releases.

[Dv2Corn]

There's no published beta release schedule. The only statement about it is in the README's Test unstable versions section: betas are "usually released every two weeks or more often". Edge builds come from the development branch every day. So betas don't follow a fixed date, and this gap is longer than usual. The last beta, v1.0.0-b.1 (30 Sep), is also the one where the beta channel moved to the new UI and the new version numbers.

What you're missing on b.1 right now:

• The security release v0.107.80 came out on 3 Nov for the stable channel: Go 1.27.3, and Multipath TCP turned off because of CVE-2026-98432. The same change is already on master (go.mod has go 1.27.3 and godebug multipathtcp=0), so the next beta and edge builds will include it.
• The bug fixes merged since b.1 are listed under [Unreleased] in CHANGELOG.md.

If you want to stay on the beta line until the next beta:

1. Turn off MPTCP for b.1 yourself. b.1 is built with Go's default, which listens with MPTCP on Linux. The GODEBUG environment variable overrides that at runtime. I checked with adguard/adguardhome:beta (v1.0.0-b.1): by default ss -Mltn in its network namespace shows an mptcp listener on :3000, and with GODEBUG=multipathtcp=0 only the plain tcp listener is left.

   Docker:

   docker run ... -e GODEBUG=multipathtcp=0 adguard/adguardhome:beta

   systemd (service installed with AdGuardHome -s install):

   sudo systemctl edit AdGuardHome
   # add:
   # [Service]
   # Environment=GODEBUG=multipathtcp=0
   sudo systemctl restart AdGuardHome

   The Go library fixes from 1.27.3 can't be switched on by configuration. For those you need a new build.

2. Or switch to the edge channel. Edge is built from master every day: Docker tag edge, Snap channel edge, or install.sh -c edge as shown in the README. Edge is currently v1.0.0-a.102+3e0cb52b (built 3 Nov, before the Go 1.27.3 commit), so the build after that should include the security update. Keep in mind that edge is less tested than beta.

[smurfsurfing]

Thanks for posting a workaround fix. I've added this to my Docker compose environment:
TZ: America/Chicago
GODEBUG: multipathtcp=0

[Dynamic5912]

There's a new release out now

https://github.com/AdguardTeam/AdGuardHome/releases/tag/v1.0.0-b.2

[smurfsurfing]

Excellent. Just updated. The new release also fixed the logout issue I've reported as well. I'm assuming its safe to remove the Docker compose environment:
TZ: America/Chicago
GODEBUG: multipathtcp=0

[guldhammer72]

How to update from Version v1.0.0-b.1 to Version v1.0.0-b.2
when "recheck" button is not there.
Ny AdGuardHome did not say there was a update

[dalisoft]

I used Docker method and just used compose up command and it’s ready. Or any AI agent do it for you. There many free AI agents

[guldhammer72]

Oh, i am running Raspbian