(For your own privacy and security, do not share full, unsanitised debug log output)
This looks like a networking issue, rather than a Pi-hole one.
Your Pi-hole is operational, receiving and processing DNS requests:
*** [ DIAGNOSING ]: contents of /var/log/pihole
[2025-02-01 00:14:33.185 600M] Imported 5557 queries from the long-term database
[2025-02-01 00:14:33.186 600M] -> Total DNS queries: 5557
[2025-02-01 00:14:33.186 600M] -> Cached DNS queries: 52
[2025-02-01 00:14:33.186 600M] -> Forwarded DNS queries: 4979
[2025-02-01 00:14:33.186 600M] -> Blocked DNS queries: 151
[2025-02-01 00:14:33.186 600M] -> Unknown DNS queries: 8
[2025-02-01 00:14:33.186 600M] -> Unique domains: 117
[2025-02-01 00:14:33.186 600M] -> Unique clients: 5
[2025-02-01 00:14:33.186 600M] -> Known forward destinations: 1
But your RPi 3 has no public connectivity:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] carpetcleaning-fortworthtx.com is 0.0.0.0 on lo (127.0.0.1)
[✓] carpetcleaning-fortworthtx.com is 0.0.0.0 on eth0 (192.168.2.213)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
Also, no DHCP server has been discovered on the link that your RPi is connected to:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
DHCP packets received on interface eth0: 0
*** [ DIAGNOSING ]: Pi-hole processes
This is unusual, as the RPi obviously has been configured via DHCP at some time, acquiring IP address, search domain and DNS ser
*** [ DIAGNOSING ]: Network interfaces and addresses
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 192.168.2.213/24 brd 192.168.2.255 scope global dynamic noprefixroute eth0
valid_lft 258989sec preferred_lft 258989sec
*** [ DIAGNOSING ]: contents of /etc
-rw-r--r-- 1 root root 84 Feb 1 00:14 /etc/resolv.conf
search home
nameserver 192.168.2.1
nameserver 8.8.8.8
You should check the cable connection between your router and RPi, maybe try another ethernet port on the router - some routers may set ethernet ports aside for guest network use.
Or they may isolate a device from communicating with others on your network, so check your router for such a feature, and also make sure that your RPi is allowed to access the Internet.