Login problems #72

user150aa346 · 2025-03-27T00:30:29Z

I'm getting hung up on the password which I know is correct. It's what I use to login as root.

Any assistance would be appreciated. Thanks.

bastgau · 2025-03-27T01:27:44Z

Can you provide us stack logs ?

Do you use MFA ?

Wendigogo · 2025-03-27T16:37:23Z

I got the same issue (on http server without MFA).

Here is my related log:

Cette erreur provient d'une intégration personnalisée

Enregistreur: custom_components.pi_hole_v6.config_flow
Source: custom_components/pi_hole_v6/config_flow.py:126
intégration: pi_hole_v6 (documentation, problèmes)
S'est produit pour la première fois: 17:20:00 (31 occurrences)
Dernier enregistrement: 17:34:12

Connection failed: No session identity provided for endpoint requiring authorization.

Hope this help!

bastgau · 2025-03-27T19:06:47Z

Hey @Wendigogo

What integration version is installed ?

After 31 attempts, I think you've reached the maximum number of connections allowed by Pi-hole. You should purge the sessions from the Pi-hole interface and/or try again later with the correct password.

montgomery102 · 2025-03-27T19:08:13Z

I'm seeing the same issue on integration version 1.9

bastgau · 2025-03-27T19:18:59Z

Need more information. Please active the debug log and provide the log stack related the integration.

montgomery102 · 2025-03-27T19:37:55Z

This error originated from a custom integration.

Logger: custom_components.pi_hole_v6.config_flow
Source: custom_components/pi_hole_v6/config_flow.py:126
integration: Pi-hole V6 Integration (documentation, issues)
First occurred: 3:36:13 PM (1 occurrences)
Last logged: 3:36:13 PM

Connection failed: No session identity provided for endpoint requiring authorization.

This is what I get... If there is a way to get more detailed logs for you I'm happy to, just not sure how to do it. I do have the debug: true line in my config.yaml for HA.

bastgau · 2025-03-27T20:06:45Z

Did you restart your HA after modifying the log level ?

montgomery102 · 2025-03-27T20:57:10Z

Yes I did restart.

bastgau · 2025-03-27T21:05:21Z

Please copy/paste the section related to log here.

You should see more logs.

montgomery102 · 2025-03-27T21:17:20Z

The below has been pasted into /homeassistant/configuration.yaml then home assistant was restarted. I then go to Settings>System>Logs.

logger:
default: warning
logs:
# Log for Pi-hole V6 integation
custom_components.pi_hole_v6: debug

The entry above was from the Home Assistant Core log with show condensed logs "on".
Here is what I get from the Home Assistant Core log with show condensed logs "off" or raw.

2025-03-27 17:13:52.235 DEBUG (MainThread) [custom_components.pi_hole_v6.config_flow] Session ID Hash: None
2025-03-27 17:13:52.235 DEBUG (MainThread) [custom_components.pi_hole_v6.config_flow] Request: POST http://192.168.51.47:80/api/auth
2025-03-27 17:13:52.239 DEBUG (MainThread) [custom_components.pi_hole_v6.config_flow] Status Code: 200
2025-03-27 17:13:52.239 DEBUG (MainThread) [custom_components.pi_hole_v6.config_flow] Data: {'session': {'valid': True, 'totp': False, 'sid': '[redacted]', 'validity': -1, 'message': 'password incorrect'}, 'took': 0.0003848075866699219}
2025-03-27 17:13:52.239 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] Connection failed: No session identity provided for endpoint requiring authorization.

I have created an "app password" in pi-hole and am using that in the HA interface. Otherwise the Pi-Hole does not have a password that is used to access the web interface.

montgomery102 · 2025-03-27T21:27:25Z

I was able to get this to work by setting a password for the web interface. Or sudo pihole setpassword the used that password in the configuration for this integration. Thank you @bastgau for all you help and I hope my discover helps you in the future. If you'd like to see any other logs from my system setup without a password please let me know.

bastgau · 2025-03-28T01:12:45Z

I have created an "app password" in pi-hole and am using that in the HA interface. Otherwise the Pi-Hole does not have a password that is used to access the web interface.

