Pi-Hole Error 429: 'Cannot authenticate with PiHole' due to API seats exceeded since updating to V6

[joepool]

Description

Since updating to PiHole V6, I am frequently not able to log into the web interface with the error 'API seats exceeded'. I have to manually increase the number of seats (docker exec pihole pihole-FTL --config webserver.api.max_sessions 17), clear all API sessions and then back to normal for a couple hours, until the same happens again. I believe homepage is using a new session each time. Is there any way around this?
I have generated a new app password since updating to V6

homepage version

v0.10.9

Installation method

Docker

Configuration

- PiHole:
      icon: pi-hole.svg
      href: http://192.168.0.3:8081/admin
      server: docker
      container: pihole
      widget:
        type: pihole
        url: http://192.168.0.3:8081
        version: 6
        key: xxxxxxx
        fields: ["queries", "blocked"]

Container Logs

No response

Browser Logs

No response

Troubleshooting

Tried generating a new app password, increasing the number of seats, but these are both just temporary fixes.

[shamoon]

Please post logs as requested innthe template with debug enabled.

Have you re-created (not just restarted) the homepage container? We definitely try to reuse the session properly: https://github.com/gethomepage/homepage/blob/7b7c7a5b805f7dcadedb85f93d432bc3f38ed926/src/widgets/pihole/proxy.js#L75C16-L75C17

[joepool]

The only log relating to PiHole even with debug logging enabled is:
homepage | [2025-02-22T20:43:43.222Z] error: <piholeProxyHandler> Failed to login to Pi-Hole API, status: 429

I have also tried to recreate the container using docker compose up -d --force-recreate but still face the same issue

[shamoon]

429 is too many requests. Perhaps there’s something on the PiHole side causing this, but I can’t reproduce it (hasn’t otherwise been reported either) and objectively, homepage isn’t making too many requests

[shamoon]

Please dont post an unrelated error on someone else's discussion, 401 is not 429

[BBT-nZ]

Hello! I'm back here again :) I met with this error too for nearly a day. Drove my head against the wall.

However, before I post the steps and settings - I wanted to check if that was allowed since my environment was Proxmox LXC and not docker per se.

[shamoon]

of course, maybe it will be worth someone asking over at the pi-hole project, Im totally unclear why only some users are hitting this