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

Pihole API status incorrect #2056

Closed
jlo88 opened this issue Jan 6, 2022 · 1 comment
Closed

Pihole API status incorrect #2056

jlo88 opened this issue Jan 6, 2022 · 1 comment

Comments

@jlo88
Copy link

jlo88 commented Jan 6, 2022

Versions

  • Pi-hole: v5.8.1
  • AdminLTE: v5.10.1
  • FTL: v5.13

Platform

  • OS and version: Raspbian GNU/Linux 10 (buster)
  • Platform: Raspberry Pi

Expected behavior

Blocking status from http://MY_IP/admin/api.php?status to reflect the blocking status from the web interface and command line pihole status.

Actual behavior / bug

Blocking status is always disabled: {"status":"disabled"}. Rebooting does not solve the issue. The web-interface and pihole status behave as expected.

Steps to reproduce

Steps to reproduce the behavior:

  1. Switch off blocking via curl -X GET 'http://MY_IP/admin/api.php?disable=3600&auth=MY_API'
  2. Switch on blocking via curl -X GET 'http://MY_IP/admin/api.php?enable&auth=MY_API'
  3. Request status via http://MY_IP/admin/api.php?status , shows diabled while the web-interface shows enabled and pihole status shows enabled as well.

Debug Token

Screenshots

N/A

Additional context

This only happens on one of my two piholes which run identical hardware and versions.

@yubiuser yubiuser transferred this issue from pi-hole/pi-hole Jan 6, 2022
@yubiuser
Copy link
Member

yubiuser commented Jan 6, 2022

Thanks for the report. Duplicate of #2051

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

No branches or pull requests

2 participants