Pi-Hole setup prevents access to VNC and others services running

I run various services on apache, nginx, VNC and SSH on my Raspberry, and tried to install Pi-hole Core v5.2.2

I was using Raspberry through VNC.

When basic-install.sh setup wizard asked me to set my local IP as static, I expected to continue the setup configuration, but actually it messed existing configuration and disconnected VNC I was using, making me lose the control of Raspberry, all others local and remote services running on Raspberry (SSH included) became unreachable too, and I have been forced to attach my Raspberry to a keyboard and a monitor in order to uninstall Pi-hole and restore functionalities.
In addition uninstallation hasn't removed all dependencies installed during setup, despite I have selected their removal when asked, and "dillo browser" appeared as default browser (it doesn't have even asked me if I appreciated such choice in first place).

I don't know if this setup script was supposed to be used on a device entirely dedicated to be used as Pi-hole dns server with no others stuff running, but this hasn't been a good experience.

Pi-hole has no impact on either ssh or VNC services. They are completely separate ports.

If you changed the IP or interface of the Pi, this would affect those services, particularly if you are addressing the Pi via the IP number.

Pi-hole does ship with its own webserver (lighttpd) as an optional install. If you chose this option this may cause interference with nginx and Apache.

"dillo browser" is not something installed by Pi-hole. That is separate software installed by you, and it looks as if it hasn't been updated in 5 years, per their website.

I have configured Pi-Hole on wlan and exactly after I clicked ok in the setup step where it asked me about static local IP, VNC lost the connection immediately, all services hosted became inaccessible, I haven't changed the IP or interface myself, I was just running the basic setup script where it hasn't appeared something alarming about disruptive changes in network configuration.
The access to those services is routed through a local Raspberry IP assigned to the device configured as static and tunneled through a VPN, not sure in what way the setup procedure of pi-hole has messed the configuration, but certainly it misconfigured something.

(I have never installed dillo browser in my whole life, It appeared after I have executed
apt update
apt upgrade
after pi-hole installation
and uninstallation
for some reason)

The install process writes the IP address you selected to /etc/dhcpcd.conf. Those changes (if you acknowledge and accept the changes) require a restart of the Raspberry Pi or a restart of the networking service. Neither of which are done by the script.

Removing all dependencies would render the device pretty near useless, that's why you're asked to be sure before you remove them. Mashing 'y' to every question would be a really bad thing to do.

Never hear of it actually. And it sounds like this was installed on a Raspberry with a desktop GUI installed? We install on headless devices so there's really no sense on us installing a web browser.

Here is our install script. You can see exactly what it does.

The Raspberry hasn't been restarted, after the described step, happened the mess, the Raspberry was still active and with the next setup step configuration waiting for an answer (that unfortunately I wasn't able to provide anymore using VNC due to the issue described)

those removed should be the dependencies added to the device in addition to those previously installed not all dependencies that pi-hole could use, and the issue appeared during installation not during uninstallation that actually restored connectivity

I never heard of it before today too, it appeared after my pi-hole adventure and pi-hole is the only thing installed today, I use Pi OS 64bit maybe there is some related dependency that triggered it

The issue has been caused by lighttpd that messed with my VPN configuration, installing it without webserver worked

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.