The issue I am facing:
I'm seeing this error on my Pi-Hole instalation.
journalctl --since "24h ago" | grep -i error
May 03 20:28:20 raspberrypi unbound[2350]: [1683163700] unbound[2350:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:20 raspberrypi unbound[2350]: [1683163700] unbound[2350:0] fatal error: could not open ports
May 03 20:28:23 raspberrypi unbound[2497]: [1683163703] unbound[2497:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:23 raspberrypi unbound[2497]: [1683163703] unbound[2497:0] fatal error: could not open ports
May 03 20:28:24 raspberrypi unbound[2641]: [1683163704] unbound[2641:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:24 raspberrypi unbound[2641]: [1683163704] unbound[2641:0] fatal error: could not open ports
May 03 20:28:26 raspberrypi unbound[2759]: [1683163706] unbound[2759:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:26 raspberrypi unbound[2759]: [1683163706] unbound[2759:0] fatal error: could not open ports
May 03 20:28:27 raspberrypi unbound[2878]: [1683163707] unbound[2878:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:27 raspberrypi unbound[2878]: [1683163707] unbound[2878:0] fatal error: could not open ports
May 03 20:28:28 raspberrypi unbound[2992]: [1683163708] unbound[2992:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:28 raspberrypi unbound[2992]: [1683163708] unbound[2992:0] fatal error: could not open ports
The error above shows Unbound is trying to use port 53, but this port is already in use.
I don't know how to help, because there is no more information.
You could try to generate and upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
If you are unable to upload the debug log, you can temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.
(Click to see more details)
sudo nano /etc/resolv.conf
Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit.
Your debug log shows Pi-hole is using port 53 and Unbound is using port 5335
*** [ DIAGNOSING ]: Ports in use
[✓] udp:0.0.0.0:53 is in use by pihole-FTL
udp:127.0.0.1:5335 is in use by unbound
[✓] udp:*:53 is in use by pihole-FTL
[✓] tcp:0.0.0.0:53 is in use by pihole-FTL
tcp:127.0.0.1:5335 is in use by unbound
[✓] tcp:[::]:53 is in use by pihole-FTL
Now we need to understand how you configured Unbound.
What is the complete output of the following command from the Pi terminal:
Hi, this is the log from 7 days ago, from May-3 the day I installed the Pi-hole
pi@raspberrypi:~ $ journalctl --since "7 days ago" | grep -i error
May 03 20:28:20 raspberrypi unbound[2350]: [1683163700] unbound[2350:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:20 raspberrypi unbound[2350]: [1683163700] unbound[2350:0] fatal error: could not open ports
May 03 20:28:23 raspberrypi unbound[2497]: [1683163703] unbound[2497:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:23 raspberrypi unbound[2497]: [1683163703] unbound[2497:0] fatal error: could not open ports
May 03 20:28:24 raspberrypi unbound[2641]: [1683163704] unbound[2641:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:24 raspberrypi unbound[2641]: [1683163704] unbound[2641:0] fatal error: could not open ports
May 03 20:28:26 raspberrypi unbound[2759]: [1683163706] unbound[2759:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:26 raspberrypi unbound[2759]: [1683163706] unbound[2759:0] fatal error: could not open ports
May 03 20:28:27 raspberrypi unbound[2878]: [1683163707] unbound[2878:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:27 raspberrypi unbound[2878]: [1683163707] unbound[2878:0] fatal error: could not open ports
May 03 20:28:28 raspberrypi unbound[2992]: [1683163708] unbound[2992:0] error: can't bind socket: Address already in use for ::1 port 53
May 03 20:28:28 raspberrypi unbound[2992]: [1683163708] unbound[2992:0] fatal error: could not open ports
May 03 21:17:04 raspberrypi kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43436s-sdio.clm_blob failed with error -2
May 04 18:00:01 raspberrypi logrotate[3541]: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition...
May 04 18:17:04 raspberrypi kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43436s-sdio.clm_blob failed with error -2
May 05 10:40:23 raspberrypi sshd[13117]: error: maximum authentication attempts exceeded for invalid user sergio from 192.168.3.103 port 29366 ssh2 [preauth]
Presuming those unbound error messages were logged when you first installed unbound after Pi-hole, then they would be expected.
In that case, you can safely ignore those messages.
By default, unbound would try to bind port 53 upon installation - but that port is required and already claimed by Pi-hole.
As you seem to have followed Pi-hole's unbound guide, you've then successfuly created /etc/unbound/unbound.conf.d/pi-hole.conf and reconfigured it to use port 5335 instead.
