PlexConnect 0.5-dev & Synology ... no shaed libraries

So, I've used the synology packaged PlexConnect, and upgraded to 0.5-dev through a zip download, and neither work for Shared libraries.

 

I get "No Plex Library Sections Available" as  message

 

Shared libraries works fine from both the PMS installed on the synology and other devices in the house.

 

Shared libraries used to work fine on the synology - not sure what changed.

 

Happy to edit python if it helps to diagnose.

 

ATV 3 - 192.168.1.14

DNS set to the synology, which is running bind with hardcodes for unblock-us & trailers.apple.com

PlexConnect is on 192.168.1.123 - the synology DS412+ with DSM 5.1-5022 update 2

PMS is 0.9.9.10 

Plexconnect dev download as of 8pm GMT on the 23rd Febuary,though same problem with last packaged synology version

 

Settings.cfg

[PlexConnect]
enable_plexgdm = False
ip_pms = 192.168.1.123
port_pms = 32400
enable_dnsserver = False
port_dnsserver = 53
ip_dnsmaster = 192.168.1.123
prevent_atv_update = True
enable_plexconnect_autodetect = False
ip_plexconnect = 192.168.1.123
hosttointercept = trailers.apple.com
port_webserver = 81
enable_webserver_ssl = True
port_ssl = 443
certfile = ../../etc/certificates/trailers.pem
allow_gzip_atv = False
allow_gzip_pmslocal = False
allow_gzip_pmsremote = True
loglevel = High
logpath = ../../var
 
log (144 KB)

>>20:26:10 PlexAPI: Server micro not updated for 2.95545558793 days - skipping.

Is this the missing "shared" server?

It probably is not fully accessible, I think Plex Inc referred to that state as "light published"...

Any chance to reconnect/republish it? I know it's not yours - since it's a shared one - but you should be able to get in contact with the owner, right?

interesting - yes, I can. Maybe a clock is set incorrectly somewhere? the interesting thing is that device is definitely connected. I can play media just fine from my PMS, from plex home theatre on the mac, from plex.tv web player, ios app, etc. I'll ask him to republish and check clocks...

No, shouldn't be affected by any clock on your machines. The number gives the time as seen from plex.tv server.

Other clients (e.g. Plex/Web) are known to do some heavy caching on IP addresses. It is totally possible that they "remember" having seen that shared server a while ago - and as long as it is still somewhat published, it might even answer to direct requests.

So, interesting. I had him reconnect, and also had a friend in another country publish a library for me to test against. The friends library has remained connecting... micro was visible briefly but has now vanished from plexconnect again, but remains ok in home theatre on a mac, and via the web.

>>micro was visible briefly but has now vanished from plexconnect again, but remains ok in home theatre on a mac, and via the web

Yep, it's possible. Please check server availability at plex.tv/servers.

Other clients usually cache a lot more information. Thinking about it, we don't really cache (over PlexConnect restarts) anything in that regard.