I'm out of thoughts at this point on how to get Pi-hole running on that OS.
What is the compelling reason to run that specific OS? If you run straight Buster from RaspberryPi, it is supported and Pi-hole will run with it.
ok thank you jfb. i use this OS to control a 3D printer.
And it already worked with the 3D printer, the Pi-hole and the Pi-VPN all at the same time and in the same raspberry pi. But now I can't
If it worked once, then something must have changed since it was last working. Any OS updates, other software changes, reconfigurations, etc.?
I have a backup that worked .... but when i have upgraded the raspberry pi, it gave me a problem on the touchscreen (blank, without image) and then I had to install everything again ... but I noticed that the pihole did not work
As you can see on the atached foto. It works and is installed on the same system, but gives me other problems, so I wanted to do a clean installation
It still tries to read that file. Please run again ls -lha /etc/dnsmasq.d
Hello yubiuser.
total 24K
drwxr-xr-x 2 root root 4.0K Oct 9 11:50 .
drwxr-xr-x 110 root root 12K Oct 9 11:33 ..
-rw-r--r-- 1 root root 1.4K Oct 9 11:33 01-pihole.conf
-rw-r--r-- 1 root root 211 Feb 5 2019 README
Really strange, because the file does not exist anymore in this directory.
Hopeless last try: move the readme as well
sudo mv /etc/dnsmasq.d/README /etc/pihole/README
pihole-FTL dnsmasq-test
sudo service pihole-FTL start
sudo service pihole-FTL status
1 Like
pihole-FTL dnsmasq-test:
dnsmasq: syntax check OK.
sudo service pihole-FTL status:
pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Fri 2020-10-09 19:59:10 WEST; 3min 39s ago
Docs: man:systemd-sysv-generator(8)
Process: 631 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUC
Oct 09 19:59:09 Repetier-Server systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 09 19:59:09 Repetier-Server pihole-FTL[631]: Not running
Oct 09 19:59:09 Repetier-Server su[686]: (to pihole) root on none
Oct 09 19:59:09 Repetier-Server su[686]: pam_unix(su:session): session opened fo
Oct 09 19:59:10 Repetier-Server pihole-FTL[631]: dnsmasq: cannot read /etc/dnsma
Oct 09 19:59:10 Repetier-Server su[686]: pam_unix(su:session): session closed fo
Oct 09 19:59:10 Repetier-Server systemd[1]: Started LSB: pihole-FTL daemon.
It seems is working 
no?
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Fri 2020-10-09 20:48:57 WEST; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 604 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUC
Oct 09 20:48:56 Repetier-Server systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 09 20:48:56 Repetier-Server pihole-FTL[604]: Not running
Oct 09 20:48:56 Repetier-Server su[656]: (to pihole) root on none
Oct 09 20:48:56 Repetier-Server su[656]: pam_unix(su:session): session opened fo
Oct 09 20:48:57 Repetier-Server pihole-FTL[604]: FTL started!
Oct 09 20:48:57 Repetier-Server su[656]: pam_unix(su:session): session closed fo
Oct 09 20:48:57 Repetier-Server systemd[1]: Started LSB: pihole-FTL daemon.
Deducting from this line and the stats of your screenshot I would guess: yes.
Problem solved?
I'm testing, i found that the pi-hole is not blocking ads when connections are over Ethernet. My laptop is connected by ethernet and pi-hole dont blocks ads. If i change to wifi the ads are blocked by pi-hole. I dont understand why 
Do you know?
Thanks so much for your Help yubiuser and jsb !!
Your debug log has expired, but it is likely that you configured your pihole to only listen on the wlan interface. In the Web interface go to Settings/DNS and select "Listen on all interfaces" to make your pihole listen on eth and wlan
This is referring to clients connected to your router via ethernet? If so, that connection is invisible to Pi-hole. Pi-hole sees only a steady stream of DNS queries arriving on the Pi-hole interface. How they get from the client to Pi-hole is unknown to Pi-hole.
Yes you are right! Thanks a lot yubiuser, You are awesome
I will test if everything works well with the repetier-server, but everything indicates that the problem is solved!!
Just a note:
The technical support of the repetier-server also recommended to:
disable nginx
sudo systemctl disable nginx
sudo service nginx stop
disable the server wifi management to not give it a chance to collide
sudo mv /usr/local/Repetier-Setup/bin/manageWifiAccess /usr/local/Repetier-Setup/bin/manageWifiAccess_off
sudo service RepetierServer restart
One more time thank you very much for your help jfb and yubiuser!
jfb is absolutely right:
Pi-hole is completely oblivious as to how a client is connected to the network.
Changing Pi-hole's interface listening behaviour is not related to the way your client connects to the network, only to Pi-hole's own connectivity.
If changing that behaviour made a difference for you, I suspect it's likely because that Repetier software is trying to turn your RPi into some kind of WiFi Access Point.
In that case, you may still need to sort out dnsmasq configuration conflicts caused by that extra hotspot.conf.
By deleting or moving that file out of the way, you made Pi-hole work again, but now your Repetier software may still count on that configuration and fail in places.
We could try to assist if you would post the content of hotspot.conf, but there's no guarantee we'll succeed. It's third party software from Pi-hole's view point, after all. 
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.