Server Version#: 1.41.5.9626
Hi team,
When I try to grant access to a library, I am getting 429 errors from sentry.io. I had uBlock Origin enabled prior to getting the errors, and it was completely blocking sentry.
Is there anything you can do to reset this limit from me? I don’t quite understand how I got myself into this state, as I’m not doing anything particularly quickly, nor in a manner that I wouldn’t normally. I’m just clicking around.
There is nothing to reset by us.
Operations has made it self-correcting.
If you hammer on it, it will lock you out again (429)
Thank you, giving this a go. I’ll report back if I’m still blocked.
I’m still blocked, @ChuckPa . I have a JSON payload in that call which I can share, which mentions a typescript error: “Cannot set properties of undefined (setting ‘isSharing’)”.
I can provide the full log, but I don’t want to share it publicly as it has IPs/library names/god knows what and I think I don’t have perms to DM you.
I shut down plex on the NAS for 1h20m by the way.
Could it be because my server version is old enough that the frontend has moved ahead? I installed it via the synology installer in DSM. I think it’s out of date, I will try an update.
The version isn’t too old. I am concerned what this sentry.io is.
Google search reveals it’s some sort of management service/app and in no way associated with Plex at the user level.
Internally we use Sentry (the company) for our crash/failure reporting collection.
This is how “Send crash reports to Plex” works.
I’m going to need to see your Server’s DEBUG logs ZIP file.
Specifically:
The process I followed:
Stop Plex
Wait 2-3 minutes
Start Plex
Wait another 3 minutes
Attempt to grant access to the library to this user (who is also now in my plex home, for some reason their plexamp still can’t see the library even when on the same wifi - no other devices, including my shield have this problem, and it’s the same model of phone as mine, which works out of the box).
Download the logs ZIP file
Attach that ZIP file here.
@ChuckPa , I think I found the smoking gun for you. Here is an image of my console when I click the send button:
That last Typescript/Javascript error means the front-end is unhappy with some state when I click Send. I can’t dive into the code because it’s minified. If I click the send button enough times, sentry.io rate limits me - fair enough, it’s working.
Also, this might be a red herring - but I am also puzzled why Plex tries to talk to 127.0.0.1, and then gets a bunch of CORS errors. I don’t have a server running locally - does it reach out just in case there is one?
Some more detail - I previously claimed plex on another synology NAS that is in storage. I’ve set up a new media server on this new machine, and claimed it on my plex account. Perhaps the machine identifier has some sort of conflict due to this.
I see
This is docker we’re working on and not Synology?
The logs/videos I posted were using the one-click install from Synology Package Manager.
After posting, I uninstalled that and tried to run with Docker using plexinc/pms-docker, and claimed it. Console says that I have 3 servers, and with this new image the way this manifests is different - no console errors, but I get a “You have no servers connected” error and the Send button is greyed out.
For my main account that claimed the server, I can use/see it with everything. For the new account that I’ve added to my plex home, I am not able to grant them access to my library either with the Synology installation or Docker using Synology Container Manager (Docker under the hood).
In both cases I am running this on a DS920+ that is up to date that belongs to my father. My own DS920+ always worked perfectly fine with Plex, but it’s currently in storage being shipped between countries, so it’s offline - and I’m staying with them, hence claiming this new one.
