Unable to access web UI via port 80

harrypnyce · February 25, 2025, 11:43pm

Thanks for posting this great thread. Apparently i should have read forums more closely before blindly triggering the upgrade. I was so excited when i noticed it (V6.0) available on my primary Pihole appliance, which is a little Debian VM.

However, Pihole2 is baremetal on an aging RPi: Raspberry Pi 3 Model B Plus Rev 1.3 which is running Raspbian GNU/Linux 12 (bookworm) armv7l been essentially flawless since it went into service back in ~2018, perhaps earlier. Burned up one micro SD card thus far in its lifetime. Could not be happier overall with the performance and this project in general.

Core version is v6.0.4 (Latest: v6.0.4)
Web version is v6.0.1 (Latest: v6.0.1)
FTL version is v6.0.2 (Latest: v6.0.2)

Seems i'll have some troubleshooting to do. I've been leverage Unbound with Pi-hole (on both devices) for years.

EDIT: Tried to run a repair, finally took a chance and even rebooted the Pihole2 device, sadly no progress. HTTPS actually works to display web (admin) interface! No clue why i'm unable to access via regular HTTP (Port 80), but thrilled for the mostly flawless upgrade process across two devices.

Bucking_Horn · February 26, 2025, 12:06pm

Please share the output of:

sudo pihole-FTL --config webserver.port

Rodrigo_Oliveira · February 26, 2025, 1:30pm

I am facing the same issue, and my server setup is the same as mentioned above. Here is my output from this command:

8080o, 443os, [::]:8080o, [::]:443

Bucking_Horn · February 26, 2025, 1:47pm

@Rodrigo_Oliveira, your Pi-hole's webserver is listening on port 8080:

You should be able to access Pi-hole's UI via http://pi.hole:8080/.

Rodrigo_Oliveira · February 26, 2025, 2:04pm

How I can make the server listen on this port?

Bucking_Horn · February 26, 2025, 2:09pm

It would already listen on port 8080.
If it's not, please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

harrypnyce · February 26, 2025, 5:27pm

Thanks you, for splitting my issue off into its own thread. Seems that is my dilemma, still running on 8080, as opposed to the (expected?) default HTTP, Port 80? I thought during the upgrade process i told it to disable any lighttpd services, but perhaps i messed it up.

Results (x2) of the following command, as instructed:

pihole1 (working as intended) = 80o,443os,[::]:80o,[::]:443os
pihole2 (working on HTTPS only) = 8080o,443os,[::]:8080o,[::]:443

And just in case, here's the full debug:
[✓] Your debug token is: https://tricorder.pi-hole.net/5T9KTUw0/

Bucking_Horn · February 26, 2025, 5:31pm

You should be able to access http://<ip-of-pihole2>:8080/admin.

Is another required webserver running on that pihole2, claiming port 80?

harrypnyce · February 26, 2025, 5:36pm

THANKS YOU, both options below appear to work, i was too dumb to find my way to there.

HTTP = http://192.168.11.8:8080/admin/
HTTPS = https://192.168.11.8/admin/

And no, sir... no other web servers (except lighttpd? which i thought i disabled during upgrade process) running that I am aware of. Just a simple Pi-hole (plus Unbound) appliance with Wireguard slapped on top for remote access.

OS: Raspbian GNU/Linux 12 (bookworm) armv7l
Host: Raspberry Pi 3 Model B Plus Rev 1.3

Bucking_Horn · February 26, 2025, 5:50pm

In case lighttpd is still running, have a read of lighttpd still running after upgrade for steps to disable it.

Once that's done, you should be able to move Pi-hole back to port 80 on your pihole2:

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

harrypnyce · February 26, 2025, 7:25pm

I KISS YOU! Thank you so very much for the hand-holding here. After making some minor modifications to the pihole.toml configuration file, specifically the webserver port (reverted to DEFAULT values) then just for good measure, attempted to stop and disable the service.

Although it did not appear active, even after i rebooted the RPi3B+. I believe this issue is now resolved. Much obliged, kind sir. <3

○ lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; disabled; preset: enabled)
Active: inactive (dead)

One last, unrelated -- i assume this is due to the fact i do not have a proper Let's Encrypt or whatever, security certificate, eh? I tinkered with some other domain settings that i may need to revert.

