The server is unreachable

Plex Media Server Desktops & Laptops
1

Server Version#: 1.15.0.573-123756e9a
Player Version#:

Hi i keep getting The server is unreachable says 5 times a week am on 1.15.0.573-123756e9a never had this on Plex Media Server 1.7.5.4035 thank you.

1 Like
2

Having the same problem over here. To the point where I canā€™t use my Plex anymore.

1 Like
3

Iā€™ve just had a similar problem over the last couple of days- all of a sudden I get a ā€˜The server ā€œNASā€¦ā€ is unreachable. Make sure itā€™s running, double check your network, and try again.ā€™ message.

Iā€™ve had it before but then itā€™s started working again without any action on my part but not for as long as this. Did you manage to resolve this in the end? I didnā€™t want to start messing around with my whole set up if it was just a Plex issue again. The NAS seems to be working fine but Plex isnā€™t working on the various platforms I usuallly use (PS4, laptop, firestick etc).

4

Nope and no reply from Plex mods even done a new post still ignored frustrating

5

Just had a look at the logs. Your post did not get picked up at the time

Appears to have been a deadlock which resulted in build up of requests eventually leading to 503 responses being returned (Service Unavailable) by the server

Jan 22, 2019 20:49:00.593 [0716] DEBUG - Completed: [::ffff:86.40.69.222:46772] 503 GET /library/parts/5712/1547007568/file.mp4?autoAdjustQuality=0&hasMDE=1&location=wan&mediaBufferSize=74944 (444 live) 2ms 290 bytes (range: bytes=0-)

If this is still happening on current public or beta release, please let me have fresh logs from those releases - the public being currently 1.15.4.993 and beta being 1.15.5.994 and i will look into it.

If deadlocks still arising then we would need to have some specific diagnostics collected which I will advise on once it is confirmed that this is still the case

6

What does this mean mate sorry.

deadlock which resulted in build up of requests eventually leading to 503 responses being returned (Service Unavailable) by the server

7

To explain -

Plex Media Server is multi-threaded and a number of threads would be active. Threads use locks to make sure that the action they are performing can complete uninterrupted and release the locks after.

A deadlock would arise when the lock is not released and other threads are locked out. This leads to new requests from Plex client apps to get queued and the queue builds up over time and the requests remain outstanding and would probably timeout at the client end. When the queued requests reaches a certain level, 503 HTTP Response Codes start to get returned.

1 Like
8

Is there any way to fix this user side or how to stop it.

9

It would a Plex Media Server issue that needs to be fixed by the development team - if it is still happening on current releases

Please see my earlier response, If it is still happening on the current versions then it needs to be investigated and referred to the development team

See The server is unreachable - #5 by sa2000

10

Ah i see iv tried all version up till the latest released few hours ago ill let you know when it happens again thank you for your time.

11

Thanks for the logs from version 1.15.4.993-bb4a2cb6c
The server did overload and start to return 503 responses at 20:01 on April 27th

Is this the normal load on the server? And who is accessing the server? I see within a 2 minute period connections from over 100 IP Addresses to your server - with a number sharing the same plex.tv account at the same time.

It is possible that this is not a deadlock but severe server overload with many simultanuous wan connections streaming

If this is genuine use with normal workload that has worked before, then would be happy to investigate and see why we started to return 503 responses.

The following would be the diagnostics for the server ending up with 503 responses being returned

What is needed is the connections list plus a process dump and the logs

To get the connections list, a specific request needs to be made in a browser on the server. The request needs to have the Plex Media Server security token included in the url. So first is to find the server security token - see https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
Note down the token string to use later

When a deadlock arises, please do the following

  • On the server use browser to make this request
    http://127.0.0.1:32400/connections?X-Plex-Token=xxxxxxxxxxxx
    Substitute the server security token for the xxxxxxxxxxxxx
    Copy the displayed response into a text file and note down the time of the request.

  • Confirm that the server is still inaccessible

  • Wait a couple of minutes and repeat the connections request and save the response and note down the time

  • Load the Windows 32-bit Task Manager (Run: C:\Windows\SysWow64\Taskmgr.exe)

  • Within this task manager, click on the Details tab and locate the Plex Media Server.exe process, right click on it and select Create Process Dump

  • Note down the location of the resulting .dmp file

  • Copy out the server log files to a new temporary directory
    C:\Users\Administrator\AppData\Local\Plex Media Server\Logs
    and Zip the copy

Zip the produced process .dmp file and upload to dropbox or similar service and send me link by private message. Similarly zip the 2 connections list and send to me with the times
And the zipped logs

12

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