AdGuard Home crashing when applying App Version: v0.107.69 / Version: 1.2.18 because port 53 is already in use

Apps and Virtualization
1

I ran into an issue when applying yesterday’s update to the following AdGuard version:

  • App Version: v0.107.69
  • Version: 1.2.18

The steps to resolve this issue is as follows:

  1. Go to Apps in TrueNAS
  2. Go to adguard-home → Application Information → Edit
  3. Go to Network Configuration → Host IPs
  4. Click on Add and select the proper Host IP (in my case, it was 192.168.1.2 and Host Network)
  5. Scroll to the bottom and Click Update.
2

If you’re using Host Networking and Containers both use port 53 (one internally, one externally), so you can disable Host Networking on AdGuard if you need to get around this, or disable Containers / switch the dnsmasq to another port, there’s a link somewhere

3

to move the container port you can use

sudo incus network set incusbr0 raw.dnsmasq="port=5354"
4

I have the same problem; I’m trying to run AdGuard Home (v1.3.13), but can’t use port 53: conflicts with ‘Virt Service’.

I have tried the incus command, above, but this doesn’t appear to change anything which allows AdGuard to install / work.

And, although my router doesn’t allow use of a non-standard port, I did try setting AdGuard to port 54, just to see if the install/update would complete with that (it does). Now, though, the AdGuard ‘Setup Guide’ still refers to port 54 even if I set the port back to 53 and enable ‘Host Network’ (the only other way I can get the install to complete). And I don’t believe I want ‘Host Network’ enabled.

Edit(1): I can now get AdGuard to complete installation with port 53 set, by setting the ‘Host IP’ to the address of my TrueNAS, i.e. “‘192.168.0.2’ IP Address”. Which is odd, because I’ve never been able to get that box to take an actual IP address before, only “‘0.0.0.0’ IP Address”. The Application Info now does report that, amongst the Ports being used, it’s using “tcp://192.168.0.2:53 : 53” (it didn’t do that, before).

However, I still can’t get DNS queries to work, if I put that address in as my router’s DNS server. So, the TrueNAS box on 192.168.0.2 is set to direct DNS queries to the router on 192.168.0.1, which then sends those back to the TrueNAS box on 192.168.0.2:53. Could this be a problem?

And, the ‘Setup Guide’ in AdGuard still refers to port 54, not 53.

Edit(2): I’ve just realised that I probably need to set an upstream DNS server, in AdGuard. If that’s so, then I’m a doofus.

Edit(3): Nope, AdGuard is still not reporting any queries.

TIA

TrueNAS Scale 25.10.4 Goldeye

5

Solved.

The problem wasn’t with the installation setup as a TrueNAS app, rather it was with the WebUI configuration setttings (first page) just after installation.

This time (after uninstalling and reinstalling), I left the WebUI configuration as default; IIRC, I had changed the default interface settings on the previous install.

Edit: mostly solved. Although AdGuard is generally working, TrueNAS app catalog lookup is prevented, and streaming via Lyrion doesn’t work. AdGuard, though, is passing lookups for streaming services via Lyrion / Squeezeboxes.

Any ideas?

TIA.

6

Now fully working, I believe:

I set the AdGuard ‘Host IP’ to “‘0.0.0.0’ IP Address”, and ticked the ‘Host Network’ box. This caused the IP address (192.168.0.3) of the second interface of the HP Gen 8 server to appear in the AdGuard Web UI ‘Setup Guide’ list. Then I set that (…0.3) as the DNS server for the router (on 192.168.0.1).

However, when an update for AdGuard was required, this did not succeed until I temporarily set the router’s DNS address back to something else (i.e. not via AdGuard). As though the AdGuard update needed to use a DNS server during updating, while AdGuard itself was stopped. So, during the AdGuard update, DNS lookups, tracking etc. were occurring with no protection via AdGuard. Comments/corrections on this?