Not sure to understand the situation. The password was configured or not configured on your pi-hole instance. 🤷🏼‍♂️

Currently, only the pre-release versions allow to use the integration with a pi-hole instance which is not configured with a password.

Wendigogo · 2025-03-28T09:53:08Z

I have created an "app password" in pi-hole and am using that in the HA interface. Otherwise the Pi-Hole does not have a password that is used to access the web interface.

Not sure to understand the situation. The password was configured or not configured on your pi-hole instance. 🤷🏼‍♂️

Currently, only the pre-release versions allow to use the integration with a pi-hole instance which is not configured with a password.

Hello,

In my case, I have a password to login in the PiHole web UI.
I also tried with 1.8.0, 1.9.0 and 1.9.2 versions of ha-pi-hole-v6 with the exact same issue.

Is there a way to find the PiHole api key somewhere? To double-check the one I copy-paste is good.

EDIT :

I enabled verbose debug for API in pihole.toml and got this (with 1.9.2) :

2025-03-28 11:03:39.035 DEBUG_API Requested API URI: 192.168.1.88 -> POST /api/auth ? (null) (Content-Type application/json)
2025-03-28 11:03:39.035 DEBUG_API Received payload with size: 59
2025-03-28 11:03:39.035 DEBUG_API Processing POST /api/auth in /api/auth
2025-03-28 11:03:39.035 DEBUG_API Password not correct
2025-03-28 11:03:39.035 DEBUG_API API: Trying to auth with password but none set: 'c2O0PlxWqUhUzWE8tW3Rsovhkzl+3vqtsGnjdcE4I6A='
2025-03-28 11:03:39.035 DEBUG_API API Auth status: OK (empty password)
2025-03-28 11:03:39.035 DEBUG_API Done

The 192.168.1.88 is my HA instance and the 'c2O0PlxWqUhUzWE8tW3Rsovhkzl+3vqtsGnjdcE4I6A=' my current API password.

I restarted my HA for each ha-pihole-v6 update.

bastgau · 2025-03-28T11:31:24Z

Is there a way to find the PiHole api key somewhere? To double-check the one I copy-paste is good.

There is no way. You have to reset the application password.

#52 (comment)

user150aa346 · 2025-03-28T11:34:40Z

Can you provide us stack logs ?

Do you use MFA ?

I'm not using 2FA. How do I access "stack logs"? Here is the log entry generated in HOAS
2025-03-28 07:32:58.884 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] Connection failed: No session identity provided for endpoint requiring authorization.

Wendigogo · 2025-03-28T15:38:27Z

Is there a way to find the PiHole api key somewhere? To double-check the one I copy-paste is good.

There is no way. You have to reset the application password.

#52 (comment)

That's what I found too. The only way is to replace it with a new generated one.

Have you seen my edit with PiHole API debug logs? I don't understand this line :
2025-03-28 11:03:39.035 DEBUG_API API: Trying to auth with password but none set: 'c2O0PlxWqUhUzWE8tW3Rsovhkzl+3vqtsGnjdcE4I6A='
How could there be no password set with the API password given on the same line?

bastgau · 2025-03-28T18:00:26Z

How could there be no password set with the API password given on the same line?

I can't explain the Pi-hole logs. I never examined the Pi-hole logs.

However, the Pi-hole logs and the integration logs seem to be identical.

bastgau · 2025-03-29T14:13:01Z

I have just created a new pre-release v1.9.3.
Hope that we could debug the login issue easier.

Wendigogo · 2025-03-29T14:23:17Z

Here is my HA basic log:

custom_components.pi_hole_v6.config_flow
Source: custom_components/pi_hole_v6/config_flow.py:124
intégration: Pi-hole V6 Integration (documentation, problèmes)
S'est produit pour la première fois: 15:19:43 (2 occurrences)
Dernier enregistrement: 15:19:55

Connection failed: No session identity provided for endpoint requiring authorization.

bastgau · 2025-03-29T15:10:28Z

Just created a new pre-release. I think that the message will be "Incorrect password".

Maybe you have to change the "name" when you create the device.

