As far as I can tell in 0.9.16.x (.0 and .1) my plex web just stops working sometimes after just a minute and always within 5 minutes. I checked the network traffic and I saw this after I tried to request something after it bombed out:
{error_name: “rate_limit”, error: “Creation of this event was denied due to rate limiting”}
and that was by calling:
https://app.getsentry.com/api/34246/store/?sentry_version=7&sentry_client=raven-js%2F2.0.5&sentry_key=[removed because I’m not sure if it’s confidential]
can I get any help? I can try revertin to 0.9.15.x if I have to.
The PLex web version is 2.5.8
Note that refreshing the screen fixes the issue, but that’s a little more than inconvenient.
I’ve also been getting this since 0.9.16.x! - A real pain!
At first I thought it was my network being overloaded as was copying files over at the time but nope happens on plex web consistently!
Oddly enough I still get the status bar updates at the bottom come through for library scanning etc even though the main web UI becomes unusable entirely.
Yup, I also notice that I get the status updates at the bottom. I’ve managed to stop the issue by navigating slowly when in the Web version (which is a huge PITA!!!). As long as I space my clicks out long enough it doesn’t happen, but this makes doing any management of my media a hassle instead of easy like it used to be.
I had that issue earlier, but I fixed it by using Firefox instead of Chrome.
I’m not sure if it’s the same for you tho 
Chrome has been pretty unstable for me lately, with Plex and other sites. No problems since I switched to using Firefox for my primary browser.
Thank you @Argotzz and @kegobeer-plex, but the error is occurring from an external web service call meaning that it’s not likely chrome (not sure how it could be).
I assume that something is saying “You’re calling me too much”, but saying that this started with this version, and chrome has not been updated since then, I am saying it’s on PLEX’s side. It could be using FF would fix it, but I’m not in the habit of changing my browser because a product broke something. I’m sure there is something that could be done on PLEX’s side to fix this.
I also have this issue in version 0.9.16.3 running on a 2010 macbook pro. Sometimes the web interface just doesn’t want to load pages. It isn’t only triggered by quick library navigation though. Sometimes I will have the web player minimized while streaming my music and it just stops mid-song, or fails to start the next song after one ends. When this happens the whole interface just turns gray and usually doesn’t work again until I refresh the page or wait a while (like at least a couple of minutes). Sometimes clicking on the settings icon or home button gives me the “no soup for you” message.
I’m a bit disappointed as this was all working beautifully just a few days ago.
*edit: This server is being accessed remotely btw, if that makes a difference. I haven’t been home to test whether or not it behaves this way on the local network.
**UPDATE: I’m sorry, I should have done further testing before making this post. This issue was actually affecting all of my network services and it ended up fixing itself after a reboot of my computers and my router. Somebody should probably delete this post
Informational: I can’t get Plex to work in Windows 10’s Edge browser at all (by the way, Edge lies and passes a Chrome user agent to the requestor because it uses much the same engine). Plex works perfectly in regular IE, the Silk browser on Kindle fire, and my daughter’s iPhone 6s and iPad (1st-gen). For the more nerd-minded, there’s a 64-bit version of Firefox called “Waterfox” - Plex seems to run fine on that for me, too.
I checked the network traffic and I saw this after I tried to request something after it bombed out:
We use Sentry for error reporting. Can you look in Chrome’s Console for the error that is trying to be reported? That will hopefully lead us to the actual problem. Also, which version of Chrome are you using?
@ericmatthys said:
I checked the network traffic and I saw this after I tried to request something after it bombed out:
We use Sentry for error reporting. Can you look in Chrome’s Console for the error that is trying to be reported? That will hopefully lead us to the actual problem. Also, which version of Chrome are you using?
I reverted back to the previous version 0.9.16.0 and I haven’t seen it since then. I will try and get the information you asked for it I see it happen again. Truth is I rarely use the Web interface, but when this was happening I was doing a lot of maintenance.
I get this issue too, im getting tired of updates causing issues, the last 3 i have had to roll back due to faults like the service crashing, yes they all eventually get fixed but for the week it can sometimes take to do that im left with a barely functional media server
The problem on the surface sounds like an error that was happening in Chrome beta / canary builds, which Google has fixed recently. We’ll need more information to be any help here.
yes i also have this issue as well where pages do not load or just take super long and recently been seeing more and more “Remote Access” issues, which is not my internet as im running fibre and ive configured my network firewall and so forth it keeps saying " Not Accessible outside your network" which drives me nuts.
Am running standard release of chrome…installed like a week ago after a new PC build, not on beta
