i have to take my server offline to stop this, the third part client Plezy is bugged, whoever use it is locked into the server and their session cannot be terminated nor can i do anything to them, i already reported this to plezy author but it seem this is a bug in plex end as well for third part clients?
author responded that this is plex issue not his issue, i am not sure how plezy is able to hold plex hostage like this, but any solution is welcomed, settings in server side such as terminate after x paused or kill sessions is not applicable to plezy, the client flat out ignore it
There a couple of parts to this feature, a) a client must pass a unique X-Plex-Session-Identifier header for each playback session and b) to display the termination message the client must implement this.
It sounds like the client may not be properly starting playback sessions.
anyway from plex end to stop clients that are not respecting this? i cant block people from using this tool except to kick the user out completely at the moment
Out of curiosity, how often are you terminating playback sessions? And, if it’s more than very infrequently, why are you continuing to allow those users to access your server?
this isnt the point at all, i own a server, there shouldnt be a client that ignore whatever the admin do, it doesnt matter if i terminate or not. its not even just termination, it doesnt even pass a sessionid, god knows what other stuff it might be doing?
i think but not confirmed yet, its not even respecting the buffer limit i have, its just ignoring all the rules
I just tested this scenario now, terminating the session does work and PMS will terminate the connection to the client, however the Plezy client will continue playing what it has in its buffer and then just freeze when it runs out of packets.
Once frozen it still continues sending timeline requests so it looks like it’s playing in the Plex dashboard but the video stream was terminated and the user would have to stop the playback session and start it again to get it to work again.
The Plezy client doesn’t appear to have any functionality to understand what is happening here and display the termination message sent by the server.
Feel free to test this yourself but just make sure you’re not testing with the client and server on the same machine as this will bypass these checks.
it doesnt respect the buffer limit, i have 60s but it can buffer 3 eps in advance somehow
it cant be blocked in taut
it doesnt have sessionid
and no, you cant always terminate it, it does work if its first session for some reason but after you play back to back then “stop session” doesnt even show anymore, and in certain situations but i cant pinpoint them yet
there should be min. requirements to allow clients to access plex api
nope, it is playing normally now even tho im blocking it, i am doing it outside of my network, i can even see taut sending the kill trigger in log, but the client completely ignore it