Version 0.107.49 casues error during initalize

[AnonymousX86]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

Docker

Setup

On one machine

AdGuard Home version

0.107.49

Action

Simply start Docker container, go to initialize page and try to fill forms.

Expected result

Proper AdGuard Home initialize.

Actual result

Getting error:

Error: control/install/configure | dnsServer.Prepare: preparing internal proxy: validating private RDNS upstreams: no upstream specified | 500

Additional information and/or screenshots

Installing previous version 0.107.48 resolves the issue.

[gidder]

Probably the same issue, but with already deployed AdGuardHome after update to 0.107.49.
The docker won't start, and I see these lines repeating in the logs:

2024/05/21 19:48:20.212312 [info] AdGuard Home, version v0.107.49
2024/05/21 19:48:20.215945 [info] tls: using default ciphers
2024/05/21 19:48:20.218690 [info] safesearch default: disabled
2024/05/21 19:48:20.225038 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
2024/05/21 19:48:20.225245 [info] auth: initialized.  users:1  sessions:0
2024/05/21 19:48:20.225378 [info] AdGuard Home updates are disabled
2024/05/21 19:48:20.225559 [info] web: initializing
2024/05/21 19:48:20.376319 [error] querylog: closing: flushing log buffer: nothing to write to a file
2024/05/21 19:48:20.376330 [fatal] dnsServer.Prepare: preparing internal proxy: validating private RDNS upstreams: no upstream specified

Downgrading to adguard/adguardhome:v0.107.48 helped

[MRobi1]

Seeing the same issue both from a new install and from an update
Forcing v0.107.48 fixes the issue

[PiuPiuson]

Same here in an existing setup. Downgrading fixed it.

[silentkiller88]

Same here in existing docker setup, doNgrading fixed the issue indeed

[geriguy43]

Just wanted to confirm, I have same issue,
AdGuard won't start after the update (automatic update by whatchtower.)

Synology NAS, Adguard in a Docker container, redirected to an own IP address.

Needed to roll back to the latest stable version which solved the problem.

[nickwilkie]

Me too, just happened to do an update a few minutes ago and my network went down, downgrading fixed. Using adguard in a docker compose on a proxmox vm.

[jerheij]

Same here, the latest version caused the error and prevented it to start. Downgrading to v0.107.48 fixed it.

[middreks]

Managed to get it up and running by setting use_private_ptr_resolvers to false in AdGuardHome.yaml config.
While this is not ideal, for a temp solution it could help.

[solidgonk]

LXC from helper-scripts deployed fine, but Docker deployment failed with this error.

[Tommatheussen]

Managed to get it up and running by setting use_private_ptr_resolvers to false in AdGuardHome.yaml config. While this is not ideal, for a temp solution it could help.

If this helps for the Devs: I never set that flag (from UI) before, now I just toggled it on and back off from the UI (in version 0.107.48) and the latest version correctly boots up now

[Xazziri]

More info:
I have 3 docker instances running of which 2 failed like described. These two show, under the Private reverse DNS servers heading: AdGuard Home could not determine suitable private reverse DNS resolvers for this system. The third (not docker but podman) did not fail and has a different message: By default, AdGuard Home uses the following reverse DNS resolvers: "10.89.2.1:53".
Setting use_private_ptr_resolvers to false in AdGuardHome.yaml config for the 2 that failed did fix the problem, but enabling local resolving on the docker hosts also works.
I would propose to check if AdGuard Home can determine suitable private reverse DNS resolvers for this system. If not, set use_private_ptr_resolvers to false.

[jerheij]

More info: I have 3 docker instances running of which 2 failed like described. These two show, under the Private reverse DNS servers heading: AdGuard Home could not determine suitable private reverse DNS resolvers for this system. The third (not docker but podman) did not fail and has a different message: By default, AdGuard Home uses the following reverse DNS resolvers: "10.89.2.1:53". Setting use_private_ptr_resolvers to false in AdGuardHome.yaml config for the 2 that failed did fix the problem, but enabling local resolving on the docker hosts also works. I would propose to check if AdGuard Home can determine suitable private reverse DNS resolvers for this system. If not, set use_private_ptr_resolvers to false.

I wonder if it wouldn't be better to disable the feature by default unless specifically enabled. Reverse DNS is, as far as I am concerned, a more advanced feature. Especially when talking about a system primarily being used for ad, and other malicious crap, blocking.

[thepod7]

I have set use_private_ptr_resolvers to false on both of my containers and the systems will still not load, they continue to fail with this error:

adguardhome_2 | 2024/05/22 11:26:28.013219 [fatal] dnsServer.Prepare: preparing internal proxy: validating private RDNS upstreams: no upstream specified

My only fix was to downgrade - adguard/adguardhome:v0.107.48

I should add that I am also running unbound along with adguard

[jerheij]

I have set use_private_ptr_resolvers to false on both of my containers and the systems will still not load, they continue to fail with this error:

adguardhome_2 | 2024/05/22 11:26:28.013219 [fatal] dnsServer.Prepare: preparing internal proxy: validating private RDNS upstreams: no upstream specified

My only fix was to downgrade - adguard/adguardhome:v0.107.48

I should add that I am also running unbound along with adguard

Have you stopped the container, updated the values and then started the containers? I read somewhere that if you do it while AGH is still running it might change it again.

[thepod7]

I have stopped the containers, even went as far as restarting the Pi's they are running on - as mentioned the only solution was to force the systems back to v0.107.48

[ainar-g]

Thank you all for the report. We have reproduced the error and working on a fix.

[EugeneOne1]

Hello @AnonymousX86 and everyone else. We've just pushed the edge build (v0.108.0-a.908+a030dd45) that should fix this to the Docker Hub. Could you please give it a try? We'll include this fix into the upcoming release if it fixes the problem.

[Liziloo]

Hello @AnonymousX86 and everyone else. We've just pushed the edge build (v0.108.0-a.908+a030dd45) that should fix this to the Docker Hub. Could you please give it a try? We'll include this fix into the upcoming release if it fixes the problem.

Worked for me! Thank you.

[ItsMelody]

Had this same issue. Gave me this error

dnsServer.Prepare: preparing internal proxy: validating private RDNS upstreams: no upstream specified

Forcing adguard/adguardhome:v0.107.48 seems to have fixed the issue.

[EugeneOne1]

@ItsMelody, could you please try the adguard/adguardhome:edge version? It should fix the issue as well.

[doedelgit]

@ItsMelody, could you please try the adguard/adguardhome:edge version? It should fix the issue as well.

I just tried this and it's working fine for me while it failed before on 0.107.49.

[ItsMelody]

@ItsMelody, could you please try the adguard/adguardhome:edge version? It should fix the issue as well.

Works!

[EugeneOne1]

Thank you all for testing. We're closing this issue for now, the release with the fix is coming soon.

[EugeneOne1]

FYI, v0.107.50 is released now.