Well that worked like a charm! So I was wondering if there was something wrong with IPv6 based on the output of the diagnostic run, specifically the 2 sections:
1st -
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.107/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
2605:6000:1000:452:7047:5f5d:183c:cf4 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)
fe80::404f:bc8f:6793:38f does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
And the second section shows again IPv4 works but IPv6 has some issue
2nd -
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] crystalxxxmovies.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] crystalxxxmovies.com is 0.0.0.0 via Pi-hole (192.168.1.107)
[✓] doubleclick.com is 216.58.194.46 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
[✓] www.cam4.fr is :: via localhost (::1)
[✗] Failed to resolve www.cam4.fr via Pi-hole (2605:6000:1000:452:b02a:25c1:ef1d:26d0)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
So not sure what's wrong with my IPv6 resolving but I think that's the root of it all.