Danny Knaggs (2E0DPK/M6DPK)

I can confirm that I tried this one hour after this issue was posted and I'm getting the same. But I also get a much longer exception which also mentions...

> @knaggsy2000, hello. Can you reach the AdGuard Home instance using `dig`? If you enable the [verbose logging](https://github.com/AdguardTeam/AdGuardHome/wiki/FAQ#verboselog), do you see any queries reaching it? > > > So the...

> Can you test with version b49? Does the previous older version work? > > You can download this manually... `https://github.com/AdguardTeam/AdGuardHome/releases/download/v0.108.0-b.49/AdGuardHome_freebsd_arm64.tar.gz ` What's different with this version compared to the...

@vincejv @gspannu The issue was still present with v0.107.41 for me and continues with .42 too - just re-tested things. @gspannu Let me re-test with that version...

@gspannu v0.108.0-b.49 still appears not to work for clients (";; connection timed out; no servers could be reached") v0.108.0-b.51 is the same too.

@vincejv Noticed in that issue you gave me mentioned about editing the YAML file by setting the bind addresses to individual IPs (for every interface) rather than just "0.0.0.0". Just...

@vincejv Yep, it's a "bind" issue in the YAML. It completely works perfectly in v0.107.42 as long as you stop the service, edit the YAML to remove "0.0.0.0" and then...

@ainar-g I see that you're a contributor to this repo, the issue has been found - it's that the "bind" address (in the YAML) if "0.0.0.0" doesn't actually seem to...

@ainar-g I've installed v0.107.43 on my backup PI (PI3 on FreeBSD 14) and used the same config as my main PI but in the "bind" section of the YAML only...

> @knaggsy2000, it's really weird, because the fix was for all Unix(-ish) systems. Have you been able to collect the verbose logs [as mentioned here](https://github.com/AdguardTeam/AdGuardHome/issues/6500#issuecomment-1847194647)? @ainar-g I've enabled verbose logs...