Wendigogo · 2025-03-30T10:58:08Z

My previous message was on your v1.9.3.

Tried again with another "name" and got the exact same message.

EDIT : tried with a bad password and also got the same log message...

bastgau · 2025-03-30T13:51:45Z

Cannot reproduce the issue on my side.

Wendigogo · 2025-03-31T14:50:44Z

I can't understand what's happening here! 🤯

Using the exact same credentials in my browser give me no error:

I tried with both IP address or hostname and got the same working result.

And from my HA session :
Connection failed (http://bpihole.ici/api): The Pi-hole V6 server seems to be unreachable.

Wendigogo · 2025-03-31T15:18:05Z

And I also tried directly from HA terminal add-on and everything seems OK:

[core-ssh ~]$ curl -k -X GET "http://bpihole.ici/api/stats/summary?sid=h1xP+ZB8+P5CNhcz+J6a4gh+d7QcEiwsYn3t7pm8rfw="
{"queries":{"total":38675,"blocked":3240,"percent_blocked":8.3775053024292,"unique_domains":976,"forwarded":5473,"cached":28734,"frequency":0.3,"types":{"A":21728,"AAAA":7825,"ANY":0,"SRV":32,"SOA":0,"PTR":8666,"TXT":1,"NAPTR":0,"MX":1,"DS":0,"RRSIG":0,"DNSKEY":0,"NS":124,"SVCB":0,"HTTPS":298,"OTHER":0},"status":{"UNKNOWN":5,"GRAVITY":1097,"FORWARDED":5444,"CACHE":24972,"REGEX":2139,"DENYLIST":0,"EXTERNAL_BLOCKED_IP":0,"EXTERNAL_BLOCKED_NULL":0,"EXTERNAL_BLOCKED_NXRA":0,"GRAVITY_CNAME":4,"REGEX_CNAME":0,"DENYLIST_CNAME":0,"RETRIED":29,"RETRIED_DNSSEC":0,"IN_PROGRESS":1223,"DBBUSY":0,"SPECIAL_DOMAIN":0,"CACHE_STALE":3762,"EXTERNAL_BLOCKED_EDE15":0},"replies":{"UNKNOWN":1113,"NODATA":5079,"NXDOMAIN":7837,"CNAME":11551,"IP":12742,"DOMAIN":140,"RRNAME":53,"SERVFAIL":20,"REFUSED":0,"NOTIMP":0,"OTHER":0,"DNSSEC":0,"NONE":0,"BLOB":140}},"clients":{"active":37,"total":37},"gravity":{"domains_being_blocked":130850,"last_update":1743408179},"took":0.0001239776611328125}
[core-ssh ~]$ 
[core-ssh ~]$ curl -k -X GET "http://bpihole.ici/api/info/version?sid=h1xP+ZB8+P5CNhcz+J6a4gh+d7QcEiwsYn3t7pm8rfw="
{"version":{"core":{"local":{"version":"v6.0.6","branch":"master","hash":"0f7803b7"},"remote":{"version":"v6.0.6","hash":"0f7803b7"}},"web":{"local":{"version":"v6.1","branch":"master","hash":"1eaddca8"},"remote":{"version":"v6.1","hash":"1eaddca8"}},"ftl":{"local":{"hash":"a3313229","branch":"master","version":"v6.1","date":"2025-03-30 17:53:24 +0100"},"remote":{"version":"v6.1","hash":"a3313229"}},"docker":{"local":null,"remote":null}},"took":0.00016021728515625}
[core-ssh ~]$

user150aa346 · 2025-03-31T16:42:19Z

Working. First login failed, 2nd attempt worked.

bastgau · 2025-03-31T17:33:36Z

Good news @user150aa346 !

@Wendigogo The error is not the same now ? Are you sure that your Pi-hole instance is reachable by your HA container ?

Can you try using the IP adress ?

Wendigogo · 2025-03-31T18:45:02Z

@Wendigogo The error is not the same now ? Are you sure that your Pi-hole instance is reachable by your HA container ?

Can you try using the IP adress ?
That's what I already did before.

cURL answer have been done directly from HA terminal.
And it also works with IP address.

FYI : HA is on a VM and Pi-Hole on a LXC container.

bastgau · 2025-03-31T19:40:15Z

Terminal via an addon ? The addon use their own container.

bastgau · 2025-03-31T20:04:03Z

@Wendigogo

A new pre-release with another debug message 😄

https://github.com/bastgau/ha-pi-hole-v6/releases/tag/v1.9.7

Wendigogo · 2025-03-31T20:09:21Z

Terminal via an addon ? The addon use their own container.

I'll try directly from ssh' VM with the newest version.

Wendigogo · 2025-03-31T22:16:52Z

Oh my! I finally got it: My password has been reset with a blank one (no password to log on the webui).

I thought it was my password vault that fill it each time I went to these pages. And I don't know how this password has been removed. Maybe when setting the API one or messing with "toml" config file

Anyway, sorry for wasting your time with this. :/

bastgau · 2025-03-31T22:48:32Z

❌ @montgomery102
✔️ @user150aa346
✔️ @Wendigogo

I will release new version : https://github.com/bastgau/ha-pi-hole-v6/releases/tag/v1.10.0

jj33 · 2025-04-06T21:53:38Z

Using v1.10.0 and only http pi-hole setup.
Password from pi-hole setup/web/api copied and verified, no 2fa enabled

bastgau · 2025-04-06T21:57:47Z

Hey @jj33

Please provide the entire logs. Not necessary to mask your IP which are reached only from your internal network.

jj33 · 2025-04-07T01:17:29Z

Hey @jj33

Please provide the entire logs. Not necessary to mask your IP which are reached only from your internal network.

Best I could find:
2025-04-06 16:42:12.369 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] <class 'custom_components.pi_hole_v6.exceptions.UnauthorizedException'> - 401 Unauthorized # POST http://192.168.33.4:80/api/auth : {'session': {'valid': False, 'totp': False, 'sid': None, 'validity': -1, 'message': 'password incorrect'}, 'took': 0.23276019096374512}
2025-04-06 16:42:12.369 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] Connection failed (http://192.168.33.4:80/api): No session identity provided for endpoint requiring authorization.
2025-04-06 16:43:20.933 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] <class 'custom_components.pi_hole_v6.exceptions.UnauthorizedException'> - 401 Unauthorized # POST http://192.168.33.4/api/auth : {'session': {'valid': False, 'totp': False, 'sid': None, 'validity': -1, 'message': 'password incorrect'}, 'took': 0.22978734970092773}
2025-04-06 16:43:20.933 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] Connection failed (http://192.168.33.4/api): No session identity provided for endpoint requiring authorization.
2025-04-06 16:47:05.511 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] <class 'custom_components.pi_hole_v6.exceptions.UnauthorizedException'> - 401 Unauthorized # POST http://192.168.33.4/api/auth : {'session': {'valid': False, 'totp': False, 'sid': None, 'validity': -1, 'message': 'password incorrect'}, 'took': 0.2380821704864502}
2025-04-06 16:47:05.512 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] Connection failed (http://192.168.33.4/api): No session identity provided for endpoint requiring authorization.

bastgau · 2025-04-07T07:50:45Z

Hey @jj33

Do you use an application password ?

Thanks.

Wendigogo · 2025-04-07T08:30:38Z

Hey @jj33, do you have a password to login to web interface?

You should double-check this as mine has been removed at some point (and I still don't know how/why).

Enjoy!

jj33 · 2025-04-07T09:07:55Z

I do have a web login password, and verified it's still in there. I put in the API password, not the web login password. Is this correct?

bastgau · 2025-04-07T11:25:02Z

Application password and admin password should work.

jj33 · 2025-04-08T16:08:01Z

So the API password did not work, but the web login password did work.

bastgau · 2025-04-09T06:55:22Z

Good news @jj33 !

jj33 · 2025-04-09T09:25:09Z

It doesn’t explain why the API password that you are supposed to use does not work. Could lead to issues down the road when someone changes or removes a login password.Cheers,JoelOn Apr 9, 2025, at 1:55 AM, Bastien Gautier ***@***.***> wrote: Good news @jj33 !—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***> bastgau left a comment (bastgau/ha-pi-hole-v6#72) Good news @jj33 ! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

bastgau · 2025-04-09T10:26:34Z

On my side, the password application and the web password work well.

neilma1 · 2025-04-15T16:52:13Z

Not sure if its related, but mine recently stopped working, so I removed the integration and readded it. I used this as the URL
https://192.168.1.180/api (this is the ip adress of my NAS which is running Pihole)
Password is the same as the web page login password.

It seems to work but then when I go into the integration I have a red error and this message.
"Failed setup, will retry: The request was unacceptable, often due to a missing required parameter"

What is the missing required parameter ? Is it something wrong with the URL? Password? Or something else

Here is what I could see in the logs.....

Logger: custom_components.pi_hole_v6
Source: helpers/update_coordinator.py:380
integration: Pi-hole V6 Integration (documentation, issues)
First occurred: 5:47:36 PM (8 occurrences)
Last logged: 5:52:55 PM

Unexpected error fetching Pi-hole data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 281, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/pi_hole_v6/init.py", line 86, in async_update_data
if not isinstance(await api_client.call_get_groups(), dict):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/pi_hole_v6/api.py", line 446, in call_get_groups
result: dict[str, Any] = await self._call(
^^^^^^^^^^^^^^^^^
...<3 lines>...
)
^
File "/config/custom_components/pi_hole_v6/api.py", line 130, in _call
raise api_error
File "/config/custom_components/pi_hole_v6/api.py", line 126, in _call
handle_status(request.status)
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/config/custom_components/pi_hole_v6/exceptions.py", line 162, in handle_status
raise exception_mapstatus_code # noqa: RSE102
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
custom_components.pi_hole_v6.exceptions.BadRequestException: The request was unacceptable, often due to a missing required parameter

And then this other log....

Logger: custom_components.pi_hole_v6
Source: custom_components/pi_hole_v6/api.py:129
integration: Pi-hole V6 Integration (documentation, issues)
First occurred: 5:47:36 PM (8 occurrences)
Last logged: 5:52:55 PM

<class 'custom_components.pi_hole_v6.exceptions.BadRequestException'> - 400 Bad Request # GET https://192.168.1.180/api/groups : {'error': {'key': 'database_error', 'message': 'Could not read domains from database table', 'hint': 'Database not available'}, 'took': 0.0001804828643798828}
<class 'custom_components.pi_hole_v6.exceptions.BadRequestException'> - 400 Bad Request # GET https://192.168.1.180/api/groups : {'error': {'key': 'database_error', 'message': 'Could not read domains from database table', 'hint': 'Database not available'}, 'took': 0.0010867118835449219}
<class 'custom_components.pi_hole_v6.exceptions.BadRequestException'> - 400 Bad Request # GET https://192.168.1.180/api/groups : {'error': {'key': 'database_error', 'message': 'Could not read domains from database table', 'hint': 'Database not available'}, 'took': 0.00016379356384277344}
<class 'custom_components.pi_hole_v6.exceptions.BadRequestException'> - 400 Bad Request # GET https://192.168.1.180/api/groups : {'error': {'key': 'database_error', 'message': 'Could not read domains from database table', 'hint': 'Database not available'}, 'took': 0.00021004676818847656}
<class 'custom_components.pi_hole_v6.exceptions.BadRequestException'> - 400 Bad Request # GET https://192.168.1.180/api/groups : {'error': {'key': 'database_error', 'message': 'Could not read domains from database table', 'hint': 'Database not available'}, 'took': 0.00022077560424804688}

bastgau · 2025-04-20T09:17:58Z

The answer returned by Pi-hole API seems to be incorrect.

400 Bad Request # GET https://192.168.1.180/api/groups : {'error': {'key': 'database_error', 'message': 'Could not read domains from database table', 'hint': 'Database not available'}, 'took': 0.0001804828643798828}

The groups are available in the Pi-hole administration website ?

neilma1 · 2025-04-21T12:11:16Z

The answer returned by Pi-hole API seems to be incorrect.

400 Bad Request # GET https://192.168.1.180/api/groups : {'error': {'key': 'database_error', 'message': 'Could not read domains from database table', 'hint': 'Database not available'}, 'took': 0.0001804828643798828}

The groups are available in the Pi-hole administration website ?

Thank you for the pointer! Yes the DB was corrupt. I deleted it and everything started working! Thank you!

Diegocampy · 2025-04-29T13:43:59Z

Same problem.

[edit, solved... my problem]

Questo errore ha avuto origine da un'integrazione personalizzata.

Registratore: custom_components.pi_hole_v6.config_flow
Fonte: custom_components/pi_hole_v6/config_flow.py:161
Integrazione: Pi-hole V6 Integration (documentazione, problemi)
Prima occorrenza: 15:30:23 (4 occorrenze)
Ultimo accesso: 15:35:25

Connection failed (https://192.168.xxx.xxx:443/api): No session identity provided for endpoint requiring authorization.

Questo errore ha avuto origine da un'integrazione personalizzata.

Registratore: custom_components.pi_hole_v6.config_flow
Fonte: custom_components/pi_hole_v6/api.py:144
Integrazione: Pi-hole V6 Integration (documentazione, problemi)
Prima occorrenza: 15:30:23 (4 occorrenze)
Ultimo accesso: 15:35:25

200 OK # POST https://192.168.:443/api/auth : {'session': {'valid': True, 'totp': False, 'sid': None, 'validity': -1, 'message': 'password incorrect'}, 'took': 5.650520324707031e-05}
200 OK # POST https://192.168.:443/api/auth : {'session': {'valid': True, 'totp': False, 'sid': None, 'validity': -1, 'message': 'password incorrect'}, 'took': 4.1961669921875e-05}
200 OK # POST https://192.168.:443/api/auth : {'session': {'valid': True, 'totp': False, 'sid': None, 'validity': -1, 'message': 'password incorrect'}, 'took': 5.221366882324219e-05}
200 OK # POST https://192.168.:443/api/auth : {'session': {'valid': True, 'totp': False, 'sid': None, 'validity': -1, 'message': 'password incorrect'}, 'took': 4.029273986816406e-05}

The IP and port are correct. The integration fails to authenticate, even though the Pi-hole web interface confirms that the credentials are correct. The response message says "password incorrect" and 'sid' is None, which seems to be the issue preventing the session from being created.

Do you have any idea what could be causing this?

Thanks in advance!

bastgau · 2025-04-29T17:15:11Z

The IP and port are correct. The integration fails to authenticate, even though the Pi-hole web interface confirms that the credentials are correct. The response message says "password incorrect" and 'sid' is None, which seems to be the issue preventing the session from being created.

No idea.

The Json displayed indicating an incorrect password is returned by the API.

Diegocampy · 2025-05-05T15:24:51Z

sorry, I solved it, it was my problem, I solved it, everything works

f1rstxlas7 · 2025-05-08T22:08:56Z

Just making a quick note here because I was experiencing a similar issue.

When I uninstalled and reinstalled a fresh copy of Pi-hole it provided me with a password to login to the Web UI with. I thought that password was for use with this integration, but I realized I had to run the 'pihole setpassword' command on the RPi3 I was hosting Pi Hole on, set a password, and then use that password for the integration.

And for additional clarity sake, my URL target was https://pi.hole:443/api which is different from the one that's pre-populated in the integration.

pacorola · 2025-05-09T12:28:35Z

Mine allows setup with http:[MY_IP:8080]/admin and default web password, but then entities are all nonfunctional. I get this error log and curiously it relates to server details that have nothing to do with mine...

{'operationName': 'CheckAlarm', 'variables': {'numinst': '5716421', 'panel': 'SDVECU'}, 'query': 'query CheckAlarm($numinst: String!, $panel: String!) {\n xSCheckAlarm(numinst: $numinst, panel: $panel) {\n res\n msg\n referenceId\n }\n}\n'})
2025-05-09 14:18:06.347 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] Connection failed (https://192.168.1.180/api): The Pi-hole V6 server seems to be unreachable. # Cannot connect to host 192.168.1.180:443 ssl:default [Connect call failed ('192.168.1.180', 443)]
2025-05-09 14:18:16.877 ERROR (MainThread) [custom_components.pi_hole_v6.config_flow] Connection failed (http://192.168.1.180/api): The Pi-hole V6 server seems to be unreachable. # Cannot connect to host 192.168.1.180:80 ssl:default [Connect call failed ('192.168.1.180', 80)]

bastgau · 2025-05-09T12:57:02Z

I think that the default web password should work.

For the other issues, I don't know how I can help you. It is depending of your integration installation.

pacorola · 2025-05-09T13:02:01Z

Somehow it started working now!

bastgau added the question Further information is requested label Mar 27, 2025

Login problems #72

Login problems #72

Comments

user150aa346 commented Mar 27, 2025

bastgau commented Mar 27, 2025 • edited Loading

Wendigogo commented Mar 27, 2025

bastgau commented Mar 27, 2025 • edited Loading

montgomery102 commented Mar 27, 2025

bastgau commented Mar 27, 2025

montgomery102 commented Mar 27, 2025

bastgau commented Mar 27, 2025

montgomery102 commented Mar 27, 2025

bastgau commented Mar 27, 2025

montgomery102 commented Mar 27, 2025

montgomery102 commented Mar 27, 2025 • edited Loading

bastgau commented Mar 28, 2025

Wendigogo commented Mar 28, 2025 • edited Loading

bastgau commented Mar 28, 2025

user150aa346 commented Mar 28, 2025

Wendigogo commented Mar 28, 2025

bastgau commented Mar 28, 2025

bastgau commented Mar 29, 2025 • edited Loading

Wendigogo commented Mar 29, 2025

bastgau commented Mar 29, 2025 • edited Loading

Wendigogo commented Mar 30, 2025 • edited Loading

bastgau commented Mar 30, 2025

Wendigogo commented Mar 31, 2025 • edited Loading

Wendigogo commented Mar 31, 2025

user150aa346 commented Mar 31, 2025

bastgau commented Mar 31, 2025

Wendigogo commented Mar 31, 2025

bastgau commented Mar 31, 2025

bastgau commented Mar 31, 2025

Wendigogo commented Mar 31, 2025 • edited Loading

Wendigogo commented Mar 31, 2025

bastgau commented Mar 31, 2025

jj33 commented Apr 6, 2025 • edited Loading

bastgau commented Apr 6, 2025

jj33 commented Apr 7, 2025

bastgau commented Apr 7, 2025

Wendigogo commented Apr 7, 2025

jj33 commented Apr 7, 2025

bastgau commented Apr 7, 2025

jj33 commented Apr 8, 2025

bastgau commented Apr 9, 2025

jj33 commented Apr 9, 2025 via email

bastgau commented Apr 9, 2025

neilma1 commented Apr 15, 2025 • edited Loading

bastgau commented Apr 20, 2025

neilma1 commented Apr 21, 2025

Diegocampy commented Apr 29, 2025 • edited Loading

bastgau commented Apr 29, 2025

Diegocampy commented May 5, 2025

f1rstxlas7 commented May 8, 2025

pacorola commented May 9, 2025

bastgau commented May 9, 2025

pacorola commented May 9, 2025

bastgau commented Mar 27, 2025 •

edited

Loading

bastgau commented Mar 27, 2025 •

edited

Loading

montgomery102 commented Mar 27, 2025 •

edited

Loading

Wendigogo commented Mar 28, 2025 •

edited

Loading

bastgau commented Mar 29, 2025 •

edited

Loading

bastgau commented Mar 29, 2025 •

edited

Loading

Wendigogo commented Mar 30, 2025 •

edited

Loading

Wendigogo commented Mar 31, 2025 •

edited

Loading

Wendigogo commented Mar 31, 2025 •

edited

Loading

jj33 commented Apr 6, 2025 •

edited

Loading

neilma1 commented Apr 15, 2025 •

edited

Loading

Diegocampy commented Apr 29, 2025 •

edited

Loading