Synology Plex Server not showing server link to setup new server

Plex Media Server NAS & Devices
1

I have a Synology DS1514+. Plex Server was previously setup on this and I had to restore it to factory defaults. I am now trying to start over. I setup the NAS, Setup the Drive, and installed plex server, and configured router. The server installs and runs fine. I click on the local link only and login using my plex account. It does not find my server nor does it offer the server tab under settings. I am unable to setup the server.

The NAS and the computer I am connecting to plex with are on the same network. I have install/uninstalled (removing the server app, files, and plex user account) a number of times without luck.

I have attached the log file.

2

Your log shows two adapters are plugged in but only one defined.

Feb 17, 2017 12:33:05.986 [0xf3f11780] DEBUG - Network interfaces:
Feb 17, 2017 12:33:05.986 [0xf3f11780] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Feb 17, 2017 12:33:05.986 [0xf3f11780] DEBUG -  * 3 eth0 (172.10.1.114) (loopback: 0)
Feb 17, 2017 12:33:05.986 [0xf3f11780] DEBUG -  * 4 eth1 (169.254.170.60) (loopback: 0)
Feb 17, 2017 12:33:05.986 [0xf3f11780] DEBUG - Creating NetworkServices singleton.

Is eth0 marked as the default gateway and does it point to a valid DNS server?

Your log shows you’re getting DNS lookup errors. Here is one example.

Feb 17, 2017 12:33:44.593 [0xea735b40] ERROR - Error issuing curl_easy_perform(handle): 6
Feb 17, 2017 12:33:44.593 [0xea735b40] ERROR - HTTP -6 downloading url https://meta.plex.tv/t/theater?language=en&subtitleLanguage=en&redband=0
Feb 17, 2017 12:33:44.593 [0xea735b40] ERROR - IVA: Error downloading trailers for source 1.
Feb 17, 2017 12:33:49.402 [0xec447b40] ERROR - Error issuing curl_easy_perform(handle): 6
Feb 17, 2017 12:34:04.620 [0xea735b40] ERROR - Error issuing curl_easy_perform(handle): 6

Once you have resolved this, finished associating it with your Plex account (which your browser is), it should populate.

If you are using a firewall, please read this article to make sure you have the appropriate ports open.

3

Thanks for the quick response.

There is only LAN1 is physically connected. I updated a new log file, which I think will show the DNS issue not there any longer. When I connect to Plex via the browser, I am not asked to setup my server or provided the server section within the setting section.

4

Forgot - I did verify the firewall ports were open.

5

May I have the entire set of log files please? This doesn’t let me look at everything I need to.

6

Logs attached

7

i hope the logs help as I have yet to get this working.

8

What’s happening with eth0? Bad cable?

First it’s up, then down, then up again. It’s driving PMS crazy.

