Help with port 53?

I just installed pihole and it was working perfect. I then installed open medial vault and it is coming back with

"FTL failed to start due to failed to create listening socket for port 53: Address already in use"

also error
"There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47"

I've looked up all I can to fix this but I'm very green with linux and systems. I really just copy and paste most commands to set up things on my RBP. I wish I knew more how to config/setup/understand all the behind the scenes stuff but it's more than overwhelming to try and learn :frowning:

Thanks in advance. Sorry for the word/copy-paste soup

wouldn't let me upload my debug log ("Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net [✗] There was an error uploading your debug log.", this is the best I've got:

*** [ DIAGNOSING ]: Ports in use udp: 127.0.0.1:5335 is in use by unbound udp: 0.0.0.0:5353 is in use by avahi-daemon udp: 0.0.0.0:5355 is in use by systemd-resolve

udp: 127.0.0.53:53 is in use by systemd-resolve (Prerequisites - Pi-hole documentation) udp: 127.0.0.1:323 is in use by chronyd udp: 0.0.0.0:57882 is in use by avahi-daemon udp::5353 is in use by avahi-daemon udp::5355 is in use by systemd-resolve udp:*:53066 is in use by avahi-daemon udp: [::11:323 is in use by chronyd tcp: 127.0.0.1:5335 is in use by unbound
[v] tcp:0.0.0.0:80 is in use by lighttpd tcp: 0.0.0.0:88 is in use by nginx tcp: 0.0.0.0:22 is in use by sshd tcp: 0.0.0.0:5355 is in use by systemd-resolve

tcp: 127.0.0.53%10:53 is in use by systemd-resolve (Prerequisites - Pi-hole documentation) tcp: 127.0.0.1:8953 is in use by unbound
[v] tcp: [::1:80 is in use by lighttpd tcp: [::1:22 is in use by sshd tcp: [::1:5355 is in use by systemd-resolve
*** I DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
Failed to resolve 981blebaa370432f812932e1b56a5a66-d7007ce577c1. cdn.forter.com on lo (127.0.0.1)
Failed to resolve 981blebaa370432f8129321b56a5a66-d7007ce577c1. cdn.forter.com on
etho
(10.0.7.32)
[v] doubleclick.com is 142.250.217.174 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
Failed to resolve www.disneyplus-begincode.com on lo (::1)
[v] No IPv6 address available on etho
Failed to resolve doubleclick. com via a remote, public DNS server (2001:4860: 4860: : 8888)
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
DHCP packets received on interface etho: 0
*** [ DIAGNOSING ]: Pi-hole processes
[v] lighttpd daemon is active
pihole-FTL daemon is failed

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

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

Run

pihole -d

and upload the debug log.