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

Issue with getting information from the api (http://ip-adres/admin/api.php) #2444

Closed
pluim003 opened this issue Dec 2, 2022 · 5 comments
Closed

Comments

@pluim003
Copy link

pluim003 commented Dec 2, 2022

It is an issue with another Docker-container, but looks like the root cause is somewhere in the AdminLTE-environment, but could also be in the main pihole-environment.

Versions

  • Pi-hole: Pi-hole version is development v5.14.2-7-g95e799e (Latest: v5.14.2)
  • AdminLTE: AdminLTE version is devel v5.17-15-gec272dd (Latest: v5.17)
  • FTL: FTL version is development vDev-faf53fb (Latest: v5.19.2)

Platform

  • OS and version: Debian 11 on Raspberry Pi
  • Platform: Raspberry Pi4 64bit

Expected behavior

I run a docker container with pihole-influx. It runs a pythonscript which pushes statistics to my influxdb. Since November 19th errors are thrown in the logfile (or on the screen) and no information is getting througn. Well just found out yesterday-evening, but until November 19th my Grafana-graphs show regular data.

A clear and concise description of what you expected to happen.

Actual behavior / bug

A clear and concise description of what the bug is.

Steps to reproduce

Steps to reproduce the behavior:

  1. Download pihole-influx-image from Dockerhub
  2. Run it against the nightly image
  3. See error

Running it when using the latest image works fine. It used to work on the nightly as well. Had it running for 'ages'. And I don't see recent changes to api.php.

Debug Token

  • URL:

Screenshots

This is when running nightly build of the dockercontainer (well I use a nightly build included with unbound, but that shouldn't make a difference).

afbeelding

When I run the latest build everything is working fine:

afbeelding

Additional context

pihole-influx-image I use can be found on https://hub.docker.com/r/pluim003/pihole-influx

Docker-compose for that one:

services:
  piholeinflux:
    image: pluim003/pihole-influx:test
    container_name: pihole-influx
    restart: unless-stopped
    environment:

      # Replace details with your InfluxDB's hostname and credentials
      PIHOLE_INFLUXDB_HOST: "10.0.0.150"
      PIHOLE_INFLUXDB_PORT: "8086"
      PIHOLE_INFLUXDB_USERNAME: "pihole"
      PIHOLE_INFLUXDB_PASSWORD: "`xxx"
      PIHOLE_INFLUXDB_DATABASE: "pihole"

      # Replace with your Pi-Hole's address including path to API below
      PIHOLE_INSTANCES: "pihole=http://10.0.0.150:8100/admin/api.php"

    # OPTIONAL: Instead of the aobove environment variables,
    #           use a custom copy of the user.toml config file.
    volumes:
      - ./custom/config.toml:/user.toml

```

@rdwebdesign
Copy link
Member

This is not a Pi-hole image.

Please contact the developers of pihole-influx image.

@pluim003
Copy link
Author

pluim003 commented Dec 3, 2022

It's true but it looks like a pihole-issue. Or has something with respect to the api changed? When I enter /api.php it looks the same in both the latest- and nightly-builds
But if it has changed, then it needs work from the developers of pihole-influx, although it hasn't been updated for ages. :-)

@yubiuser
Copy link
Member

yubiuser commented Dec 3, 2022

Is your Pi-hole dashboard password protected? You might be affected by:
https://discourse.pi-hole.net/t/upcoming-changes-authentication-for-more-api-endpoints-required/59315/1

as PR #2411 was merged at 18th Nov into development

@pluim003
Copy link
Author

pluim003 commented Dec 3, 2022

Aha. Thanx. That explains it. I'll dig into this. Should check the discourse site more frequently. Maybe pihole-influx also need modifications. Using a fork as it seems it's not being in development anymore.

@pluim003 pluim003 closed this as completed Dec 3, 2022
@pluim003
Copy link
Author

pluim003 commented Dec 3, 2022

Solution is clear thanx to @yubiuser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants