[pihole] COMMUNICATION_ERROR in Pi-hole binding since RC1 – HTTP protocol violation

[miloit]

Description:

Since updating to RC1, the Pi-hole binding fails to communicate with the Pi-hole server. Attempting any operation triggers a COMMUNICATION_ERROR. The error appears to be related to HTTP authentication handling.

Steps to Reproduce:

Update the openhab to RC1.
Attempt to use any functionality that communicates with the Pi-hole server (e.g., fetching stats or toggling blocking).

Expected Behavior:

The binding should successfully communicate with the Pi-hole server and return the expected data or perform the requested action.

Actual Behavior:

Communication fails with the following error

COMMUNICATION_ERROR
Exception while sending request to Pi-hole. org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header

Additional Information:

This issue did not occur in previous versions before RC1.
The error suggests that the binding is receiving an authentication challenge from the Pi-hole server without the proper WWW-Authenticate header, which violates HTTP protocol expectations.
Pi-hole version:
Binding version: RC1
###Possible Workarounds:
None identified so far.

[lolodomo]

I see no change merged for the binding since the 6th of November.

[lolodomo]

Please mention the pihole version you are running.

[lolodomo]

A new pihole version 6.3 was released 3 weeks ago.
https://github.com/pi-hole/pi-hole/releases

I guess you update to this version and this new version is not "compatible" with the current binding. You can try to downgrade pihole to a previous version.

[miloit]

My version is latest

Core v6.3FTL v6.4.1Web interface v6.4

[miloit]

Workaround is get a new API token than no error

[lsiepel]

fyi @magx2 do you see any possible ways to improve the error message to be more descriptive ?

[magx2]

My version is latest

Core v6.3FTL v6.4.1Web interface v6.4

Are you using serverVersion=6 (it was introduced in #19350 )

[miloit]

@magx2 sorry I am in the hospital

To make it clear the binding/thing runs fine until oh5.1RC1 than there came up this error

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/pi-hole-integration/37841/92

[Wikibear]

I don't have any issues with V6. I installed it two days ago and its working on my side without any issues. I ran in trouble to understand how to generate API key. So you must click on "configure app password" copy that new password and insert it into openhab pihole settings page and click on save. Click in pihole on replace app password and still wait that thing will connect to it.

[magx2]

@miloit is working on updating the documentation about generating API Key for PiHole v6

[Wikibear]

We must say goodbye to the wording API Key. That doesn't exist in V6 any more. The new definition of it is app password. Same with the helping text underneath token box:

[magx2]

OK, but we still have to support v5 (and it's naming)