Ad Guard doesnt work on Truenas Scale

TrueNAS General
,
1

Hi everyone

Recently I installed AdGuard on my Trunas scale, and it didn’t work. I found by myself that AdGuard used the port 53, and on my NAS I have Dnsmasq that uses the same port, and I didn’t install Dnsmasq, but apparently it’s necessary for some apps.
I tried to change the Adguard port, but the filters on Adguard are ignored. With the help of chat gpt I found that adguard doesn’t listen on the new port (8053) and the port 53 or it’s blocked by something.
I tried to disable Dnsmasq but I can’t maybe cause of some permissions.
I just want to install AdGuard, so if someone has the same issue, please help me.

Thnak you for your time.

1 Like
2

Which version of truenas are you on? If you’re on 25.04 it may not be dnsmasq but incus blocking the port and there’s a command to change the incus port
See:

3

my truenas is on 25.04.1

4

then it’s incus blcoking port 53. You can change the incus port with this command

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

ok thank you, and last question, is changing the port cause issues with something?

6

No. I’ve changed it in april and didn’t have problems until now.

7

ok thank you for your response

8

I created a LXC Container with ubuntu under TrueNAS and installed Adguard on that machine.
Here is a good giude for settig up Adguard Home:

I still try to get Adguard working on my Android as an Private DNS.
Phone is connected via Tailnet (Headscale) to my TrueNAS.

9

hallo Lars,

this does not help for me. Still the same problem as Aiden.

RenderError: [EINVAL] render.adguard-home.schema: The port is being used by following services: 1) “10.135.110.1:53” used by Virt Service

truenas_admin@truenas22[~]$ sudo incus network show incusbr0
config:
  ipv4.address: 10.135.110.1/24
  ipv4.nat: "true"
  ipv6.address: fd42:faf0:4260:5d8f::1/64
  ipv6.nat: "true"
  raw.dnsmasq: port=5354
description: ""
name: incusbr0
type: bridge
used_by:
- /1.0/profiles/default
managed: true
status: Created
locations:
- none
project: default

it does not work either with or without “port=5354”

Installation of AdGuard and pihole fails

1 Like
10

You’re the second person who says that changing the incus port doesn’t help anymore.
Apparently something changed (but i dont know what ), so you may have to file a bug report, but i don’t know if it should be on github because it’s apps related, or in jira because it’s network related…

11

Ran into this issue also.

render.adguard-home.schema: The port is being used by following services: 1) “10.10.106.1:53” used by Virt Service

And pi-hole has the same issue.

render.pihole.schema: The port is being used by following services: 1) “10.10.106.1:53” used by Virt Service

Version : 25.10.0.1

12

Hello, I have the same issue -
`sudo incus network set incusbr0 raw.dnsmasq=“port=5354”` doesn’t help

13

Same here :frowning:

14

The absolute last thing that comes to my mind why it’s working for me but not some others:
Are you guys using a network bridge in your systems or the nic directly?
In my setup i’m using a bridge so that vm’s & lxc and previously an nspawn-jail could reach the host.

15

i am also using a bridge

1 Like
16

Hi guys, just some loud thinking about that Incus port 53 problem - it can help you eventually.

Generally speaking Incus is a fork of LXD (system container and virtual machine manager) and the Dnsmasq is the DNS forwarder and DHCP server part, that’s allowing Incus to provide DHCP and DNS services for the VMs.

When looking in the documentation detials Incus node is enabled from the truenas storage driver to create a storage pool with remote TrueNAS storage server … etc. but this is completely different story, unrelated to the Dnsmasq.

Creating a network bridge for the LXC containers and moving the host IP onto it should resolve the issue, as LarsR wrote …

PS: Just found that issue resolved with a bridge in “Error Setting Up Instances - [EFAULT] The DNS and DHCP service exited prematurely: exit status 2”

17

Just came here to add that I’m having the same issue with the Ad Guard install. The specific error I’m getting is:

RenderError(err_str) from None base_v2_1_77.error.RenderError: [EINVAL] render.adguard-home.schema: The port is being used by following services: 1) "10.203.233.1:53" used by Virt Service

18

Quick update: The workaround I found for my specific issue was assigning the AdGuard install its own static IP address.

First, I added an additional static IP address to my network interface via System > Network.

Second, when I started the app installation, in the “Host IPs” section I clicked “Add” and selected the additional static IP address I created in the first step, instead of using my host/TrueNAS IP address.

It installed flawlessly. I haven’t gone into AdGuard yet to configure it, but this at least got me past the app install error where port 53 was already being used.

1 Like
20

Did you add a bridge IP or an VLAN ip ?

21

I just followed your instructions and it fixes my install of AdGuard. I was losing hope. Thank you.