403 forbiden on admin page

Hey

I'm facing a weirdo issue since today.

cannot acces anymore to web interface but pihole is working 100%.

Here the debug token https://tricorder.pi-hole.net/z5KYsWTh/

What i do encounter is when i try to acces admin with

  • /admin
  • dns/admin
  • pi

I endep everytime on

403 Forbidden


nginx/1.18.0 (Ubuntu)

Currently running on

Status:

[✓] FTL is listening on port 53
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✓] UDP (IPv6)
[✓] TCP (IPv6)

[✓] Pi-hole blocking is enabled

If you guys have any clue

Pi-hole uses lighttpd as its web back-end and also configures it for the Pi-hole webGUI:

If want to use nginx instead, below might supply some hints:

https://docs.pi-hole.net/guides/webserver/nginx/

Keep in mind though that with the v6 release, the lighttpd dependency is dropped and replaced by a web daemon embedded in the pihole-FTL binary/daemon:

dehakkelaar@ph6b:~$ pihole-FTL --config webserver
webserver.domain = pi.hole
webserver.acl =
webserver.port = 80,[::]:80,443s,[::]:443s
webserver.session.timeout = 300
webserver.session.restore = true
webserver.tls.cert = /etc/pihole/tls.pem
webserver.paths.webroot = /var/www/html
webserver.paths.webhome = /admin/
webserver.interface.boxed = true
webserver.interface.theme = default-auto
webserver.api.max_sessions = 16
webserver.api.prettyJSON = false
webserver.api.pwhash =
webserver.api.password = ********
webserver.api.app_pwhash =
webserver.api.app_sudo = false
webserver.api.cli_pw = true
webserver.api.excludeClients = []
webserver.api.excludeDomains = []
webserver.api.maxHistory = 86400
webserver.api.maxClients = 10
webserver.api.client_history_global_max = true
webserver.api.allow_destructive = true
webserver.api.temp.limit = 60.000000
webserver.api.temp.unit = C
dehakkelaar@ph6b:~$ sudo ss -nltup | grep 'Netid\|pihole-FTL'
Netid State  Recv-Q Send-Q Local Address:Port Peer Address:PortProcess
udp   UNCONN 0      0            0.0.0.0:53        0.0.0.0:*    users:(("pihole-FTL",pid=921351,fd=16))
udp   UNCONN 0      0            0.0.0.0:123       0.0.0.0:*    users:(("pihole-FTL",pid=921351,fd=34))
udp   UNCONN 0      0               [::]:53           [::]:*    users:(("pihole-FTL",pid=921351,fd=18))
udp   UNCONN 0      0               [::]:123          [::]:*    users:(("pihole-FTL",pid=921351,fd=35))
tcp   LISTEN 0      200          0.0.0.0:443       0.0.0.0:*    users:(("pihole-FTL",pid=921351,fd=29))
tcp   LISTEN 0      32           0.0.0.0:53        0.0.0.0:*    users:(("pihole-FTL",pid=921351,fd=17))
tcp   LISTEN 0      200          0.0.0.0:80        0.0.0.0:*    users:(("pihole-FTL",pid=921351,fd=27))
tcp   LISTEN 0      200             [::]:443          [::]:*    users:(("pihole-FTL",pid=921351,fd=30))
tcp   LISTEN 0      32              [::]:53           [::]:*    users:(("pihole-FTL",pid=921351,fd=19))
tcp   LISTEN 0      200             [::]:80           [::]:*    users:(("pihole-FTL",pid=921351,fd=28))

No clue if this will help any. I recently shifted a couple Pi4's running ga over to dev. It wasn't until I entered https:///admin in whatever browser I tried that I could get to the admin page. 403s otherwise. After that, I've had no problems getting in.

Your system is using nginx on port 80:

[✗] tcp:[::]:80 is in use by nginx 

As already explained by deHakkelaar, Pi-hole uses lighttpd as webserver.

lighttpd wasn't able to start because port 80 was already in use.

If you want to use Pi-hole with nginx, you will need to configure it to server Pi-hole's web interface pages and execute PHP.

If you want to use lighttpd you have 2 options:

  1. you can disable nginx and restart lighttpd; or
  2. you can change lighttpd port to something else (8080, for example) and access the web interface at http://pi.hole:8080/admin

Does pi-hole was using nginx before ? because i dind't intaleed nginx instead of lighttpd

No, nginx has never been used.
Pi-hole has always shipped with the lighttpd package.

The upcoming Pi-hole v6 will drop that package dependency and ship with an embedded civetweb instead.

If you didn't consciously install nginx yourself, then it likely was pulled as a dependency by some other software that you've installed on your system.