Lost access to web interface after upgrading to Beta 6.0

I had v5 and decided to participate testing on Beta 6.0. Used the following commands to update

echo "development-v6" | sudo tee /etc/pihole/ftlbranch 
pihole checkout core development-v6
pihole checkout web development-v6

after the updated i manually removed lighttpd(sudo apt-get remove lighttpd and tried to access web admin after that. Now it is unreachable.

With https://pihole IP:8080 it gives me the error on chrome
image

Error code: SSL_ERROR_RX_RECORD_TOO_LONG on firefox

debug log here
https://tricorder.pi-hole.net/EYlDDk9A/

pihole -t seems to be okay still.. even after rebooting the platform.

Does it work properly with the following URL?

http://pihole IP:8080

Note this is with http, not https.

It does not. I have a unifi controller running on this platform as well. It might have that port taken already and the new web server failed to get setup.

when i tried http://pihole IP:8080, it was redirected to the unifi controller.

It appears that port 8080 is occupied by java, not pihole-FTL. From your debug log:

*** [ DIAGNOSING ]: Ports in use
    udp:127.0.0.1:5335 is in use by unbound
    udp:0.0.0.0:5353 is in use by avahi-daemon
    udp:0.0.0.0:44278 is in use by avahi-daemon
[✓] udp:0.0.0.0:53 is in use by pihole-FTL
    udp:0.0.0.0:68 is in use by dhcpcd
    udp:0.0.0.0:514 is in use by rsyslogd
    udp:0.0.0.0:514 is in use by rsyslogd
    udp:0.0.0.0:51822 is in use by <unknown>
    udp:0.0.0.0:631 is in use by cups-browsed
    udp:0.0.0.0:41641 is in use by tailscaled
    udp:*:5353 is in use by avahi-daemon
    udp:*:3478 is in use by java
    udp:[::ffff:100.91.4.141]:44558 is in use by java
    udp:[::ffff:10.6.0.1]:46673 is in use by java
    udp:*:10001 is in use by java
[✓] udp:*:53 is in use by pihole-FTL
    udp:[::ffff:192.168.1.41]:53605 is in use by java
    udp:*:514 is in use by rsyslogd
    udp:*:514 is in use by rsyslogd
    udp:*:51822 is in use by <unknown>
    udp:*:41641 is in use by tailscaled
    udp:*:37989 is in use by avahi-daemon
    tcp:127.0.0.1:8953 is in use by unbound
    tcp:127.0.0.1:631 is in use by cupsd
    tcp:127.0.0.1:27117 is in use by mongod
    tcp:100.91.4.141:41690 is in use by tailscaled
    tcp:0.0.0.0:514 is in use by rsyslogd
[✓] tcp:0.0.0.0:53 is in use by pihole-FTL
    tcp:127.0.0.1:5335 is in use by unbound
    tcp:0.0.0.0:22 is in use by sshd
    tcp:[fd7a:115c:a1e0:ab12:4843:cd96:625b:48d]:41690 is in use by tailscaled
    tcp:*:8080 is in use by java
    tcp:[::1]:631 is in use by cupsd
    tcp:[::]:514 is in use by rsyslogd
    tcp:*:8880 is in use by java
    tcp:*:8843 is in use by java
    tcp:*:6789 is in use by java
[✓] tcp:[::]:53 is in use by pihole-FTL
    tcp:[::]:22 is in use by sshd
    tcp:*:8443 is in use by java

Here is how it looks on my dev 6.0 that is working normally:

*** [ DIAGNOSING ]: Ports in use
    udp:127.0.0.1:5335 is in use by unbound
    udp:0.0.0.0:5353 is in use by avahi-daemon
    udp:0.0.0.0:36853 is in use by avahi-daemon
[✓] udp:0.0.0.0:53 is in use by pihole-FTL
    udp:0.0.0.0:68 is in use by dhcpcd
    udp:*:5353 is in use by avahi-daemon
[✓] udp:*:53 is in use by pihole-FTL
    udp:*:37277 is in use by avahi-daemon
    tcp:0.0.0.0:8080 is in use by pihole-FTL
    tcp:127.0.0.1:8953 is in use by unbound
    tcp:127.0.0.1:5335 is in use by unbound
    tcp:0.0.0.0:443 is in use by pihole-FTL
    tcp:0.0.0.0:22 is in use by sshd
[✓] tcp:0.0.0.0:53 is in use by pihole-FTL
    tcp:[::]:8080 is in use by pihole-FTL
    tcp:[::]:443 is in use by pihole-FTL
    tcp:[::]:22 is in use by sshd
[✓] tcp:[::]:53 is in use by pihole-FTL
1 Like

that must be it, the unifi controller already had the port taken. il try to reconfigure it to port 80..

thank you @jfb

aaand. im back in business, updated /etc/pihole/pihole.toml file and set the ports back from 8080 to 80

port = "80,[::]:80,443s,[::]:443s"

then ran pihole -r(reconfigure)

this might help those who have a similar setup. unifi controller and pi-hole on the same platform.

1 Like

This should not be necessary anymore. A simple pihole restartdns (to restart FTL) should be enough,

1 Like

Thinking about it, this is probably true for a lot of situations in V6.