Pi-Hole Live-Stats broken after updating AdminLTE about heimdall-apps

[tibbe]

I guess the new config UI needs to have a separate fields for the API token, so that Heimdall can correctly compose the URLs it needs (i.e. the URL field would still be the api.php base URL).

[tibbe]

Finally managed to make it work by using http://pihole:80/admin/api.php. Note that "pihole" is the container name and thus the name on the internal docker network. Port 80 is the internal container port of the docker container, not the port exposed on the host.

[antoniodourado]

I'm having the same issue. Waiting for the update.
Browser console is displaying the following and probably is for the same reason mentioned by @Mask3007 :

Also, how do I update Heimdall to the latest version after it gets fixed? I'm runing it in a container with docker compose.

[wez]

FWIW, I worked around this by having my traefik proxy redirect the broken URL:

middlewares:
    pihole-stats-redirect:
      # Workaround for https://github.com/linuxserver/Heimdall/issues/1083
      redirectRegex:
        regex: "^https://pihole.local/stats/api.php$"
        replacement: "https://pihole.local/admin/api.php?summaryRaw&auth=TOKEN"

and add pihole-stats-redirect to the list of middlewares for my pihole service.

I have the config URL explicitly set to https://pihole.local/stats in heimdall (which in turn implicitly appends /api.php when making the request).

This effectively allows unauthenticated access to just the stats page, via the proxy, which seems reasonable to me.

[rmatte]

I don't think that the config UI needs a separate field for an API token, because different apps could pass in the token with different names / identifiers for it. I just think it would be nice if the config field could accept a URL with the relevant options in a standard format like...

http://172.17.0.4:80/admin/api.php?summary&auth=my_api_token

Where my_api_token is the token provided by pi-hole. That way the config field would be much more flexible. The field doesn't currently seem to allow for that just because of how the Pihole.php is parsing the data from that field.

[rmatte]

I'm also not really sure how this ended up with an enhancement label when the entire stats feature for pi-hole is effectively broken at this point. Just saying.

[keriati]

After triggering an Update of the App List it should be possible now to add Pi-hole with an api key.
Note: probably editing of the old Pi-hole entries will not work as they are now missing an api key from the db.

[Xaositek]

Running Heimdall 2.5.5 within Docker on unRAID and after updating the Application list, I don't see the new API field yet.

[keriati]

I would try to refresh the page, I dunno why, for me it just showed up at some point. Maybe some cache is keeping the old version...

[Xaositek]

I would try to refresh the page, I dunno why, for me it just showed up at some point. Maybe some cache is keeping the old version...

At this point I've tried on my iPad, iPhone, MacBook, and Windows 11 VM. Tried Safari, Chrome, and Firefox. I don't think it's cache or browser at this point. I've also restarted the Docker container twice.

[rmatte]

I would try to refresh the page, I dunno why, for me it just showed up at some point. Maybe some cache is keeping the old version...

At this point I've tried on my iPad, iPhone, MacBook, and Windows 11 VM. Tried Safari, Chrome, and Firefox. I don't think it's cache or browser at this point. I've also restarted the Docker container twice.

For me I had to remove the Pi-hole app from heimdall dashboard and re-create it. Not sure if you've done that or not but just mentioning it. Maybe your app list update didn't complete or something?

[Xaositek]

I would try to refresh the page, I dunno why, for me it just showed up at some point. Maybe some cache is keeping the old version...

At this point I've tried on my iPad, iPhone, MacBook, and Windows 11 VM. Tried Safari, Chrome, and Firefox. I don't think it's cache or browser at this point. I've also restarted the Docker container twice.

For me I had to remove the Pi-hole app from heimdall dashboard and re-create it. Not sure if you've done that or not but just mentioning it. Maybe your app list update didn't complete or something?

At this point I deleted my three links to different Pi-Hole servers I have, removed them from my trash bin, restarted the Docker container again, re-ran the Application list update and still nothing.

[Xaositek]

okay so just destroyed the entire Docker image and rebuilt it - problem is solved now.

[tibbe]

I still can't figure out what URL to use. Since my docker container has the name "pihole" and runs on port 8081 I tried http://pihole:8081/admin/api.php?summaryRaw&auth=<token> and various other combinations of query parameters I could think of. What's the right URL to use?

[rmatte]

I still can't figure out what URL to use. Since my docker container has the name "pihole" and runs on port 8081 I tried http://pihole:8081/admin/api.php?summaryRaw&auth=<token> and various other combinations of query parameters I could think of. What's the right URL to use?

When you're adding Pi-hole to heimdall make sure you have the application type selected as Pi-hole, then you'll have a "Config (Optional)" section at the bottom. Set the URL to http://<pi_hole_ip_address>:<pihole_port>/admin/api.php and put the API key in the "API key" field right next to that. The main URL for actually visiting the Pi-hole page is configured above that Config section under the main URL field and should be set to http://<pi_hole_ip_address>:<pihole_port>/admin/login.php

[tibbe]

I still can't figure out what URL to use. Since my docker container has the name "pihole" and runs on port 8081 I tried http://pihole:8081/admin/api.php?summaryRaw&auth=<token> and various other combinations of query parameters I could think of. What's the right URL to use?

When you're adding Pi-hole to heimdall make sure you have the application type selected as Pi-hole, then you'll have a "Config (Optional)" section at the bottom. Set the URL to http://<pi_hole_ip_address>:<pihole_port>/admin/api.php and put the API key in the "API key" field right next to that. The main URL for actually visiting the Pi-hole page is configured above that Config section under the main URL field and should be set to http://<pi_hole_ip_address>:<pihole_port>/admin/login.php

Is the port 1010 different from the standard http port or do both urls have the same port?

[rmatte]

I still can't figure out what URL to use. Since my docker container has the name "pihole" and runs on port 8081 I tried http://pihole:8081/admin/api.php?summaryRaw&auth=<token> and various other combinations of query parameters I could think of. What's the right URL to use?

When you're adding Pi-hole to heimdall make sure you have the application type selected as Pi-hole, then you'll have a "Config (Optional)" section at the bottom. Set the URL to http://<pi_hole_ip_address>:<pihole_port>/admin/api.php and put the API key in the "API key" field right next to that. The main URL for actually visiting the Pi-hole page is configured above that Config section under the main URL field and should be set to http://<pi_hole_ip_address>:<pihole_port>/admin/login.php

Is the port 1010 different from the standard http port or do both urls have the same port?

It entirely depends on how you set it up. I have mine running on port 1010 for the main http UI so that's what I use.