Suspend accounts

Just something I would like to see is the ability to suspend a specific account. Now, if I want to kick someone from my server because he is watching something and taking up all of my cpu, I have to delete his account or close the server completely.

 

Maybe we can already do it, just don't know how.

 

Thanks. :)

plex.tv

Servers

Edit sharing

Revoke.

have fun

Yea. Revoking someone is hardly the same as suspending them.

Yes, but this isn't built to be a commercial server or servicing 5 million people.  We do not need to complicate the product by putting in a lot of features to support the 1% that uses this for sharing among many people.

PS  By commercial I mean we should not be setting up commercial servers servicing  many people.

Yes, but this isn't built to be a commercial server or servicing 5 million people. 

You seem to be reading too much into this request.

Blocking account access could be useful for many reasons.  I'd like to easily be able to block my daughters account, for example.

Why not just keep the share but remove access to the sections?  That you can easily toggle on and off. 

I for one would love more customisation in regards to sharing, so I support this request 100%

I think its a great idea.

It's not for commercial purpose at all. When 3-4 friends (and me) are on my server watching a movie the CPU resources are at 100%, I cannot do anything else on my computer, this is not practical at all. If I revoke the invite, I have to resend an email for them to get back in. Having the ability to suspend/pause the accounts would take care of this.

You seem to be reading too much into this request.

Blocking account access could be useful for many reasons.  I'd like to easily be able to block my daughters account, for example.

You might want to refer to the lengthy Parental Controls thread, then.

It's not for commercial purpose at all. When 3-4 friends (and me) are on my server watching a movie the CPU resources are at 100%, I cannot do anything else on my computer, this is not practical at all. If I revoke the invite, I have to resend an email for them to get back in. Having the ability to suspend/pause the accounts would take care of this.

Or you might want to look at the threads mentioning limits on concurrent users, bandwidth limits, etc.  Why would you want to maintain suspending and reactivating users constantly?

You might want to refer to the lengthy Parental Controls thread, then.

Why?  Can this feature not stand on its own?

You might want to refer to the lengthy Parental Controls thread, then.

Or you might want to look at the threads mentioning limits on concurrent users, bandwidth limits, etc.  Why would you want to maintain suspending and reactivating users constantly?

I agree these are both great options, and I myself would be extremely happy if we could put limits on concurrent users. Thats probably my most wanted feature.

But none of this have been implemented yet. For god knows what reason. So why can't this request stand on its own? Could this be easier to implement? If so, why not do it?

I am all for any new features that give us increased control and security of our servers. They are desperately needed, in my opinion. The fact the server has almost no control over any client request it receives, is just very simply not a good situation to have at all. The all or nothing approach Plex has used to date for Server/Client connections, is a poor substitute for proper controls.

I am all for any new features that give us increased control and security of our servers. They are desperately needed, in my opinion. The fact the server has almost no control over any client request it receives, is just very simply not a good situation to have at all. The all or nothing approach Plex has used to date for Server/Client connections, is a poor substitute for proper controls.

The primary control is fairly obvious...don't share the server with people that could negatively impact performance.  That's not granular enough, but it is pretty effective for non-local clients.

The primary control is fairly obvious...don't share the server with people that could negatively impact performance.  That's not granular enough, but it is pretty effective for non-local clients.

I have no problem at all with my shared users. What I am asking for is proper control of the server in a Server/Client relationship. Like the way any properly coded Server/Client system would be coded. I've been in IT for 35 years now, and I've never seen a serve/client relationship where the Client has all the control, and the server has none, like the way Plex currently is constructed.

I have no problem at all with my shared users. What I am asking for is proper control of the server in a Server/Client relationship. Like the way any properly coded Server/Client system would be coded. I've been in IT for 35 years now, and I've never seen a serve/client relationship where the Client has all the control, and the server has none, like the way Plex currently is constructed.

Look at the closest parallels to Plex.  DLNA servers have almost no controls at all.  The majority of installations have very limited users attached to them, normally within one family.  You see this as a client/server piece of infrastructure where most see it as a media server.  To many, a media server is a piece of hardware with almost no configuration possible.  This is not sendmail or MySQL.  If it were, its configurability would severely hamper its usability.

The oft-cited complaint is that Plex is not implementing features fast enough.  If Plex waited until it had a complete set of controls for every feature, no features would ever be released.  Currently, sharing is a light switch and you'd like it to be a dimmer on a timer.  I'm glad we have sharing and happy we didn't have to wait for the dimmer just to turn on the light.

Look at the closest parallels to Plex.  DLNA servers have almost no controls at all.  The majority of installations have very limited users attached to them, normally within one family.  You see this as a client/server piece of infrastructure where most see it as a media server.  To many, a media server is a piece of hardware with almost no configuration possible.  This is not sendmail or MySQL.  If it were, its configurability would severely hamper its usability.

The oft-cited complaint is that Plex is not implementing features fast enough.  If Plex waited until it had a complete set of controls for every feature, no features would ever be released.  Currently, sharing is a light switch and you'd like it to be a dimmer on a timer.  I'm glad we have sharing and happy we didn't have to wait for the dimmer just to turn on the light.

Yes, Plex started out as a simple media server, and that's all it was for years. But 2 years ago they chose to make it a Server/Client relationship with remote clients outside the relative security of the local network.

There are security issues that have been known for 30-40 years now that need to be implemented when you choose to create a system like that. The main one being that the Server has control of what the clients can do on that server when needed. I am in no way saying that Plex had to put those in place on release of that update. I am also glad that they introduce new features that the user base wants. What I am saying is that there controls that are sorely needed now, because it is Plex that advertises this as a Server/Client system now. Not me, or others like me, that keep hammering away at this issue here. Server controls are needed to be in place if you are going to put that type of system into the hands of the non-technical consumer base. Especially with all the security issues raging on the Net these days. Plex is allowing lay people to expose their personal PC's to intrusion, and the vast majority of non-technical Plex server users are not aware of that fact at all. So in my opinion it is up to the developer to safeguard their customers PC by introducing proper, industry standard controls to this system. Same as I've had to program into Server/Client systems I've worked on for the past 30 years. It's really as simple as that. ;)

And note, I am not demanding that they do this immediately before working on anything else. I just want it to be taken care of at some point. Hopefully sooner than later, but I'll take what I can get.

Or you might want to look at the threads mentioning limits on concurrent users, bandwidth limits, etc.  Why would you want to maintain suspending and reactivating users constantly?

And where are those options in Plex ?

So, in short what you are asking for is an extension to a Parental Controls system.

There is already a very long and well established thread on the Plex Pass forums regarding this and it's variations and related requests (and the 38 ensuing pages)

No, let's put it this way, what I would like to see is a way to suspend a user account without having to delete the account itself. And why not put that option and those for the library sharing right into Plex media server and not via the web page ?

It's just an idea, would be more practical imo.

1 Like