Feb 17, 2017 14:02:20.919 [0xef111b40] DEBUG - Network change.
Feb 17, 2017 14:02:20.920 [0xef111b40] DEBUG - NetworkInterface: Notified of network changed (force=0)
Feb 17, 2017 14:02:20.921 [0xef111b40] DEBUG - Network interfaces:
Feb 17, 2017 14:02:20.921 [0xef111b40] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Feb 17, 2017 14:02:20.921 [0xef111b40] DEBUG -  * 4 eth1 (169.254.170.60) (loopback: 0)
Feb 17, 2017 14:02:20.921 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.921 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.921 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.921 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.922 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.930 [0xef111b40] DEBUG - NetworkInterface: received Netlink message len=80, type=RTM_DELADDR, flags=0x0
Feb 17, 2017 14:02:20.931 [0xef111b40] DEBUG - NetworkInterface: Netlink address message family=2, index=3, flags=0x80
Feb 17, 2017 14:02:20.931 [0xef111b40] DEBUG - Network change.
Feb 17, 2017 14:02:20.931 [0xef111b40] DEBUG - NetworkInterface: Notified of network changed (force=0)
Feb 17, 2017 14:02:20.932 [0xef111b40] DEBUG - Network interfaces:
Feb 17, 2017 14:02:20.932 [0xef111b40] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Feb 17, 2017 14:02:20.932 [0xef111b40] DEBUG -  * 3 eth0 (172.10.1.114) (loopback: 0)
Feb 17, 2017 14:02:20.932 [0xef111b40] DEBUG -  * 4 eth1 (169.254.170.60) (loopback: 0)
Feb 17, 2017 14:02:20.932 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.932 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.932 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.933 [0xf0fffb40] DEBUG - Network change for advertiser.
Feb 17, 2017 14:02:20.933 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.933 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.933 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.933 [0xf0fffb40] ERROR - Error broadcasting message: send_to: Network is unreachable
Feb 17, 2017 14:02:20.933 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.933 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.933 [0xf0fffb40] DEBUG - Network change for advertiser.
Feb 17, 2017 14:02:20.933 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.933 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.934 [0xef111b40] DEBUG - NetworkService: Got notification of changed network (first change: 0)
Feb 17, 2017 14:02:20.934 [0xf0fffb40] ERROR - Error broadcasting message: send_to: Network is unreachable
Feb 17, 2017 14:02:20.934 [0xef111b40] DEBUG - NetworkService: Dispatch network change after two second delay.
Feb 17, 2017 14:02:20.934 [0xf0fffb40] DEBUG - Network change for advertiser.
Feb 17, 2017 14:02:20.934 [0xef111b40] DEBUG - NetworkInterface: received Netlink message len=80, type=RTM_GETADDR, flags=0x0
Feb 17, 2017 14:02:20.934 [0xf0fffb40] DEBUG - NetworkService: Network change for browser (polled=0), closing 3 browse sockets.
Feb 17, 2017 14:02:20.934 [0xef111b40] DEBUG - NetworkInterface: Netlink address message family=2, index=3, flags=0x80
Feb 17, 2017 14:02:20.934 [0xef111b40] DEBUG - Network change.
Feb 17, 2017 14:02:20.934 [0xf0fffb40] DEBUG - NetworkService: Setting up multicast listener on 0.0.0.0:32413 (outbound: 0)
Feb 17, 2017 14:02:20.934 [0xef111b40] DEBUG - NetworkInterface: Notified of network changed (force=0)
Feb 17, 2017 14:02:20.935 [0xf0fffb40] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device
Feb 17, 2017 14:02:20.935 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 127.0.0.1 on broadcast address 127.255.255.255 (index: 0)
Feb 17, 2017 14:02:20.935 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 169.254.170.60 on broadcast address 169.254.255.255 (index: 1)
Feb 17, 2017 14:02:20.935 [0xf0fffb40] DEBUG - NetworkService: Network change for browser (polled=1), closing 3 browse sockets.
Feb 17, 2017 14:02:20.936 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 127.0.0.1 on broadcast address 127.255.255.255 (index: 0)
Feb 17, 2017 14:02:20.936 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 169.254.170.60 on broadcast address 169.254.255.255 (index: 1)
Feb 17, 2017 14:02:20.936 [0xf0fffb40] DEBUG - NetworkService: Network change for browser (polled=0), closing 2 browse sockets.
Feb 17, 2017 14:02:20.937 [0xf0fffb40] DEBUG - NetworkService: Setting up multicast listener on 0.0.0.0:1901 (outbound: 0)
Feb 17, 2017 14:02:20.937 [0xf0fffb40] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device
Feb 17, 2017 14:02:20.937 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 169.254.170.60 on broadcast address 239.255.255.250 (index: 0)
Feb 17, 2017 14:02:20.938 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:20.938 [0xef111b40] DEBUG - Network change notification but nothing changed.
Feb 17, 2017 14:02:20.938 [0xef111b40] DEBUG - NetworkInterface: received Netlink message len=80, type=RTM_DELADDR, flags=0x0
Feb 17, 2017 14:02:20.938 [0xef111b40] DEBUG - NetworkInterface: Netlink address message family=2, index=3, flags=0x80
Feb 17, 2017 14:02:20.939 [0xef111b40] DEBUG - Network change.
Feb 17, 2017 14:02:20.939 [0xef111b40] DEBUG - NetworkInterface: Notified of network changed (force=0)
Feb 17, 2017 14:02:20.939 [0xef111b40] DEBUG - Network change notification but nothing changed.
Feb 17, 2017 14:02:21.039 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.039 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.140 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.140 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.242 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.242 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.344 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.344 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.445 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.445 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.546 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.546 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.647 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.647 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.749 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.749 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.850 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:21.850 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:21.951 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
Feb 17, 2017 14:02:22.934 [0xf0fffb40] DEBUG - Network change for advertiser.
Feb 17, 2017 14:02:22.934 [0xf0fffb40] DEBUG - Network change for advertiser.
Feb 17, 2017 14:02:22.934 [0xf0fffb40] DEBUG - Network change for advertiser.
Feb 17, 2017 14:02:22.935 [0xf0fffb40] DEBUG - NetworkService: Network change for browser (polled=0), closing 2 browse sockets.
Feb 17, 2017 14:02:22.935 [0xf0fffb40] DEBUG - NetworkService: Setting up multicast listener on 0.0.0.0:32413 (outbound: 0)
Feb 17, 2017 14:02:22.935 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 127.0.0.1 on broadcast address 127.255.255.255 (index: 0)
Feb 17, 2017 14:02:22.935 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 172.10.1.114 on broadcast address 172.10.1.255 (index: 1)
Feb 17, 2017 14:02:22.936 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 169.254.170.60 on broadcast address 169.254.255.255 (index: 2)
Feb 17, 2017 14:02:22.936 [0xf0fffb40] DEBUG - NetworkService: Network change for browser (polled=1), closing 2 browse sockets.
Feb 17, 2017 14:02:22.936 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 127.0.0.1 on broadcast address 127.255.255.255 (index: 0)
Feb 17, 2017 14:02:22.938 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 172.10.1.114 on broadcast address 172.10.1.255 (index: 1)
Feb 17, 2017 14:02:22.938 [0xf0fffb40] DEBUG - NetworkService: Browsing on interface 169.254.170.60 on broadcast address 169.254.255.255 (index: 2)
Feb 17, 2017 14:02:22.938 [0xf0fffb40] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Feb 17, 2017 14:02:23.039 [0xf0fffb40] INFO - Network Service: Abandoning browse socket, it was closed.
9

