Plex Crashes Frequently: 503 Service Unavailable

After running fine for years, over the last month or so Plex has become unavailable several times a week.

When I attempt to log into Plex on my Win 10 server I get a 503 server unavailable message. Usually quitting and restarting will bring it back. Logs attached. Any help would be appreciated.

Server Version#: 1.16.3.1402 (just updated)
Player Version#: Latest Nvidia Shield App, iphone app, Web

Plex Media Server Logs_2019-07-16_21-35-52.zip (3.3 MB)

Is anyone from Plex here and able to help??

Continues to occur frequently. Latest logs attached.

It’s been five days since my original post. Can a long-time Lifetime Plex Pass member get a little help?

Plex Media Server Logs_2019-07-22_08-44-40.zip (3.5 MB)

i dont think anyone can help here, i posted same thing, and i read other posts detailing same thing, i just hope the crash reports are reaching plex tech support, because i never had an issue for years, and now it keeps having issues

Might help you gather more information.

1 Like

Thanks for the update, appreciate the response. Good to know I’m not alone.

Between this and the not able to watch a recording in progress from the beginning bug, Plex is becoming totally unusable. I’m sad to say that after years of using Plex without issue, I’ve been looking at alternatives as the bugs lately are adding up. I can’t just tell the wife and kids to wait, and maybe someone at Plex will look at my problem and fix it.

Emby has been rock solid so far.

I PM’d the Plex employee on that thread with my logs and dump files. Will keep you all posted.

The set of logs here are very good and show build up of requests from 10.0.0.6 (Media Room) and also from remote user (josephdixxxxx) and would need the /connections list and process dump at the time

The new diagnostics you PM’ed me for the 29th July do not show any deadlock and no 503s.
When you took the /connections list, the logs show that requests were being handled ok and no deadlock

Jul 29, 2019 22:06:31.365 [11152] DEBUG - Request: [127.0.0.1:58352 (Loopback)] GET /hubs/home/recentlyAdded?type=1&includeExternalMedia=1 (13 live) Page 16-50 GZIP Signed-in Token (Chewbaccaman)
Jul 29, 2019 22:06:31.369 [9208] DEBUG - Request: [127.0.0.1:58344 (Loopback)] GET /hubs/home/recentlyAdded?type=2&includeExternalMedia=1 (13 live) Page 16-50 GZIP Signed-in Token (Chewbaccaman)
Jul 29, 2019 22:06:31.420 [14132] DEBUG - Completed: [127.0.0.1:58352] 200 GET /hubs/home/recentlyAdded?type=1&includeExternalMedia=1 (13 live) GZIP Page 16-50 54ms 15236 bytes (pipelined: 4)
Jul 29, 2019 22:06:31.455 [14132] DEBUG - Completed: [127.0.0.1:58344] 200 GET /hubs/home/recentlyAdded?type=2&includeExternalMedia=1 (13 live) GZIP Page 16-50 86ms 16720 bytes (pipelined: 8)
Jul 29, 2019 22:06:54.401 [18204] DEBUG - Request: [127.0.0.1:58398 (Loopback)] GET /channels/all (5 live) GZIP Signed-in Token (Chewbaccaman)
Jul 29, 2019 22:06:54.404 [14132] DEBUG - Completed: [127.0.0.1:58398] 200 GET /channels/all (5 live) GZIP 2ms 712 bytes (pipelined: 1)
Jul 29, 2019 22:06:54.419 [18204] DEBUG - Request: [127.0.0.1:58398 (Loopback)] GET /photo/:/transcode?url=%2F%3A%2Fplugins%2Fcom.plexapp.plugins.unsupportedappstore%2Fresources%2Ficon-default.png%3Ft%3D1420494167%26X-Plex-Token%3Dxxxxxxxxxxxxxxxxxxxx&width=188&height=188&minSize=1 (6 live) GZIP Signed-in Token (Chewbaccaman)
Jul 29, 2019 22:06:54.421 [11244] DEBUG - Request: [127.0.0.1:58399 (Loopback)] GET /photo/:/transcode?url=%2F%3A%2Fplugins%2Fcom.plexapp.plugins.WebTools%2Fresources%2FWebTools.png%3Ft%3D1461650852%26X-Plex-Token%3Dxxxxxxxxxxxxxxxxxxxx&width=188&height=188&minSize=1 (6 live) GZIP Signed-in Token (Chewbaccaman)
Jul 29, 2019 22:06:54.442 [14132] DEBUG - Completed: [127.0.0.1:58398] 200 GET /photo/:/transcode?url=%2F%3A%2Fplugins%2Fcom.plexapp.plugins.unsupportedappstore%2Fresources%2Ficon-default.png%3Ft%3D1420494167%26X-Plex-Token%3Dxxxxxxxxxxxxxxxxxxxx&width=188&height=188&minSize=1 (6 live) GZIP 22ms 10222 bytes (pipelined: 2)
Jul 29, 2019 22:06:54.453 [14132] DEBUG - Completed: [127.0.0.1:58399] 200 GET /photo/:/transcode?url=%2F%3A%2Fplugins%2Fcom.plexapp.plugins.WebTools%2Fresources%2FWebTools.png%3Ft%3D1461650852%26X-Plex-Token%3Dxxxxxxxxxxxxxxxxxxxx&width=188&height=188&minSize=1 (6 live) GZIP 32ms 32598 bytes (pipelined: 1)

Jul 29, 2019 22:07:24.870 [20412] DEBUG - Request: [10.0.0.13:58407 (Subnet)] GET /status/sessions (5 live) Signed-in Token (Chewbaccaman)
Jul 29, 2019 22:07:24.871 [20924] DEBUG - Completed: [10.0.0.13:58407] 200 GET /status/sessions (5 live) 1ms 292 bytes (pipelined: 1)

Jul 29, 2019 22:07:29.551 [3040] DEBUG - Request: [[::1]:58415 (Loopback)] GET /connections (6 live) GZIP Signed-in Token (Chewbaccaman)
Jul 29, 2019 22:07:29.553 [20924] DEBUG - Completed: [[::1]:58415] 200 GET /connections (6 live) GZIP 2ms 746 bytes (pipelined: 1)

So would need to wait until you have a repeat of the error 503s as you had on the 21st July and capture the deadlock diagnostics

could you please let me know what was running on this machine

There were also requests building up from remote shared server Diamante - could you find out what version of Plex Media Server was running on it on the 20th July please

I’ve been running plex for years… Same thing… Crashes every day… 503 error.
logs attached… Plex Media Server Logs_2019-08-03_10-03-45.zip (4.5 MB)

Any help?

Just pm’d you with the latest connections, dmp and logs.

I am on version Version 1.16.3.1433, Windows 10

According to the connections logs, josephdixxxxx looks like they were running 1.16.3.1402-22929c8a2, Windows, 10.0 (Build 17763), PC, x64

Thanks for the help.

Went to go remove remote user josephdixxxxx from my friend list under sharing, as it looks like their server (Diamante) is causing issues according to the connections log.

Noticed that they now have two servers. And one (Diamante) is listed as “unavailable” in red. Could this be causing the problem?

It was believed to be caused by earlier versions of Plex Media Server - but i am not sure at this stage if 1.16.3.1402 does have that bug

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.