after upgrade to version 6, ADMIN webpages dont load and I get 'Index of /admin'

Help
1

Interestingly the Web GUI did initially load on Android in Chrome, but not in any other Browser, nor on Windows 11 in Chrome, Edge or Firefox, just showinh 'Index of /admin'

I have tried all the suggestions in the FAQ and Help entries

The Web Admin GUI should load and did when I typed in the url http://192.168.0.252/admin
the WEB GUI should load and did before I updadted to Version 6.
I have uninstalled Lighttpd and removed it
I have stopped abd disabled Apache2
I understand that FTL in version 6 deals with https: requests. But when using https://192.168.0.252/admin or https://192.168.0.252:8443/admin, I get 192.168.0.252 refused to connect ERR_CONNECTION_REFUSED
Using http: simply lists and Index of files in the /admin folder

  • Operating System Raspian GNU/Linux 11 (bullseye) 0 aarch64
  • Raspberry Pi 4 Model B Rev 1.5
  • Docker not installed

Debug Token:

Debug token is: https://tricorder.pi-hole.net/A10mHMs7/

2

The debug log shows previous failures when trying to bind to port 80:

[2025-04-21 12:53:45.949 BST 32081] cannot bind to 80: 98 (Address in use)

But apparently this was fixed in your last attempt and now Pi-hole web server is using the default ports (80 and 443):

[✓] tcp:[::]:443 is in use by pihole-FTL
[✓] tcp:[::]:80 is in use by pihole-FTL

The address http://192.168.0.252/admin (without the s) should work, but you made a mistake in your configuration and port 443 is not marked as "secure", for HTTPS. This port is currently available for HTTP only:

2025-04-21 12:54:30.377 BST [631M] INFO: Web server ports:
2025-04-21 12:54:30.377 BST [631M] INFO:   - 0.0.0.0:80 (HTTP, IPv4, OK)
2025-04-21 12:54:30.377 BST [631M] INFO:   - 0.0.0.0:443 (HTTP, IPv4, OK)
2025-04-21 12:54:30.377 BST [631M] INFO:   - [::]:80 (HTTP, IPv6, OK)
2025-04-21 12:54:30.377 BST [631M] INFO:   - [::]:443 (HTTP, IPv6, OK)

To fix this, change your ports using this command:

sudo pihole-FTL --config webserver.port '80,443s,[::]:80,[::]:443s'

Note:

The first URL is not working because port 443 is not marked as secure (explained above) and the second URL doesn't work because port 8443 is not used in your configuration.

3

I executed the command you suggested and now the result differs but still the site does not display:

https://192.168.0.252/admin. Shows

Image
Image1080×2340 76.3 KB

Latest debug output is:

This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2025-04-22:19:02:37 debug log has been initialized.
[i] System has been running for 1 days, 6 hours, 8 minutes

*** [ DIAGNOSING ]: Core version
[✓] Version: v6.0.6
[i] Remotes: origin GitHub - pi-hole/pi-hole: A black hole for Internet advertisements (fetch)
origin GitHub - pi-hole/pi-hole: A black hole for Internet advertisements (push)
[i] Branch: master
[i] Commit: v6.0.6-0-g0f7803b

*** [ DIAGNOSING ]: Web version
git status failed

*** [ DIAGNOSING ]: FTL version
[✓] Version: v6.1
[i] Branch: master
[i] Commit: a3313229

*** [ DIAGNOSING ]: Operating system
[✓] Distro: Raspbian
[✓] Version: 11
[✓] dig return code: 0
[i] dig response: "Raspbian=11,12 Ubuntu=20,22,23,24 Debian=11,12 Fedora=40,41 CentOS=9,10"
[✓] Distro and version supported

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: FirewallD
[i] Firewalld service inactive

*** [ DIAGNOSING ]: System hardware configuration
[i] lshw -short
H/W path Device Class Description

4

This log above is incomplete.

Please generate a new debug log, upload it and do not paste the log contents.
Just copy and paste the Token generated after the upload.

5

Apologies, should have looked. I copied what I thought was the URl on the SSH teminal of my phone and it copied the output rather than the URl

Please see: https://tricorder.pi-hole.net/VYTAeuH9/

Andrew

6

Hi

Sorry have been away on holiday for 2+ weeks

Pihole Admin is still not working. As requested I have generated an new debug log and uploaded it, reference URL is: https://tricorder.pi-hole.net/5DIIamnJ/

Andrew

7

Your new log shows Pi-hole web server is using ports 80 and 443:

[✓] tcp:0.0.0.0:80 is in use by pihole-FTL
...
[✓] tcp:0.0.0.0:443 is in use by pihole-FTL

[2025-05-07 14:52:56.868 BST 2471] Initializing HTTP server on ports "80,443s,[::]:80,[::]:443s"

Now you should be able to access the web interface using these URLs:

8

Thank you, unfortunately as I previously reported, the links you suggested, which are those I have been trying DO NOT work.

Please see screen grabs attached. This all worked before upgrade to V6. I also tried reinstalling PiHole before the last debug output and still no resolution.

Andrew S Hudson

(attachments)

IMG_2709.jpeg
IMG_2709.jpeg2160×1620 107 KB

IMG_2708.jpeg
IMG_2708.jpeg2160×1620 99.9 KB

9

Hi

OK solved it.

I had to grant execute permission to "others" on the full chain of directories, not just admin, so sudo chmod 755 /var/www and sudo chmod 755 /var/www/html - after that the admin interface works.

It clearly should be resolved in the installation script, because there are a huge number of similar ‘complaints’ on the internet about the same issue.

Andrew Hudson

10

I think the install script won't change permissions outside the directories used by Pi-hole on purpose.

The default permissions works for most users, but in some cases (like yours) the system is using different permissions. We can't force the installer to change this because it will probably break permissions for many users.

1 Like
11

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