Cannot access webinterface since update to v6

Help
1

Hey there,

after updating to v6 I cannot access the the webinterface via 192.168.178.23 anymore... :confused:

I have tried several possible solutions from the forum, but ultimately without success...

Everything else seems to be working fine.

What could be the issue?

Debug Token:

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

2

Your debug log shows that Pi-hole's embedded webserver is configured to listen on ports 8080/HTTP and 443/HTTPS:

   [webserver]
     port = "8080o,443os,[::]:8080o,[::]:443" ### CHANGED, default = "80o,443os,[::]:80o,[::]:443os"

You should be able to access Pi-hole's HTTP UI by stating that port, e.g. via http://pi.hole:8080/.

Since your debug log shows no other webserver listening on port 80, you may also move back to that port, e.g.

sudo pihole-FTL --config webserver.port "80o,443os,[::]:80o,[::]:443os"
3

Hej there. Thank you for your quick reply! Unfortunately that's not working...

If I'm using http://pi.hole:8080/ or :80 or "http://192.168.178.xx/admin/index.php" I'll get: ERR_CONNECTION_TIMED_OUT either way.

When using "ping pihole" in Windows PowerShell it pings "pihole.fitz.box, assigned IP" without any loss, max. 1ms.

Update1:

  • I used: "sudo service lighttpd restart"
  • Lighttpd -v says: "lighttpd/1.4.59 (ssl)"

Update2:

  • curl -I localhost/admin says: "HTTP/1.1 403 Forbidden"

Update3:

  • I used "sudo pihole -r" (again, out of desparation)

nothing of the a.m. helps... can't access the web interface :person_shrugging:

4

Lighttpd should not be running if your on V6. See the note from the Fixes and Findings announcement. Also, is this baremetal or docker?

Most users should have been offered a dialog box during the upgrade to choose to disable lighttpd, and most users should have chosen to do so. Unless you are using lighttpd for any other web service, it is no longer needed.
Please run the following to disable it: sudo systemctl stop lighttpd && sudo systemctl disable lighttpd

5

I think I deactivated Lighttpd during the update but apparently activated it again when tried to solving the problem.

I did run your command, but still can't access web ui....
I have even used ' systemctl disable lighttpd" to prevent it from starting automatically at boot.

It runs on a Raspberry Pi 4 Model B Rev 1.5 (Linux 11 (bullseye))

6

What do you get trying just http://{pihole ipaddr}/admin or {pihole ip addr}:80/admin where {pihole ipaddr} = piholes ip without the brackets?

Note that the index.php was part of the old lighttpd and isn't used anymore for access.

1 Like
7

Well.. almost either way :sweat_smile:

  1. http://{pihole ipaddr}/admin/ -> ERR_CONNECTION_REFUSED
  2. {pihole ipaddr}:80/admin/ -> ERR_CONNECTION_REFUSED
  3. {pihole ipaddr}:8080/admin/ -> ERR_CONNECTION_TIMED_OUT

thanks about the index part...!

8

The mod indicated your admin should be accessible on

What do you get when you try below

http://192.168.178.23:8080/admin

https://192.168.178.23/admin

9

As the mod suggested, I moved it back to 80.

http/:/192.168.178.xx:8080/admin -> ERR_CONNECTION_TIMED_OUT
https/:/192.168.178.xx/admin -> ERR_CONNECTION_TIMED_OUT

and:
https://192.168.178.xx:443/admin -> ERR_CONNECTION_TIMED_OUT

10

Not sure if this will help or not but can you clear your browsers cache / cookies?

11

Well, i'll give it a try :smiley:

Update:
didn't help.
Tried Chrome and Mozilla (default)

12

http/:confused: is NOT correct

it's supposed to be http:// NOT http/:confused:

you have the colon in between the /
it's colon and // after

13

That is indeed true... Without the typo the results (unfortunately) stay the same...

Although it also kinda is " :confused: " :wink:

14

I give up.... :grinning:

1 Like
15

If you changed your configuration, please generate a new debug log if the new settings.

1 Like
16

Ok, I did everything again and also generated a new debug log as rdwebdesign suggested (indeed a good suggestion!)

Now I can access the web ui via http://192.168.178.xx/admin/ yay! :smiley:
but I cannot via https://192.168.178.xx/admin/login

I don't fully get it... :person_shrugging:

The new debug token is:

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

17

_TIMED_OUT means no one is answering the call, i.e. there is no webserver listening, or its answers don't make it back to the browser.
This would be expected when connecting to port 8080 while the webserver is listening on port 80.

_REFUSED means that the machine did refuse to accept the request, which often indicates a firewall issue.

This may be expected for port 8080, as that is deviating from standard HTTP port 80.

But right now, you've done so many changes, including reactivating lighttpd, which was perfectly disabled when we started, that I don't know what configuration we deal with.
Please provide a fresh debug token, and please don't rush into blindly changing your configuration again.

1 Like
18

Your firewall doesn't allow HTTPS:

*** [ DIAGNOSING ]: FirewallD
[i] Firewalld service active
[✓]   Allow Service: http
[✓]   Allow Service: dns
[✓]   Allow Service: dhcp
[✓]   Allow Service: dhcpv6
[✓] FTL Custom Zone Detected
[✓]   Local Interface Detected
[✓]   FTL Port 4711/tcp Detected

You'd have to allow HTTPS as well.

In addition, if you would want your webserver to listen on non-standard ports (like 8080), you'd need to allow those in your firewall as well.

1 Like
19

Thank you so much for all your help!!

I haven't fully understood why it has worked before the update but hasn't after although the config seemed to be ok (except the 80/880 part, which was like that before also)...
But anyways: Changing back to default obviously did the trick on the 2nd try! :blush:

Thanks again to all of you! You have been very helpful! :smiley:

1 Like
20

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