Pi Hole running but web interface no longer accessible

Help
1

Expected Behaviour:

I am running Pi Hole on Open Media Vault using Portainer.
This setup is running fine since 2021. Including Updates.

I was always able to access pi hole, use the IOs app etc.

Actual Behaviour:

I had a power outage today, this has never been an issue before.

Now Pi Hole seems to be running but I can no longer access the web interface using https://pihole or the IP.

ERR_CONNECTION_REFUSED

I tried:

  • restart of everything I can think about
  • rebuilding the container
  • updating pihole
  • service lighttpd restart

I can ping the IP of the pi hole and it works fine.

When I run curl -I pi.hole
I get

HTTP/1.1 301 Moved Permanently
Location: /admin/
Date: Sat, 20 Apr 2024 12:58:33 GMT
Server: lighttpd/1.4.59

and curl -I 127.0.0.1
results in

HTTP/1.1 403 Forbidden
Content-Type: text/html
Content-Length: 341
Date: Sat, 20 Apr 2024 13:13:54 GMT
Server: lighttpd/1.4.59

It would be awesome if anybody can point me to a solution.
Thanks!

Debug Token:

I did get Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net

So here is the log without ´Domainlist, Adlists etc to shorten it.

REMOVED

2

One more comment.

Running the live log via command line it looks like devices and apps are using the pi hole as DNS

But all browser traffic from desktop and mobile devices, does not

I am 100% sure that it does work normaly because I have to disable pi hole reguarly for work :slight_smile:

I did not change any configurations and I checked all DNS settings

3

The correct address to access the web interface is: http://pi.hole/admin
or using IP: http://192.168.2.195/admin

Are you able to connect using /admin ?

4

Of course I did. I even have it bookmarked that way.
I tried all combinations I can think off :slight_smile:

Although I can call simply the IP all day everyday and it redirects me to /admin

But I fixed it myself by setting the pi hole to a new macvlan with a different IP.

A new vlan with the same IP did not work.
So I believe it must have been something with the IP and the Router...

Doesn´t matter now.

Thank you for your help and this can be closed :slight_smile: