Pihole is still using old IP adress AND new macvlan address / Nginx forwarding doesnt work

Help Community Help
1

Expected Behaviour:

Raspberry Pi 4 4 GB connected to fritzbox (eth0)
Openmediavault installed on debian

Sorry guys i am new to this. The question might be answered before already but i think i am missing something and can't get it running for 3 days now. So after installing pihole on omv in docker i later installed nginx proxy manager and i could access from my own (sub-)domains the services installed in docker container. I had of course to change the port as nginx uses 443 and 80. I noticed after a while that some ads are not blocked as i didnt use 443 and 80 for pihole anymore. So i read, this could be solved using macvlan. I installed (using portainer UI and later CLI) a macvlan driver (IP= 192.168.178.2, parent interface=eth0) and made the pihole container use this network driver. I expect now to access pihole over the macvlan IP only and when i use the default local static IP of my RASPBERRY Pi, i expect to get the congratulation page of nginx.

Actual Behaviour:

When i access the local ip adress, i still get pihole interface: "Did you mean to go to the admin panel?"
Also when i try to start nginx proxy manager container, it tells me "Can't bind adress: Port 443 already in use" (Turns out pihole is using it.)

Debug Token:

https://tricorder.pi-hole.net/ey3jnrndei

2

Pi-hole doesn't need or use 443.

Going to the IP address or using a custom domain means that the automatic redirection to /admin/ is disabled.

You'll need to use http://custom-domain/admin/ or http://ipaddress/admin/ to get there.

3

Landing on an nginx page when accessing a URL using Pi-hole's IP would require that the container running Pi-hole also contains nginx or that Pi-hole's lighttpd has been configured to redirect HTTP requests to nginx's IP.

Neither of those conditions is fulfilled by using a standard Docker Pi-hole, so unless you manipulated your installation, your current observation seems to match what is expected: Accessing Pi-hole's IP takes you to Pi-hole's UI.

4

I thought 443 is to provide a sinkhole for ads that use ssl?

5

@Bucking_Horn sorry I mean of course when I access the local static ip address of my RASPBERRY PI I expect the nginx welcoming page

6

No, there is no way to do that with SSL/TLS. And really, you should be using the default NULL blocking or NXDOMAIN blocking. The blockpage will be going away because it doesn't work with HTTPS.

7

So are you saying I shouldn't use the port 443 in pihole docker container at all?

8

I'm not saying to use or not use. I'm providing the information for you to make the choice on if you want to use or not use.

1 Like
9

It works !!!! Thank you all for the insights and your valuabe time! For others searching for a solution: I was following DB Tech's Video on how to install this on RP and he used Port 443 but as stated here, Pihole doesn't need Port 443 to operate.

10

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