Type = CERTIFICATE_DOMAIN_MISMATCH
Message = SSL/TLS certificate /etc/pihole/tls.pem does not match domain pihole2.example.com !

harrypnyce · February 27, 2025, 6:18pm

Thanks again for resolving my prior issue. On my pihole1 appliance i'm now encountering a new, unexplained error message while trying to run through the update process. No issues with pihole2, it updated just fine again this morning.

  [✓] Supported OS detected
  [✓] Update local cache of available packages
  [✓] Building dependency package pihole-meta.deb
  [✓] Installing Pi-hole dependency package

  [i] Checking for updates...
  [i] Pi-hole Core:     up to date
error: cannot lock ref 'refs/remotes/origin/footer/null': 'refs/remotes/origin/footer' exists; cannot create 'refs/remotes/origin/footer/null'

  Error: Unable to update local repository. Contact Pi-hole Support.

Attempted to run through the full debug, but wasn't even able to upload the dubugger:

********************************************
[✓] ** FINISHED DEBUGGING! **

   * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.

[?] Would you like to upload the log? [y/N] y
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (22) The requested URL returned error: 400

[✗] There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log

Starfoxfs · February 27, 2025, 8:06pm

I have the same Problem, since i updated from Development Builds V6.0 to Master Branch i have no access to Webinterface

The Webserver Ports are correct.

I access Pihole Webinterface through https://ip/admin

:Edit: Now it works. I used the above the solution form @Bucking_Horn thanks

harrypnyce · February 28, 2025, 4:11pm

Took a few attempts over a couple day period, but finally seems to have uploaded my debug token for my pihole1 appliance, Debian 12 (bookworm) virtual machine: https://tricorder.pi-hole.net/WCF8P86t/

Not sure why updates appear borked. Tried searching elsewhere, but was unable to dig up anything relevant or useful.

rdwebdesign · February 28, 2025, 6:42pm

Your debug log says you are running master branch, but your screenshot suggests you are running a different branch for the Web component: footer/null

Try to fix it running pihole checkout web master, then try to update again.

harrypnyce · February 28, 2025, 11:01pm

THANK YOU, for investigating this for me -- i was hesitant to start blindly making changes. Didn't occur to me to check and compare version information. Much obliged.

Before any updates were attempted (today):

Core version is v6.0.4 (Latest: v6.0.4)
Web version is v6.0.1 (Latest: v6.0.1)
FTL version is v6.0.2 (Latest: v6.0.3)

Sadly, still blocked with same / similar error message.

Please note that changing branches severely alters your Pi-hole subsystems
  Features that work on the master branch, may not on a development branch
  This feature is NOT supported unless a Pi-hole developer explicitly asks!
  Have you read and understood this? [y/N] y

  [i] Fetching branches from https://github.com/pi-hole/web.giterror: cannot lock ref 'refs/remotes/origin/footer/null': 'refs/remotes/origin/footer' exists; cannot create 'refs/remotes/origin/footer/null'
  [✗] Fetching branches from https://github.com/pi-hole/web.git

Finally, i attempted to reboot the system and re-run through the attempted update process, same results. No issues with the pihole2 appliance, that updated flawlessly:

Core v6.0.4
FTL v6.0.3
Web interface v6.0.1

harrypnyce · March 2, 2025, 8:53pm

Appreciate the response. Tried a couple times, unfortunately still appears "stuck" for lack of a better term.

Tried to re-run the repair process one more time (-r flag) just to see if that'd help resolve anything... it seems to have forced the update through, although i still encounter an error anytime I'm attempting the normal sudo pihole -up commands, as shown above. Will continue to leverage this (repair) "workaround" until i muster up the effort to finally rebuild this virtual machine.

harrypnyce · March 3, 2025, 10:37pm

Nothing changed, but as of today, all now appears RESOLVED. Thanks again for a wonderful v6 upgrade and going the extra mile to hold my hand with some unknowns.

[✓] Supported OS detected
  [✓] Update local cache of available packages
  [✓] Building dependency package pihole-meta.deb
  [✓] Installing Pi-hole dependency package

  [i] Checking for updates...
  [i] Pi-hole Core:     up to date
  [i] Web Interface:    up to date
  [i] FTL:              up to date

  [✓] Everything is up to date!

system · March 24, 2025, 10:38pm

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