Problems since updating to Pi-Hole version 6.1.2

[Thedarklurch]

Since the update to Pi Hole version 6.1.2, the plugin no longer works, no matter how often I regenerate the app password or which address I enter for Pi Hole. Even if I leave the field blank, the add-on cannot seem to connect to Pi Hole; I see a yellow exclamation mark all the time. I've already tried reinstalling the add-on and now I don't know what to do, so I thought I'd write a post here.

[morficus]

Same issue here as well

[madpat1998]

It seems like the Plugin makes API calls to the wrong endpoint now.
Here is a line from my pi-hole webserver log:
"API: Bad request (key: bad_request, hint: The API is hosted at pi.hole/api, not pi.hole/admin/api)"

[madpat1998]

I logged into this Elgato piece ... again and downloaded the app again. The new version works for me.

[Thedarklurch]

I logged into this Elgato piece ... again and downloaded the app again. The new version works for me.

Unfortunately, even that didn't work for me, I also removed the app and reinstalled it via elgato but the same error no matter how often I redo the app password and no matter how many times I enter something else in the address line. Nothing worked

[z400MB]

Will there ever be a working version again? The current version (2.0) no longer works with 6.1.4. Reinstalling the plugin didn't help.

[dborod]

Any update of whether this bud will get resolved?

[t1m0thyj]

There shouldn't be anything in newer Pi-Hole versions that breaks the plug-in. Am using current version (2.0) with the latest Pi-Hole (Core 6.3, Web 6.4, FTL 6.4.1) without any issues.

If the plug-in isn't working for you, please attach log files from
C:\Users\<username>\AppData\Roaming\Elgato\StreamDeck\logs\us.johnholbrook.pihole0.log

[rtheil]

I just updated pihole to 6.x, as this plugin hasn't worked for months. It still doesn't work.

The plugin no longer displays any errors. I did find this entry in the FTL log, but I don't think it's relevant.

2025-12-11 16:50:18.422 GMT [1846/T2204] WARNING: API: Config item is invalid (key: bad_request, hint: webserver.api.app_pwhash: not of type string)

There is no us.johnholbrook.pihole0.log in StreamDeck\logs. There are no files at all that start with "us"

I deleted the plugin, reinstalled, got a new pihole app password and put it in place, and it still doesn't work.

So... what is different about pihole 6 from pihole 5? Why the api port number, of course. it's now 8080 by default, not 80. Is that the problem? IDK

Specifying 192.168.1.2:8080 as the "Address" does not work. Removing that port and switching to https does not work.

I can authenticate to the API just fine with postman via POST http://192.168.1.2:8080/api/auth

[rtheil]

I've just figured out a specific way to make this work

1. Delete the pihole button on the StreamDeck
2. Create a new pihole Toggle button on StreamDeck
3. Fill in the address FIRST with the hostname of your pi, with the same port the admin runs on. In my case "192.168.1.2:8080"
4. NOW fill in the app password (remember this is NOT the API key) from the settings page in the admin.

The toggle works for me, confirmed in admin.

After reviewing some of the code, it makes an assumption that the default address is "pi.hole", and that's it, so that's assuming port 80. But even though I can open the admin app with https on 443, I cannot get https to work on this plugin.

[t1m0thyj]

Https support is limited because the Stream Deck plugin doesn't support self-signed certificates - see #22 (comment) for workaround and this repo for more detailed instructions.

I believe this is a limitation of the JS web runtime, so the plugin would need to be rewritten in a native language like C# or Rust to support them.

[t1m0thyj]

I learned that the plugin backend can be updated to use Node.js instead of JS web runtime, which allows it to support self-signed certs. Opened #32 for this.

The changes are fairly big and I don't use HTTPS for my own Pi-hole, so would appreciate if someone can test the plug-in by installing it from source with the instructions in the updated readme.

[jku-sr]

I've just figured out a specific way to make this work

1. Delete the pihole button on the StreamDeck
2. Create a new pihole Toggle button on StreamDeck
3. Fill in the address FIRST with the hostname of your pi, with the same port the admin runs on. In my case "192.168.1.2:8080"
4. NOW fill in the app password (remember this is NOT the API key) from the settings page in the admin.

The toggle works for me, confirmed in admin.

After reviewing some of the code, it makes an assumption that the default address is "pi.hole", and that's it, so that's assuming port 80. But even though I can open the admin app with https on 443, I cannot get https to work on this plugin.

just wanted say, this sequence of reconfiguration worked for me on

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