I have setup pi-hole on a fresh install of debian 9, and connect my phone to the openvpn server where is pi-hole installed. I have made a traditional install, i mean without docker.
Here is my debug logs [✓] Your debug token is: m1lsavlmx5
I think the problem is:
[code][✗] dnsmasq daemon is inactive[/code[✗] dnsmasq daemon is inactive]
In V4.0, dnsmasq is embedded in pihole-FTL, and dnsmasq no longer runs as a separate process. The debug log will show dnsmasq as either failed or inactive.
pihole-FTL is running on port 53 in place of dnsmasq:
*** [ DIAGNOSING ]: Ports in use
...
*:53 pihole-FTL (IPv4)
*:53 pihole-FTL (IPv6)
Your debug log shows that Pi-Hole is blocking domains:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] staticnode23932.win is 0.0.0.0 via localhost (127.0.0.1)
[✓] staticnode23932.win is 0.0.0.0 via Pi-hole (92.222.72.77)
[✓] doubleclick.com is 216.58.209.238 via a remote, public DNS server (8.8.8.8)
The problem appears to lie in your network/VPN configuration. The requests from the clients are not getting to the Pi_hole. Look at the IP addresses assigned below:
i can't tell you that this is the correct interface. After you setup the VPS, when you install Pi-Hole you will need to select the correct interface for the assigned IP address.
If your VPS is publicly acessible, you do want to put on the VPN prior to installing Pi-Hole, or you'll be making an open DNS resolver. That is not a desired outcome.
To avoid having an open resolver, do not install Pi-Hole on any device that is either (1) not protected behind a firewall or router, or (2) not access controlled by a VPN.
A typical home user installs Pi-Hole on a Pi or other similar SBC that is behind their network router, hidden from the internet by the router.