Pihole Docker in unRAID - Stopped Blocking Ads/Minimal Dashboard

[anon24967819]

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

Expected Behaviour:

Pihole should block most or all adds. When I first set-up Pihole, it blocked pretty much everything.

I moved my unRAID OS flash drive to a new motherboard. Everything works, except Pihole.

Actual Behaviour:

In the new motherboard, Pihole initially showed zero blocking and no log history. I deleted the Docker.img/configs and then reinstalled Pihole from scratch. Now I see 10 queries and 6 blocked queries. I should be seeing hundreds in each of these categories.

Pihole port mappings are setup in the Docker to handle all router DNS traffic via 10.0.1.2, using ports 53 UDP/TCP and 80 TCP. I noticed additional ports being used, though I do not think they should be: 443 and 67.

Debug Token:

5rf95o8knv

[anon24967819]

Update: I decided to double check all my settings via the official Pihole setup guide. One of the first things in that guide is to set a router static dns. It was then I realized that I forgot to change this back to the static local IP pointing to the Pihole Docker. I had previously removed/changed this in my router when the Pihole stopped working as a means to have internet on all my devices on the home network until Pihole got fixed.

So, now Pihole appears to be seeing/blocking traffic.

But, I'm still seeing two additional ports being used that I did not set in the Pihole Docker container.

Here are the mapped ports.

Here are the total allocations.

Why are ports 443 and 67 showing up in the allocations?

[jfb]

Take a look in your debug log, about a third of the way down from the top, for the listing of ports in use. This matches a port to a process. In my install on a Pi, for example, I show the following ports in use.

*** [ DIAGNOSING ]: Ports in use
[] is in use by 
[] is in use by 
[22] is in use by sshd
[53] is in use by dnsmasq
[548] is in use by afpd
[5900] is in use by vncserver
[80] is in use by lighttpd
[4711] is in use by pihole-FTL
[5353] is in use by unbound
[8953] is in use by unbound

[deHakkelaar]

These are all the ports that Pi-hole is using (67 UDP for DHCP service):

pi@noads:~ $ sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:4711          0.0.0.0:*               LISTEN      472/pihole-FTL
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      763/lighttpd
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      647/dnsmasq
tcp6       0      0 :::80                   :::*                    LISTEN      763/lighttpd
tcp6       0      0 :::53                   :::*                    LISTEN      647/dnsmasq
udp        0      0 0.0.0.0:53              0.0.0.0:*                           647/dnsmasq
udp        0      0 0.0.0.0:67              0.0.0.0:*                           647/dnsmasq
udp6       0      0 :::53                   :::*                                647/dnsmasq

To see all listening daemons run "sudo netstat -nltup" without the grep.

[anon24967819]

My results are these from the initial log above:

*** [ DIAGNOSING ]: Ports in use
[53] is in use by dnsmasq
[4711] is in use by pihole-FTL

I reran the debug (debug token: xao8z1hxzj ) and get these:

*** [ DIAGNOSING ]: Ports in use
[53] is in use by dnsmasq
[4711] is in use by pihole-FTL

[anon24967819]

[deHakkelaar]

sudo ss -lnp | grep 'Netid\|:53 \|:67 \|:80 \|:471'

?

[anon24967819]

[deHakkelaar]

curl -I http://localhost

?

[anon24967819]

[deHakkelaar]

Looks all good

[anon24967819]

Thanks for taking the time to give me the confirmation.