Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pi-hole v6 statistics do not appear. #1431

Open
MRSOFT69 opened this issue Feb 19, 2025 · 5 comments
Open

Pi-hole v6 statistics do not appear. #1431

MRSOFT69 opened this issue Feb 19, 2025 · 5 comments

Comments

@MRSOFT69
Copy link

Good afternoon,
I have noticed that with the new version of Pi-hole (v6), I can no longer see the blocking statistics on the Heimdall dashboard. I imagine the Pi-hole API has changed. Is there any way to get it back?

thx!

@Unklebens
Copy link

Hello, i noticed the same absence of stats in the Pi-hole tile. I regenerated another API token but i still get Error 400 when testing from heimdall

@Trashwarez
Copy link

Same here

@kroese
Copy link

kroese commented Feb 22, 2025

In any case you need the new Enhanced App that supports v6 (which is only available in the Heimdall development branch) linuxserver/Heimdall-Apps#779

Then you need to supply an App Password (instead of a API key like with v5).

But even with all that in place, I still get Server Error when clicking 'Test`. It seems the URL doesnt even matter, as I always get that same error no matter the value for URL.

@PedroBuffin do you have any idea why it does not work?

@Unklebens
Copy link

from what i read in pihole doc, you now need to generate a session token with an app password and the query pihole API with that session token, im gonna try to make the request suing powershell to try them and give results subsequently

@kroese
Copy link

kroese commented Feb 23, 2025

Okay the problem was that the password was incorrect. But this was very troublesome to discover, because the error message was too generic. I improved the Pihole app to fix that: linuxserver/Heimdall-Apps#816

So now it works correctly with v6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Non-Docker Issues
Development

No branches or pull requests

4 participants