Restarting PC/Streamdeck software causes new active session

[Derezzler]

I received an error today that I've hit my max amount of active sessions when trying to troubleshoot one of my Piholes.

It looks like every time I reboot or restart the streamdeck software it creates a new active session. It created so many instances between my 2 Piholes I didn't know what was what and had to cli into them to add to max session amount to be able to access the Piholes and remove them all.

I reduced the session timeout to default from 7 days to maybe help mitigate it but would like to go back to 7 days eventually so I'm having to enter my credentials too often when checking the stats from my PC via web GUI.

I have 2 Piholes w/unbound - 1 Raspberrypi Zero W on Dietpi, and 1 docker on my QNAP NAS
Each have a button on the stream deck to toggle disable them
I also have a multi-action button to disable both at once

I might be wrong because it looks like it creates a new session for each button. I don't think this is normal as the other sessions from other things such as my home assistant and Pihole remote on my phone do not create multiple active sessions.

[t1m0thyj]

I might be wrong because it looks like it creates a new session for each button

This is correct - currently sessions are stored per-context which is unique to each button. If they were stored in a global map per Pi-Hole URL, this would reduce the number of sessions created by the plug-in.

[marty-andrew]

Also experiencing this and had to temporarily increase webserver.api.max_sessions to 32, I have 4 buttons configured, controlling 2 pi-hole's, so only 2 buttons each and had this error. Also using Homepage docker container and it was only when the Stream Deck was added that the API limits became a problem.