Yesterday, I had to rebuild my Plex server from scratch because the database corrupted and wouldn’t launch. I signed into the new Plex install (same Ubuntu 16.04LTS virtual machine, running official Plex Docker image), and all my friends are listed. Of course, since this is a new server, I have to (individually) share my libraries with them.
I can share with exactly five people (selecting “All Libraries”) before I get this error message. I have been running Plex for almost five years, and have never seen this before. If I wait a period of time - I’m not sure how long exactly, but at least five minutes - I can add five more before I run into this again.
It’s worth noting that I run two different Plex servers (different virtual machines on the same host, using the same internet connection), and I can add five PER SERVER before I hit what appears to be a timeout, so this is CLEARLY a per-server limitation imposed by Plex
What the hell, Plex! There’s several topics dating back over a year about this issue. It spans multiple version on multiple platforms, so clearly it’s an API change. This won’t impede people running mass share scripts, because the script will simply keep trying, or they’ll add a pause after five attempts. Just like DRM and having to answer questions out of video game manuals to play Wing Commander, this only inconveniences LEGITIMATE USERS.
Can we at least get an official response to this, preferably with a fix? Between this, the inability to locally authenticate when my internet is out (making Plex useless), and the constant addition of new features no one wants while core functionality issues remain unaddressed for years, it seems like you’re trying really hard to scare away your core customer base. I have two lifetime Plex Passes. I would pay a monthly fee to have “premium” support. I want to give you my money, but not if you keep pulling this carp!
I hear Jellyfin and Emby are coming along nicely these days.