Plex update 1.13.9.5439- Server unreachable

Plex Media Server NAS & Devices
25

@Cyborg1 Yes, and that is not the issue. I have confirmed (as stated in my update above) that this issue seems to be confined to 1.13.7.5369 and perhaps other .7 builds (I have no other builds to test). You will NOT experience this problem on a port bonded unit (even with a single NIC active) because both NICs are tied to the same IP address. The underlying issue seems to be related to PMS trying to use the IP of NIC2 that in a Synology can not be truly disabled.

I am going to hold at v1.13.5.5291 until I hear from someone on the dev team that they have identified and corrected the issue on forthcoming releases. As @ChuckPa stated above, “
 Punt 1.13.7 entirely — It’s beta”

26

I ended up rolling all the way back to 1.13.4.5271. I tried almost every version in between and they all had the same issue (including 1.13.8), couldn’t connect to server. 1.13.4 seemed to fix my problem for now. Seems like a lot of people in general are having this connection to server issue with the last few updates.

27

I started having issues again with v1.13.5.5291. I was not getting the same network type issues that I saw before, so I guess I am now in a more similar boat to @Cyborg1.

I have downgraded again to v1.13.4.5251 *as that is the only v1.13.4.x build I had on hand. Things are now working for me again.

I see that v1.13.8.5395 has now been released. @ChuckPa do you have any feed back on these issues? Does v1.13.8.x have anything that may have resolved things? Wife is getting pissed with the down time LOL.

28

Stay at 1.13.4 for the time being. There is a lot going on and resources are a bit stretched ATM to diagnose new issues.

29

This is still an issue in 1.13.9.5439. I have replicated this issue in every version starting in 1.13.6. (didn’t have 1.13.5 to try out) currently I am stable on 1.13.4.

30

@Cyborg1

Please do not edit the thread title after dialog has begun.

Editing the title breaks the links I have in external documents used to track issues.

Editing the title has introduced ambiguity. Did this start with 1.13.9 or really with 1.13.7 or 1.13.6 or 1.13.5?

31

This issue started in 1.13.6 (although i don’t have 1.13.5 to try out). As I said this issue is present in every version I have tried after 1.13.4.

32

On my 916+ I uninstalled and removed the Plex folder to start from scratch. I then installed 1.13.9 and tried to access it locally, I get the same result ‘server not found’. When I try this same method with 1.13.4 I am able to access the server first try.

Not limiting it to one Synology, I tried both 1.13.4 and 1.13.9 on a 918+ with the same result. One step further I setup another router with only the Synology attached to rule out any networking related causes
still no go.

I am fully confident at this point it is not my network setup and not my Plex configuration.

33

If it’s not your network and not your configuration, what is it?
There are those with issues but there are more without issues.

What’s unique with your network and PMS setup?

34

Good question. I normally have port bonding with the synology/router, turned this off to make things simple plus this didn’t give me any trouble in 1.13.4.

I know that moving to anything newer than 1.13.4 breaks the connection. It looks like there was a large overhaul on version 1.13.6 (in my mind the issues start in this version).

Other than setting up a Synology from scratch (I would move to windows before I did that). I am not quite sure what else to try.

35

Let’s spin back to networking 101 and make sure of the basics.

  1. The LAN’s IP range is per RFC1918 (192.168.x.x, 10.x.x.x, or 172.16.x.x - 172.31.x.x) ?
  2. Everything wired or on a WiFi which does not have “Network Isolation mode” enabled ?
  3. They all have the same DNS resolver (modem/router) ?
  4. They all have the same network gateway (modem/router) ?
  5. IPv6 is disabled for all ?
36
  1. Yes, using a 10.x.x.x
  2. Everything is hard wired
  3. All on the same DNS resolver (router resolving to 8.8.8.8)
  4. All on one router/modem
  5. IPv6 is off on the synology and on the router

-On another note if plex is uninstalled (via package center) and then the folder is deleted, what happens to the SQLITE database?
Reason I am asking is because once reinstalled I took another look at the logs and see a ton of data corruption errors.

37

On Synology, the installer does not remove your metadata when you uninstall the package.

I did it this way because Synology does not allow us to install versions lower than that which is currently installed. To switch to a previous version of PMS, while retaining your existing data, you only need uninstall the package and re-install the desired one.

If you wish you create a fresh instance of your metadata (e.g. create a new server), with PMS stopped.

  1. Open the Plex share in FileStation
  2. Rename Library to Library.old (or Library.keep if experimenting)
  3. Start PMS
  4. open http://ip.addr.of.syno:32400/web in an in-cognito browser tab
  5. Sign in, see the greeter and start of the setup wizard
  6. If experimenting, I suggest the Friendly name be a ‘test’ name you can easily identify and delete later should you so choose.
38

Followup Comment.

If you’ve deleted the Plex share (or minimally the Library folder), you have a fresh installation.

Unless you’re really well versed in how PMS works, deleting select things under that can make matters worse.

Cleaning Caches is well documented.
Clearing support database files isn’t. We do those on a per-case basis.

39

Ya, I was manually backing up and deleting the entire Plex share each time. Thanks for the advice, I will keep trying.

40

Is the IP addr of your Syno static or dynamic (DHCP).

It’s a really good idea to make it static. (Remote access works WAY better should you try it).

Also, on Windows clients, consider relaxing firewall restrictions on the Syno’s IP. Some firewall’s / anti-virus tools are so tight, they make body parts squeak.

41

IP is static.

42

Syno Firewall enabled or disabled?

43

Currently enabled I have it manually configured. Turning the firewall off didn’t make a difference. *tried in the past too

It just so odd I can access the server for a split second at random when I refresh the browser. *private and regular mode

If this were something like a firewall issue or selinux etc. I would expect it to be either always working or not working at all.

44

Turning the Syno firewall off “for a second” isn’t instantaneous. I have no idea why
 it just isn’t.

How about making the exceptions in it so you never have to screw with it again?

  • TCP: 32400 (for access to the Plex Media Server) [required]

  • UDP: 1900 (for access to the Plex DLNA Server)

  • TCP: 3005 (for controlling Plex Home Theater via Plex Companion)

  • UDP: 5353 (for older Bonjour/Avahi network discovery)

  • TCP: 8324 (for controlling Plex for Roku via Plex Companion)

  • UDP: 32410, 32412, 32413, 32414 (for current GDM network discovery)

  • TCP: 32469 (for access to the Plex DLNA Server)

From this: 32410 -> 21414 are also required for web cients (Plex/web) to find the server (GDM protocol) on the LAN.