Cant turn on DNS over https for AdGuard Home

mkdr · January 12, 2024, 5:04pm

If you go to the Adguard Home webgui of Brume II with fw 4.4.6 under http://192.168.8.1:3000/#encryption and you hit “enable encryption” there comes the error:

If you change the port under:

to something else for example 3001, it still doesnt work. You cant click on the save button on the bottom it is grayed out:

I guess it is not working because you need a valid certificate:

Is there any way to use a certificate which is already used by the router for DDNS?

I think this process should be automated and build into the GLinet firmware, if it is advertised to come with Adguard home.

slesar · January 12, 2024, 6:18pm

443 port is used gl gui. You need change port. Try use my setting and will be work.

mkdr · January 12, 2024, 6:35pm

No, it does not. I already said I tried to change port to 3001. You cant save. And I also mostly suspected why, because it wants a certificate.

These are empty with default GLinet fw:

Is that a bug? What if I use the ones on your screenshot from /etc/nginx ? They seem to exist. But it says it is invalid:

Anyway, that menu isnt needed it seems to use DNS over HTTPS. It seems to be misleading and is just for if you want to run the web interface on https. If you look into “DNS settings”, I changed default 8.8.8.8 9.9.9.9 into:

That seems to work.

slesar · January 12, 2024, 6:45pm

Go go gl gui and find port 443 in security menu.
3001 yes is new port but not public of course, just local area network.

Because it is generated by adguard home server to new config.yaml in adguard home. All default is blank.

It is not bug. If you want real ssl with your Adguard Home then make it public your resolver.

Well done, but first post not talking about that?

admon · January 12, 2024, 6:45pm

Using DNS-over-HTTPs inside your network isn’t usually needed and not many devices support it anyway.

It‘s just for inside the network and not about the upstream DNS.

mkdr · January 12, 2024, 6:49pm

Like I said in my 2nd post. It seems the description is misleading:

That is NOT needed it seems for communication between adguard to dns server (upstream), just for web interface and lan to adguard, which is not used anyway because:

So I guess I can leave it deactivated and just use:

slesar · January 12, 2024, 7:46pm

You won’t see logs from Adguard Home. Looks like your made router dns server with dhcp (inside luci) . Just leave 2nd dns server for someone static devices to connect adguard home server.

mkdr · January 12, 2024, 7:59pm

Not sure what youre talking about. No, I did not, never touched any luci settings. The option “AdGuard Home Handle Client Requests” is disabled by default. seems you (accidentally) activated it on your device in the past. the default is dnsmasq => adguard => upstream.

also what logs? I see logs/statistics with the option disabled.