The network parameters one can edit for the App in the GUI appear quite incomplete, I cannot get the thing to play nice with the bridge interface on my NAS. The web page the Pihole should render on won’t render because of a SSL incompatibility.
The version control # moreover is not helpful either since it gives no clue as to which version of Pihole it’s pointing to. Am I just going full dotard or is there a guide how to deal with the latest SCALE Pihole app?
I’m to the point where using jailmaker will likely be quicker than trying to figure out the docker container. That seems at odds with using docker.
Hey thank you for the response. The issue is that the App button that takes me to the alleged web interface on port 20720/admin/, results in the following error message:
This site can’t provide a secure connection
“SERVER FQDN” sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
The SSL cert works just fine for the 443 HTTPS service and comes via CloudFlare and ZeroSSL / ACME.SH. So I cannot connect to the pi-hole GUI, assuming it’s running.
I may run it in a jail so I can assign a custom IP to it, control it better. It likely will take me less time to set up than the Docker version because there are plenty of good guides out there for pi-hole on various flavors of Linux. Plus I have experience from setting it up on two different Pi’s.
Lastly, the App author is on version 2.014 for the App on his Github but iXsystems App is still pointing to 1.x, presumably because 1.x is stable and 2.014 is not?
That said, I just retried to reach the GUI via the link in the App menu and now it works, of course.
EDIT: The issue is that the App isn’t handling the SSL cert happily (for whatever reason). As long as I try to get there via HTTP, all is well. This likely will push me to use jailmaker after all - to be able to assign a separate IP address via DHCP, install a SSL cert to the FQDN of the pihole, and so on.
