Just updated to Version 1.41.7.9795 to see if it fixes everything but for the last 2 versions i’m having 503 like one or twice per day…
I did move server and leave nvidia Quadro for intel, but probably not related.
Can you provide you server logs? This should have been resolved in the 9795 build.
i can. best way to send it to you? prv msg or share link?
You can DM me and just attach the zip file to the DM.
I’m getting it too. To clarify this isn’t the 500 not authorized. It’s 503 service unavailable
Yes. I did install this latest version but this morning was the same… 503 , service unavailable. Seems i cant send @drzoidberg33 message at this time:
An error occurred: Sorry, drzoidberg33 is not accepting messages at the moment.
Not sure if it matters but seeing these errors in the logs on the latest beta:
Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-b8182f5e6/HTbackdrops.bundle.
Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-b8182f5e6/Fanart-TV.bundle.
Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-b8182f5e6/PlexMovie.bundle.
on your case its also happening during the maintenance window? I did a database rebuild using the script but same behavior this mourning. I saw that a new version was release, already installed but from release notes could not find a connection to the problem
No it seems to happen 3-4 hours after restarting Plex. Will try the new version.
This latest version that came out last night, .9799 I believe, appears to have resolved it for me. This is the item that I believe addresses it (although it was noted in the last version as well) -
- (Agents) Requests to legacy agents routes would fail (PM-3385)
From my understanding, if you use the legacy agents, e.g. have “use local media assets” for sideloaded posters/subs/etc. this issue will arrise, which I do. So far, I haven’t had a crash since 9799 installed. Fingers crossed.
Please also see this thread/post: Library.db size more than doubled in latest version - #64 by drzoidberg33
@drzoidberg33 ahh thanks. I’ll have to check my db sizes to see if they ballooned. The other odd thing I noticed before is the temp transcode dir had ballooned massively. like tens of gigabytes, almost as if plex wasn’t cleaning up after itself, or perhaps the crashes were causing the orphans to stay behind. The latest version seems to have resolved this as well as the missing bw stats.
I did the update this morning, so lets see if tomorrow its all good and no 503 error 
i’ll wait for the update on the database size since i can live with it as long as Plex stays up and running will report back tomorrow.
If any test is needed @drzoidberg33 feel free to reach out.
Yep in doubled in size but doesn’t appear to be impactful right now so I’ll wait for the update which will handle it. Thanks for the heads up though. Good to know.
Good morning, just to give news about this beta, and no 503 until now. more that 48h uptime. Seems that the beta did its thing.
Thanks again for sharing this. I did end up manually clearing the entries. Although Plex seemed fine, some operations seemed slower, and maint tasks like backup db and/or optimize would hang the server for quite a while. Once clearing these entries, things seem back to normal.
There is one odd thing I noticed, perhaps normal but after running the SQLlite delete command, vacuuming, restarting Plex, the db was small but the wal files was still huge. I stopped Plex once more and started and wal file shrunk.
Good morning, i’ve spotted the 503 error again for 2 times now after the latest update: Version 1.41.9.9961 hope its temporary
If you see it again make sure to grab the server logs. Not much I can really do without that.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
