Pi-Hole v6 To Many Request - Add/Increase cache time.

[Krojack]

Description

I was making changes to my dashboard and doing several reloads when I started getting the following messages:

glance | 2025/06/22 14:33:40 ERROR Failed to fetch Pihole v6 session ID error="authentication request returned status 429 Too Many Requests with message ''"

Maybe add a cache option for the config. Could default to something like 15 minutes.

[ralphocdol]

cache exists on most widget including DNS. Either way, cache itself doesn't help when reloading glance.yml as the cache time will reset, especially when the widget's API source has rate limiting like this. Your best bet is to comment out the widget first until your done modifying your config.

[ralphocdol]

For a bit of clarity and for others who stumbles upon this issue.

After PiHole got updated to v6, they implemented a rate limiting and there's no way around it as of v6.1.2

The Pi-hole API implements a rate-limiting mechanism to prevent abuse.

Source: https://docs.pi-hole.net/api/auth/#rate-limiting

At the moment, Glance doesn't store the last sessionID it generates after each Glance Restart (whether it be YML config update or a Glance restart) as it does not have one to begin with, and each restart triggers a new POST /api/auth to PiHole which could then stack up hitting the rate limit hence the suggestion to comment out DNS widget until you're done with editing the config.

The cache property does NOT cache anything after Glance Restart, the cache timer only starts after the fact.