This is so frustrating. I worked just fine until I had to reset my synology. Then it didn’t work after resetting and reinstaling Plex. Same network, no changes other than that. Although, I have been able to connect via the IP to plex and the NAS OS, I did change the network cable. I am able to connect to the plex via the IP address and port 32400. It does not show me the server to setup. If I go to plex on my iPad, I see the plex server on this synology device listed as Not Authorized. How come I see it listed on the ipad and not when I connected via the local IP in the web browser?

10

Ok… Now we’ve got a stable condition to work with.

Reinstalling DSM doesn’t touch PMS’s data (your Library)
Reinstalling the Plex package doesn’t touch it either (unless you hand-delete the Plex share)

What I would like to do is safely move your existing Library off to the side so nothing happens to it.
While it’s off to the side, we’ll ‘setup’ a new server but not actually add any media to it.
Once you’ve got all the connectivity the way you need / want it, we’ll put it back together.

  1. Stop PMS
  2. Open FileStation and navigate to the Plex share
  3. (If you can’t see the Plex share in FileStation, we can fix that with these steps:
    3a. Enable SSH (control panel - terminal)
    3b. ssh -l admin ip.of.syno.nas and sign in using the admin password
    3c. sudo sh
    3d. synoshare --setbrowse Plex 1
    3e. Go back to FileStation and ‘refresh’. Confirm the Plex share is now visible.
    3f. Exit the ssh session.
  4. Rename Library to Library.safe
  5. Start PMS
  6. Connect to the IP of your Syno http://ip.of.syno.nas:32400/web
  7. Sign in with your Synology username and password and begin setup
  8. When it offers to create libraries, skip it
  9. Continue forward until you reach the Dashboard.

10 .Now the tokens are aligned
11. Perform any network configurations you need / want to establish connectivity as you want it. (Settings - Server - Remote Access)
12. When satisfied, Stop PMS
13. Return to FileStation
14. (be careful as you do this to avoid having to repeat the above setup steps)
15. Navigate down in Plex share Library -> Plex Media Server.
16. Copy file Preferences.xml and overwrite Library.safe/Plex Media Server/Preferences.xml This transfers the new tokens to your existing
17. Navigate back to the top of the Plex share
18. Rename Library to Library.temp
19. Rename Library.safe back to Library
20. Start PMS

11

Hi,
I followed your instructions. I reinstalled DSM and reinstalled Plex. There is no media on the unit at this time, so we are OK on that front. I stopped plex, had to assign the user permission to view the Plex directory, and renamed Library as stated. I started plex and navigated to the URL. Logged into my plex account and it did not ask me to create a library or even state is found my plex server. I did look at the directory on the NAS and it did recreate the Library file, but that is all. It still can not see the plex server but can access the plex portal via the NAS URL:32400/web.

12

Since there’s no media loaded in the library, let’s just use the BFH approach :slight_smile:

  1. Uninstall PMS
  2. Delete the Plex share. If you can’t see the Plex share in FileStation, unable it with:
    2a. Enable SSH
    2b. ssh -l admin ip.of.syno.box and use the admin password
    2c. sudo sh and elevate to the root (admin password)
    2d. synoshare --setbrowse Plex 1 (this is what makes it visible)
    2e. exit (from the root shell)
    2f. exit (from the ssh session)
  3. Return to FileStation and delete the Plex share
  4. Now install PMS again. This will be a fresh/cold install. It will create everything new. Do not start PMS after package installation
  5. Make sure share permissions (to your media) is all set as you like
  6. Now start PMS
  7. Open http://ip.of.syno.box:32400/web and start first-time wizard setup
  8. Add one Library only during the setup wizard
  9. Arrive at the Dashboard
  10. Customize any settings (Settings - Server - …) as you wish
  11. Test drive this for a bit before adding more libraries
13

It did not work. For what ever reason, it seems as if the Plex Server is not recognizing that my workstation is on the same network and will not offer me the ability to setup the server. I ended up having to connect directly to the Synology. Once I did a direct connection, I was able to setup the Plex Server as expected. After setting up the server, I then joined the Synology NAS back to my network and all worked as it should.

Thanks again,
Rob

14

Rob,
Please take a look at the Control Panel -> Network. See which adapter is selected as the ‘Default Gateway’.

Because of how Synology does adapter aliasing (layer 2 switching) in the box, any adapter can actually ‘attach’ to any of the default IP addresses (even if undefined). When you connected directly, the internal routing table adjusted dynamically and ‘matched’. Yes, it’s screwy but that’s how it works.

15

@ChuckPA said:
Since there’s no media loaded in the library, let’s just use the BFH approach :slight_smile:

  1. Uninstall PMS
  2. Delete the Plex share. If you can’t see the Plex share in FileStation, unable it with:
    2a. Enable SSH
    2b. ssh -l admin ip.of.syno.box and use the admin password
    2c. sudo sh and elevate to the root (admin password)
    2d. synoshare --setbrowse Plex 1 (this is what makes it visible)
    2e. exit (from the root shell)
    2f. exit (from the ssh session)
  3. Return to FileStation and delete the Plex share
  4. Now install PMS again. This will be a fresh/cold install. It will create everything new. Do not start PMS after package installation
  5. Make sure share permissions (to your media) is all set as you like
  6. Now start PMS
  7. Open http://ip.of.syno.box:32400/web and start first-time wizard setup
  8. Add one Library only during the setup wizard
  9. Arrive at the Dashboard
  10. Customize any settings (Settings - Server - …) as you wish
  11. Test drive this for a bit before adding more libraries

Would this be the best approach if I am trying to migrate my Plex server media and role/responsibilities from one NAS to another?
Dataset itself has been migrated from an ASUSTOR to a Synology DS1815+. I followed the “Move an install” procedures but I think I have fouled something up along the lines. Does Plex have an issue if the quad NIC ( or any other multi NIC ) is bonded or teamed? If I stop the Plex service on the Syno and launch it from my Old NAS location it populates two servers in the settings and devices listing. Would love any tips if you might have them.

16

The data we need migrated is all that below the Plex Media Server directory common to every installation. Each NAS vendor puts it in a different location but it’s always the same structure and contents from here down. Since you’re getting the name replicated, I think you did it correctly and you’re getting two instances of the same server because you cloned the first onto the second NAS. One way around this is to rename the first server after cloning it so you can distinguish it from the clone.

The easiest and safest way to clone is when you approach it from the Linux level. tar the data on the old system using path relative addressing and untar it on the new system in the correct position.

On desktop Linux, the default location is in /var/lib/plexmediaserver with ./Library beginning there.
On Synology, the default location is in /volume1/Plex with ./Library beginning there. See the symmetry ?

Although Desktop Linux -> Synology would require cleanup, it would be as simple as:

sudo sh
cd /var/lib/plexmediaserver
cd tar cf /home/chuck/PlexLibrary.tar ./Library

Now I’d copy the .tar file to the Plex share on the Syno and:

sudo -su root
cd /volume1/Plex
mv Library Library.unused
tar xf /volume1/Plex/PlexLibrary.tar

I’ve detailed how to do this in the Linux Tips section. You’ll need to account for the plex user on Synology because I don’t run as root on Syno.
http://forums.plex.tv/discussion/293814/back-up-restore-clone-your-pms-metadata I think you’ve already accounted for this.

Regarding the network teaming

Bonding the adapters gives you the most aggregate throughput and presents the simplest interface (one IP) to PMS.
It gives you, because of how LACP works, multiple ‘lanes’ of traffic at the full wire speed of each wire. Think of a multi-lane highway with the speed limit set. You don’t get the sum of all (4Gbits/sec to a single point) but instead get 4x 1Gbit links sharing the same IP.
For a media server, that’s great. You can have 4 independent gigabit feeds going anywhere you want and that’s a lot of video streaming.

Does this help?

17

It kind of helps.
I’m currently at step 7 of the reinstall process but no servers are being found by plex web.
I also split the network addpaterson the DS1815+ to 2 bonds of 2 1gb. As you state there should be no issues running the bind at 4x1gb, so i will revert to that config. I have ensured that the correct permission are allocated for the plex user on the plex folders. I migrated the actual media data (video files) simply using the native mount of remote fodler between the two NAS devices. Should I have instead compressed and migrated the actual plex media library instead?

The final intent is to move all services and roles to the new DS1815 and remove the Asustor device from my home network. The asustor seems to have similar admin interfacing to the syno device.

Current status:
Asustor - Plex Server powered off from the app management
Plex on this location was signed out of before stoppage of service

Synology - Plex installed and service powered on
Signed in to plex web but no servers are populating.

18

Belay my last about not being able to find a server. I was trying to do that while connected to Synology QuickConnect. Server has been found added only one show library, ensured it was matching media with metadata properly and am now propagating the remaining media files.