pihole

Description

1. Reproduce

install pihole app, default settings except web password
2. Expected result
launch pihole
3. Actual result
pihole fails to run
most likely reason port :53 is now taken by incus (dnsmasq)
(potential fix: keep incus dnsmasq away from host IP)
(see also this post in the forum https://forums.truenas.com/t/local-dns-on-fangtooth/34857)

Session ID: 2cb584e5-30ad-4649-1e16-c5ec9d76d9ca

Problem/Justification

None

Impact

None

Linked issues

is duplicated by

NAS-134398

pihole fails to start because port :53 taken (dnsmasq from incus?)

Activity

Show:

Bug Clerk February 25, 2025 at 1:00 PM

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk February 25, 2025 at 1:00 PM

Mixing apps and containers are inherently complex. It’s going to take a bit of configuration for each use-case. When you install the pihole app you can use the host-networking mode and choose the host interface to bind to.

If you don’t choose one, the app could potentially bind to 0.0.0.0 (which means all addresses). This won’t work since incus binds a server on port 53 on the incusbr0 specific interface.

You need to either:

configure the pihole app properly and choose a specific host interface
potentially figure out a command to change the default dns port for incus (be warned, this will cause undefined behavior and we haven’t tested it)

Bonnie Follweiler February 24, 2025 at 1:59 PM

Good Morning .

I have moved this ticket into our queue to review now.
An engineering representative will update with any further questions or details in the near future.

Bug Clerk February 22, 2025 at 7:04 PM

debug-verleihnix-20250222200256.txz - xrnpONYJDT:

TrueNAS Version: 25.04-BETA.1
10 tracebacks (6 unique) found in middlewared.log: socket.gaierror: [Errno -3] Temporary failure in name resolution, aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host update.ixsystems.com:443 ssl:default [Temporary failure in name resolution], pyroute2.netlink.exceptions.NetlinkError: (22, 'Invalid argument'), KeyError: 'temperature', KeyError: 'smart_support', aiohttp.client_exceptions.ClientConnectionResetError: Cannot write to closing transport
20 middlewared jobs have failed
2 cronjobs found
1 warning alerts.
No ECC memory
1 USB disks detected
Root encrypted dataset found: tank-SSD-NVMe, tank-SSD-SATA

-- generated automatically --

Bug Clerk February 22, 2025 at 7:03 PM

Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.

https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153