Just noticed this feature the other day while fiddling around for something else. Fantastic news, Plex Team! When the heck was this introduced? Can’t believe I missed it until now.
So happy with my Plex server now: Able to limit max bitrate for any user, able to to limit max streams per user and able to limit daily data quota per user.
The holy trinity is been achieved!
How are you limiting bitrate for certain users or daily quota?
What I really want still is a way to make it so certain users only have access one the network but not remotely.
Where is this settings? I couldnt find it anywhere :(. I have the latest PMS and plex web.
“Remote streams allowed per user” is in Server > Network. I’m on PMS Version 1.4.2.3400
Royal2000H, check out my post on daily quotas:
anyone else having an issue with this? i set the “remote streams allowed per user” to a value of 1. Whenever a second person using the same account tries to connect, it causes my server to lock up. I was forced to set the setting back to “unlimited”.
I’m not sure the feature actually works. I put my iPhone and iPad both on LTE and with the setting set to 1, it didn’t stop my iPhone from streaming after my iPad had already started streaming.
@doce957 multiple members here in the forum are experiencing the same problem as you. Anything higher than “unlimited” and the system crashes.
I don’t have the issue of crashing on my end, but I’ve yet to actually see the limit work. I have it set to 1 and yet I can start more than 1 streaming session on my account and other accounts. Is this feature simply not working at all? Has anyone got it to work?
@Ikornaselur said:
I don’t have the issue of crashing on my end, but I’ve yet to actually see the limit work. I have it set to 1 and yet I can start more than 1 streaming session on my account and other accounts. Is this feature simply not working at all? Has anyone got it to work?
@Ikornaselur Just to be sure… Are you testing it with streams on your local net or remote to your server? It only applies to streams outside of your network [ nevermind 
]
…and I just tested it as well, mine doesn’t crash either but it does allow more than the 1 stream I set it to
For those that are having issue, and seeing crashing, do you have Enable Plex Media Server debug logging enabled?
If so turn it off and try again.
@cayars Do you happen to have a link to the other thread(s) where the crash is mentioned?
@thebrain said:
Just noticed this feature the other day while fiddling around for something else. Fantastic news, Plex Team! When the heck was this introduced? Can’t believe I missed it until now.
1.4.0. Looks like it didn’t make the release notes.
There is a crash when this limit is hit and debug logging is enabled. When this limit is hit one of the internal objects is left in a state that the logger didn’t quite know how to handle. The crash was fixed already and hopefully should make the next release.
For systems that automatically restart crashed services, such as Linux, it can appear as if the limit is not working because the server gets restarted thus effectively clearing the limits. Then as clients re-establish their playbacks (whilst playing from their own media buffer), the number of playbacks mount up until the limit is hit again and it starts all over. This can make it appear as if the limit is not being enforced.
So, until this crash is fixed (#6427), you should either disable the per-user stream limit or disable debug logging. Either will avoid the crash.
I can confirm that as soon as I tried without debug logging enabled, it works just as advertised.
Are there any plans for allowing individual users to have more slots than others?
@gbooker02 said:
@thebrain said:
Just noticed this feature the other day while fiddling around for something else. Fantastic news, Plex Team! When the heck was this introduced? Can’t believe I missed it until now.1.4.0. Looks like it didn’t make the release notes.
There is a crash when this limit is hit and debug logging is enabled. When this limit is hit one of the internal objects is left in a state that the logger didn’t quite know how to handle. The crash was fixed already and hopefully should make the next release.
For systems that automatically restart crashed services, such as Linux, it can appear as if the limit is not working because the server gets restarted thus effectively clearing the limits. Then as clients re-establish their playbacks (whilst playing from their own media buffer), the number of playbacks mount up until the limit is hit again and it starts all over. This can make it appear as if the limit is not being enforced.
So, until this crash is fixed (#6427), you should either disable the per-user stream limit or disable debug logging. Either will avoid the crash.
I’m on windows and I don’t have debug logging enabled. Setting a limit to 1 does nothing.
Are you sure it works?
I confirmed similar behaviour yesterday. I turned on 1 remote stream per user and throughout the night noticed 2 instances where my server went offline.
Easy enough restart the plex app and away we go.
Then again later on that night the server crashed again.
My only explanation at the time was I enabled this 1 remote stream per user feature, and it had to be related.
Turned it off and it hasn’t crashed since.
I haven’t dumped any logs at this point but after reading through this thread I am pretty confident that it is the cause.
