Pi hole not blocking ads on PC, works on mobile

[mati1414]

Please follow the below template, it will help us to help you!

Expected Behaviour:

Blocking ads on mobile and desktop

Actual Behaviour:

Pi hole is blocking ads only via mobile iOS device. Doesn't work from desktop Manjaro

Debug Token:

https://tricorder.pi-hole.net/anmcpi4ac8

[jfb]

You have configuration problems with your Pi-hole install.

Your debug log shows multiple IPs assigned to the Pi-hole host (one of which appears to be a public IP), and Pi-hole is configured for neither. The Pi-hole host cannot reach the gateway you have assigned.

You are running Centos 8, which is not officially supported. See this thread:

Admin Console shows loading symbols and does not work properly

Expected Behaviour: The Admin Console should show anything else than loading symbols and blacklisting etc. should work. Actual Behaviour: The Admin Console shows only loading symbols on the dashboard and no numbers in the fields at the top. When trying to blacklist (or whitelist) a domain, it says "Failure! Something went wrong, see output below:" but shows no output. When clicking on "Network" a popup message "An unknown error occured while loading the data." occurs. Same applies for "Query Lo…

[mati1414]

Yes, I'm running CentOS 8 but I didn't install Admin Console because I don't want to use it.

Pi-hole host is a VPS server, gateway was a public IP - I was following instruction and checked it twice. How it should be set?

EDIT:

I reconfigured Pi hole - now it has one internal address 192.168.5.1 but it still doesn't work.
It says:

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the wg0 interface:
192.168.5.1/24 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

[✗] No IPv6 address(es) found on the wg0 interface.

[i] Default IPv4 gateway: 51.38.124.1

• Pinging 51.38.124.1...
  ping: sendmsg: Required key not available
  [✗] Gateway did not respond.

And
[root@vps817653 ~]# cat /etc/pihole/setupVars.conf
BLOCKING_ENABLED=true
PIHOLE_INTERFACE=wg0
IPV4_ADDRESS=0.0.0.0
IPV6_ADDRESS=
PIHOLE_DNS_1=1.1.1.1
PIHOLE_DNS_2=1.0.0.1
QUERY_LOGGING=true
INSTALL_WEB_SERVER=false
INSTALL_WEB_INTERFACE=false
LIGHTTPD_ENABLED=false

It says that gateway is not reachable while:
root@vps817653 ~]# ping 51.38.124.1
PING 51.38.124.1 (51.38.124.1) 56(84) bytes of data.
64 bytes from 51.38.124.1: icmp_seq=1 ttl=64 time=0.164 ms
64 bytes from 51.38.124.1: icmp_seq=2 ttl=64 time=0.414 ms
64 bytes from 51.38.124.1: icmp_seq=3 ttl=64 time=0.241 ms
64 bytes from 51.38.124.1: icmp_seq=4 ttl=64 time=0.210 ms
64 bytes from 51.38.124.1: icmp_seq=5 ttl=64 time=0.261 ms
64 bytes from 51.38.124.1: icmp_seq=6 ttl=64 time=0.217 ms
64 bytes from 51.38.124.1: icmp_seq=7 ttl=64 time=0.231 ms

What's wrong?

[jfb]

@mati1414

I reconfigured Pi hole - now it has one internal address 192.168.5.1 but it still doesn’t work.

cat /etc/pihole/setupVars.conf
BLOCKING_ENABLED=true
PIHOLE_INTERFACE=wg0
IPV4_ADDRESS=0.0.0.0

How did the 0.0.0.0 address get assigned for Pi-hole use? That's not a valid IP.

Sort out the Pi-hole host on the VPS, then you can assign the appropriate interface and IP to Pi-hole.

[mati1414]

I have no idea how it got assigned 0.0.0.0.

I reconfigured interfaces and now have one 192.168.5.1 assigned to wg0 and public IP to eth0.

Can I just manually change 0.0.0.0 to 192.168.5.1?

[yubiuser]

I would run pihole -r and change it there.