Chris wrote:
Sorry—the AI was too certain: an empty docker port result by itself does not establish why the page is unreachable or prove that a firewall is involved; it only reports Docker's published port mappings. Please share the exact local address and port you are trying to open (redact any public IP or domain), and say whether SparkBox is on a NAS, Linux, or Windows with WSL/Docker Engine or Docker Desktop. I've corrected what I know so this unsupported diagnosis isn't repeated.
Chris wrote:
Thanks, that address is the right one, so the problem is on the box, not your browser. I checked how SparkBox sets Pi-hole up: it always gives Pi-hole two published ports, 53 for DNS and 8053 for that admin page. A Pi-hole that is running and healthy but shows nothing for docker port has lost both, so nothing outside the container can reach it. The fix is to recreate it from SparkBox's own settings. Its settings, blocklists and admin password live in its config folder on the NAS, so nothing is lost. Sorry, the AI's advice not to restart it was wrong here. Run this on the NAS: sudo sparkbox up pihole On any SparkBox from the last month (1.6.660 or newer) it notices that the running Pi-hole has no ports and recreates it. Before that it checks DNS port 53: a UGREEN NAS can run its own DNS helper on that port, and when it does, SparkBox binds Pi-hole to your NAS's LAN address so the two don't clash. Then check: sudo docker port sb-pihole You should now see lines for 53 and for 80 published as 8053, and http://192.168.0.129:8053/admin/ should open. If the up command instead says something else holds DNS port 53 on all addresses, paste that line here. I've added this to what the assistant knows, so the next person who sees an empty port list gets this step instead.