I installed the latest (Version 1.1.4.2757) Plex server on my Diskstation 614+ --which happens to be the mapped-drive location for my Windows 64-bit Plex server installation--and it is NOT picking up correctly named and located .srt subtitles. Here's what I know:

The old Plex server still works fine finding and playing media files on the Synology NAS box and picks up subtitles fine. I have the Media & Agent settings set to look at Personal Media first for TV shows. The Languages setting is set to show subtitles always, etc. Actually, the latest version for Windows (1.1.4.2757) just picked up the same bug as the Synology of the same version has--you can't access the Languages tab from the local server web interface, so I'm taking it by faith that the settings shown in https://app.plex.tv/web/app#!/settings/server/fc-etc/languages is correct, as that is the only way to access that page for either my Synology server or my Windows 10 server.

I've checked every setting to make sure my Synology Plex installation exactly matches the Windows Plex installation. I'm pretty much out of ideas at this point.

SO--Windows picks up external .srt files fine on the same media library that the Synology can't. Synology does find embedded subtitles, of which I only have a couple.

Thoughts?

Hello,

I'm facing a problem that almost none of my video's seem to play anymore from my NAS (Synology DS216Play).
I keep getting message "This server is not powerful enough to convert video" almost instantly.
I have this when play video's from my Ipone, SamsungTV and Laptop.

Anyone has any idea how to solve this?

Thanks!

Details on my setup below including one example error log:

DS216Play
DSM 6.0.2-8451 Update 1
Plex Server: Version 0.9.16.3
Plex Web: Version 2.5.9

I currently have a DS415+ at home and use with Plex. I need to buy a new NAS for my office anyways and was thinking of using the the 415+ at the office and me taking the DS916+ for home. Is the 916+ a worthy upgrade over the 415+? The passmark CPU score is lower on the 916+ CPU. My main concern is transcoding with Plex. How do you think these 2 compare for that?

Thanks!

I have plex installed for several months, all working perfect.
Then it suddenly stops working: nothing changed at my set up.
When I re-install plex I can get it running but as soon as I access the plex server from a webbrowser of my phone via the app it stops running on the NAS.
i get 0 error messages.

Have done a manual re-install of plex arm version but problem persists.

log shows this
Oct 25, 2016 19:16:23.398 [0x7595f430] INFO - Crash Uploader - Platform: linux-synology-armv7 (3.10.77 (#8451 SMP Wed Aug 17 05:11:05 CST 2016)) ServerUUID: 4137bed2-177d-4b89-bc8c-8937dd0555bb UserId: cobbaut@gmail.com Version: 1.1.4.2757-24ffd60
Oct 25, 2016 19:16:23.397 [0x76936c60] DEBUG - HTTP requesting POST https://crashreport.plexapp.com
Oct 25, 2016 19:16:29.494 [0x76936c60] DEBUG - HTTP 502 response from POST https://crashreport.plexapp.com
Oct 25, 2016 19:16:29.495 [0x76936c60] ERROR - Failed to upload crashdump 73eef943-3c22-44c2-60143a55-544fe8fd: 502

Hello.

I have a problem in my Synology. No problem with Plex, but I'm desperate and I think there are smart people who can help me solve it in the forum.

I have a DS2413+ with 4 drives (4TBx4) and I just add 8 drives (5TBx8) for expand capacity. SHR btrfs. Volume consistency checking was successful and the repair has been running for about 1.5 days. During the stage 'Repairing (Adding disk xx.xx%)' I opened a SSH session and issued 2 commands to try to speed up the repair:

echo 50000 > /proc/sys/dev/raid/speed_limit_min
echo 32768 > /sys/block/md4/md/stripe_cache_size

The repair continued fine after increasing the minimum speed limit from 10000 to 50000. However when I increased the stripe cache size from 1024 (default) to 32768 the SSH session go out, the web DSM interface was unresponsive and the NAS reboot. The DSM is working now but its reporting the volume is crashed.

I found some commands to solve a case like mine.

sfdisk -l

Error: /dev/md2: unrecognised disk label
get disk fail
Error: /dev/md3: unrecognised disk label
get disk fail
Error: /dev/md5: unrecognised disk label
get disk fail
Error: /dev/md6: unrecognised disk label
get disk fail

cd /etc/space
ll

Original 4 drives with data:
-rw-rw-rw-  1 root root  4577 Oct 21 21:13 space_history_20161021_211345.xml

Insert 8 new extra drives:
-rw-rw-rw-  1 root root 12902 Oct 21 21:53 space_history_20161021_215326.xml

Crash drive:
-rw-rw-rw-  1 root root 10274 Oct 23 11:18 space_history_20161023_111845.xml

Restart:
-rw-rw-rw-  1 root root 10274 Oct 23 13:37 space_history_20161023_133740.xml

Fail sdb8 drive:
-rw-rw-rw-  1 root root  9457 Oct 24 03:29 space_history_20161024_032915.xml

cat space_history_20161021_215326.xml

In this critical part I get confused.

mdadm -E /dev/sd[abcdefgh]7
mdadm -E /dev/sd[abcdefgh]7 > /root/sdABCDEFGH7superb.txt

synospace.sh -p /etc/space/space_history_20161021_215326.xml

mdadm -C /dev/md6 -R -l raid5 -n 8 --assume-clean missing missing missing missing missing missing missing missing 
mdadm -C /dev/md2 -R -l raid5 -n 12 --assume-clean missing missing missing missing missing missing missing missing missing missing missing missing 
mdadm -C /dev/md3 -R -l raid5 -n 12 --assume-clean missing missing missing missing missing missing missing missing missing missing missing missing 
mdadm -C /dev/md4 -R -l raid5 -n 12 --assume-clean missing missing missing missing missing missing missing missing missing missing missing missing 
mdadm -C /dev/md5 -R -l raid5 -n 12 --assume-clean missing missing missing missing missing missing missing missing missing missing missing missing

mdadm -C /dev/md4 -R -l raid5 -n 7 --assume-clean /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sdh7 /dev/sdg7 /dev/sde7

So am I right in thinking it might be worth trying an mdadm force-assemble? I think I'm right in saying the outcome of this command won't cause any irreparable damage by itself?

raid path="/dev/md4" uuid="80b6fb38:60fc64ad:8267cc1d:750f50d4" level="raid5" version="1.2"

/dev/sda7:
Array UUID : 80b6fb38:60fc64ad:8267cc1d:750f50d4
Name : DiskStation:4 (local to host DiskStation)

I'm guessing, going by the XML the command would be:

mdadm -C /dev/md4 -R -l raid5 -n 7 --assume-clean /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sdh7 /dev/sdg7 /dev/sde7

mdadm: /dev/sda7 appears to be part of a raid array:
    level=raid5 devices=12 ctime=Sat May 21 04:00:36 2016
mdadm: /dev/sdb7 appears to be part of a raid array:
    level=raid5 devices=12 ctime=Sat May 21 04:00:36 2016
mdadm: /dev/sdc7 appears to be part of a raid array:
    level=raid5 devices=12 ctime=Sat May 21 04:00:36 2016
mdadm: /dev/sdd7 appears to be part of a raid array:
    level=raid5 devices=12 ctime=Sat May 21 04:00:36 2016
mdadm: /dev/sdh7 appears to be part of a raid array:
    level=raid5 devices=12 ctime=Sat May 21 04:00:36 2016
mdadm: /dev/sdg7 appears to be part of a raid array:
    level=raid5 devices=12 ctime=Sat May 21 04:00:36 2016
mdadm: /dev/sde7 appears to be part of a raid array:
    level=raid5 devices=12 ctime=Sat May 21 04:00:36 2016
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md4 started.

mdadm --detail /dev/md4
`/dev/md4:
Version : 1.2
Creation Time : Mon Oct 24 16:05:50 2016
Raid Level : raid5
Array Size : 5860457472 (5588.97 GiB 6001.11 GB)
Used Dev Size : 976742912 (931.49 GiB 1000.18 GB)
Raid Devices : 7
Total Devices : 7
Persistence : Superblock is persistent

Update Time : Mon Oct 24 16:05:50 2016
      State : clean

Active Devices : 7
Working Devices : 7
Failed Devices : 0
Spare Devices : 0

     Layout : left-symmetric
 Chunk Size : 64K

       Name : DiskStation:4  (local to host DiskStation)
       UUID : d8dc80f4:4f116ae7:535e5dff:79aea56d
     Events : 0

Number   Major   Minor   RaidDevice State
   0       8        7        0      active sync   /dev/sda7
   1       8       23        1      active sync   /dev/sdb7
   2       8       39        2      active sync   /dev/sdc7
   3       8       55        3      active sync   /dev/sdd7
   4       8      119        4      active sync   /dev/sdh7
   5       8      103        5      active sync   /dev/sdg7
   6       8       71        6      active sync   /dev/sde7`

pvs

PV         VG     Fmt  Attr PSize PFree
  /dev/md2   vg1000 lvm2 a--  2.72t    0 
  /dev/md3   vg1000 lvm2 a--  2.73t    0 
  /dev/md4   vg1000 lvm2 a--  2.73t    0 
  /dev/md5   vg1000 lvm2 a--  2.73t    0 
  /dev/md6   vg1000 lvm2 a--  6.37t    0

In this critical part I get confused. What disk number should I choose?
PLEASE HELP. n6?

mdadm -CR -amd --assume-clean -n6 -e1.2 -l5 /dev/md4 /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sdh7 /dev/sdg7

mdadm: /dev/sda7 appears to be part of a raid array:
    level=raid5 devices=6 ctime=Mon Oct 24 16:39:26 2016
mdadm: /dev/sdb7 appears to be part of a raid array:
    level=raid5 devices=6 ctime=Mon Oct 24 16:39:26 2016
mdadm: /dev/sdc7 appears to be part of a raid array:
    level=raid5 devices=6 ctime=Mon Oct 24 16:39:26 2016
mdadm: /dev/sdd7 appears to be part of a raid array:
    level=raid5 devices=6 ctime=Mon Oct 24 16:39:26 2016
mdadm: /dev/sdh7 appears to be part of a raid array:
    level=raid5 devices=6 ctime=Mon Oct 24 16:39:26 2016
mdadm: /dev/sdg7 appears to be part of a raid array:
    level=raid5 devices=6 ctime=Mon Oct 24 16:39:26 2016
mdadm: array /dev/md4 started.

pvs

PV         VG     Fmt  Attr PSize PFree
  /dev/md2   vg1000 lvm2 a--  2.72t    0 
  /dev/md3   vg1000 lvm2 a--  2.73t    0 
  /dev/md4   vg1000 lvm2 a--  2.73t    0 
  /dev/md5   vg1000 lvm2 a--  2.73t    0 
  /dev/md6   vg1000 lvm2 a--  6.37t    0

lvm lvscan
inactive '/dev/vg1000/lv' [17.27 TiB] inherit

vgchange -ay
1 logical volume(s) in volume group "vg1000" now active

mount /dev/vg1000/lv /volume1

Trying to repair /dev/md4 mistakenly used the number 7 on /dev/md4 instead of using the number 12.

Wrong:
mdadm -C /dev/md4 -R -l raid5 -n 7 --assume-clean /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sdh7 /dev/sdg7 /dev/sde7

Right:
mdadm -C /dev/md4 -R -l raid5 -n 12 --assume-clean /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sdh7 /dev/sdg7 /dev/sde7

Wrong:
mdadm -CR -amd --assume-clean -n 6 -e1.2 -l5 /dev/md4 /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sdh7 /dev/sdg7

Right?
mdadm -CR -amd --assume-clean -n 12 -e1.2 -l5 /dev/md4 /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sdh7 /dev/sdg7

So now my Volume appears damaged.

raid path="/dev/md2" uuid="0ea2e18c:2819c5dc:07b96b51:cd208f63" > /dev/sda5
raid path="/dev/md3" uuid="4032df32:cee99c16:5ecf7189:04408674" > /dev/sda6
raid path="/dev/md4" uuid="80b6fb38:60fc64ad:8267cc1d:750f50d4" > /dev/sda7
raid path="/dev/md5" uuid="d3f9e63f:9fc77224:7223b3b6:34256bd6" > /dev/sda8
raid path="/dev/md6" uuid="3e3dc3b7:44855efa:ef8d1eeb:e2ac8a03" > /dev/sde9
raid path="/dev/md7" uuid="d8dc80f4:4f116ae7:535e5dff:79aea56d" > /dev/sde7

  /dev/md2   vg1000 lvm2 a--  2.72t    0
  /dev/md3   vg1000 lvm2 a--  2.73t    0
  /dev/md4   vg1000 lvm2 a--  2.73t    0
  /dev/md5   vg1000 lvm2 a--  2.73t    0
  /dev/md6   vg1000 lvm2 a--  6.37t    0 

And the worst is that trying to repair my disk 8 failed, then my RAID5 volume is now degraded, but can still be rebuilt with the right help.

mdadm --detail /dev/md1
/dev/md1:
Version : 0.90
Creation Time : Tue Oct 25 02:59:40 2016
Raid Level : raid1
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 11
Preferred Minor : 1
Persistence : Superblock is persistent

Update Time : Tue Oct 25 03:03:21 2016
      State : active, degraded

Active Devices : 11
Working Devices : 11
Failed Devices : 0
Spare Devices : 0

       UUID : 33c748d2:bbc7472b:3017a5a8:c86610be (local to host DiskStation)
     Events : 0.19

Number   Major   Minor   RaidDevice State
   0       8        2        0      active sync   /dev/sda2
   1       8       18        1      active sync   /dev/sdb2
   2       8       34        2      active sync   /dev/sdc2
   3       8       50        3      active sync   /dev/sdd2
   4       8       66        4      active sync   /dev/sde2
   5       8       82        5      active sync   /dev/sdf2
   6       8       98        6      active sync   /dev/sdg2
   7       8      130        7      active sync   /dev/sdi2
   8       8      146        8      active sync   /dev/sdj2
   9       8      162        9      active sync   /dev/sdk2
  10       8      178       10      active sync   /dev/sdl2
  11       0        0       11      removed

mdadm --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Wed May 18 18:16:26 2016
Raid Level : raid5
Array Size : 10691246016 (10195.97 GiB 10947.84 GB)
Used Dev Size : 971931456 (926.91 GiB 995.26 GB)
Raid Devices : 12
Total Devices : 11
Persistence : Superblock is persistent

Update Time : Tue Oct 25 03:01:24 2016
      State : clean, degraded

Active Devices : 11
Working Devices : 11
Failed Devices : 0
Spare Devices : 0

     Layout : left-symmetric
 Chunk Size : 64K

       Name : DiskStation:2  (local to host DiskStation)
       UUID : 0ea2e18c:2819c5dc:07b96b51:cd208f63
     Events : 37291

Number   Major   Minor   RaidDevice State
   4       8        5        0      active sync   /dev/sda5
   5       8       21        1      active sync   /dev/sdb5
   6       8       37        2      active sync   /dev/sdc5
   7       8       53        3      active sync   /dev/sdd5
  15       8      181        4      active sync   /dev/sdl5
  14       8      165        5      active sync   /dev/sdk5
  13       8      149        6      active sync   /dev/sdj5
  12       8      133        7      active sync   /dev/sdi5
   8       0        0        8      removed
  10       8      101        9      active sync   /dev/sdg5
   9       8       85       10      active sync   /dev/sdf5
   8       8       69       11      active sync   /dev/sde5

mdadm --detail /dev/md3
/dev/md3:
Version : 1.2
Creation Time : Fri May 20 22:37:48 2016
Raid Level : raid5
Array Size : 10744172032 (10246.44 GiB 11002.03 GB)
Used Dev Size : 976742912 (931.49 GiB 1000.18 GB)
Raid Devices : 12
Total Devices : 11
Persistence : Superblock is persistent

Update Time : Tue Oct 25 03:00:21 2016
      State : clean, degraded

Active Devices : 11
Working Devices : 11
Failed Devices : 0
Spare Devices : 0

     Layout : left-symmetric
 Chunk Size : 64K

       Name : DiskStation:3  (local to host DiskStation)
       UUID : 4032df32:cee99c16:5ecf7189:04408674
     Events : 15834

Number   Major   Minor   RaidDevice State
   4       8       54        0      active sync   /dev/sdd6
   6       8        6        1      active sync   /dev/sda6
   5       8       22        2      active sync   /dev/sdb6
   7       8       38        3      active sync   /dev/sdc6
  15       8      182        4      active sync   /dev/sdl6
  14       8      166        5      active sync   /dev/sdk6
  13       8      150        6      active sync   /dev/sdj6
  12       8      134        7      active sync   /dev/sdi6
   8       0        0        8      removed
  10       8      102        9      active sync   /dev/sdg6
   9       8       86       10      active sync   /dev/sdf6
   8       8       70       11      active sync   /dev/sde6

HERE'S THE PROBLEM! Raid Devices : 6 Total Devices : 5

mdadm --detail /dev/md4
/dev/md4:
Version : 1.2
Creation Time : Mon Oct 24 17:08:25 2016
Raid Level : raid5
Array Size : 4883714560 (4657.47 GiB 5000.92 GB)
Used Dev Size : 976742912 (931.49 GiB 1000.18 GB)
Raid Devices : 6
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Tue Oct 25 03:00:21 2016
      State : clean, degraded

Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

     Layout : left-symmetric
 Chunk Size : 64K

       Name : DiskStation:4  (local to host DiskStation)
       UUID : 2d13abf1:788790a8:cbc1d111:c322fe27
     Events : 28

Number   Major   Minor   RaidDevice State
   0       8        7        0      active sync   /dev/sda7
   1       8       23        1      active sync   /dev/sdb7
   2       8       39        2      active sync   /dev/sdc7
   3       8       55        3      active sync   /dev/sdd7
   4       0        0        4      removed
   5       8      103        5      active sync   /dev/sdg7

mdadm --detail /dev/md5
/dev/md5:
Version : 1.2
Creation Time : Sun Jul 10 07:41:06 2016
Raid Level : raid5
Array Size : 10744172032 (10246.44 GiB 11002.03 GB)
Used Dev Size : 976742912 (931.49 GiB 1000.18 GB)
Raid Devices : 12
Total Devices : 11
Persistence : Superblock is persistent

Update Time : Tue Oct 25 03:00:20 2016
      State : clean, degraded

Active Devices : 11
Working Devices : 11
Failed Devices : 0
Spare Devices : 0

     Layout : left-symmetric
 Chunk Size : 64K

       Name : DiskStation:5  (local to host DiskStation)
       UUID : d3f9e63f:9fc77224:7223b3b6:34256bd6
     Events : 9814

Number   Major   Minor   RaidDevice State
   0       8       24        0      active sync   /dev/sdb8
   1       8        8        1      active sync   /dev/sda8
   2       8       40        2      active sync   /dev/sdc8
   3       8       56        3      active sync   /dev/sdd8
  11       8      184        4      active sync   /dev/sdl8
  10       8      168        5      active sync   /dev/sdk8
   9       8      152        6      active sync   /dev/sdj8
   8       8      136        7      active sync   /dev/sdi8
   8       0        0        8      removed
   6       8      104        9      active sync   /dev/sdg8
   5       8       88       10      active sync   /dev/sdf8
   4       8       72       11      active sync   /dev/sde8

AND PERHAPS THERE IS A PROBLEM, BUT HERE I'M NOT SURE!

mdadm --detail /dev/md6
/dev/md6:
Version : 1.2
Creation Time : Fri Oct 21 21:52:52 2016
Raid Level : raid5
Array Size : 6837200384 (6520.46 GiB 7001.29 GB)
Used Dev Size : 976742912 (931.49 GiB 1000.18 GB)
Raid Devices : 8
Total Devices : 7
Persistence : Superblock is persistent

Update Time : Tue Oct 25 03:00:20 2016
      State : clean, degraded

Active Devices : 7
Working Devices : 7
Failed Devices : 0
Spare Devices : 0

     Layout : left-symmetric
 Chunk Size : 64K

       Name : DiskStation:6  (local to host DiskStation)
       UUID : 3e3dc3b7:44855efa:ef8d1eeb:e2ac8a03
     Events : 253

Number   Major   Minor   RaidDevice State
   0       8       73        0      active sync   /dev/sde9
   1       8       89        1      active sync   /dev/sdf9
   2       8      105        2      active sync   /dev/sdg9
   3       0        0        3      removed
   4       8      137        4      active sync   /dev/sdi9
   5       8      153        5      active sync   /dev/sdj9
   6       8      169        6      active sync   /dev/sdk9
   7       8      185        7      active sync   /dev/sdl9

AND PERHAPS THERE IS A PROBLEM, BUT HERE I'M NOT SURE!

mdadm --detail /dev/md7
/dev/md7:
Version : 1.2
Creation Time : Mon Oct 24 16:05:50 2016
Raid Level : raid5
Array Size : 5860457472 (5588.97 GiB 6001.11 GB)
Used Dev Size : 976742912 (931.49 GiB 1000.18 GB)
Raid Devices : 7
Total Devices : 1
Persistence : Superblock is persistent

Update Time : Tue Oct 25 03:00:20 2016
      State : clean, FAILED

Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0

     Layout : left-symmetric
 Chunk Size : 64K

       Name : DiskStation:4  (local to host DiskStation)
       UUID : d8dc80f4:4f116ae7:535e5dff:79aea56d
     Events : 30

Number   Major   Minor   RaidDevice State
   0       0        0        0      removed
   1       0        0        1      removed
   2       0        0        2      removed
   3       0        0        3      removed
   4       0        0        4      removed
   5       0        0        5      removed
   6       8       71        6      active sync   /dev/sde7

Please help to restore the correct values. The service center does not respond Synology and I'm desperate.

Trying to install PlexMediaServer-1.1.4.2757-24ffd60-x86.spk on DS1515+ , Install is stuck at "Processing, Please wait."

I have a DS1515+
I use Synology Package Center to do a Manual Install of Plex packages
Currently running PlexMediaServer-1.1.3.2700-6f64a8d-x86.spk
I stopped the current package.
Then try Manual Install of the package I just downloaded from Synology website, PlexMediaServer-1.1.4.2757-24ffd60-x86.spk
After uploading the file, the Package Center is stuck at a message saying "Processing. Please wait."
I waited overnight, still stuck there.
Multiple reboots of Synology. Multiple re-downloads of package. Same problem.

Anybody else have this problem? Or a solution?

i think someone forgot to sign the new Plex package with its public key.
It is an unknown author.

@ChuckPa

I have moved some movie files on my Synology, from one big folder and separated into smaller folders (1. to make getting at files easier and 2. To allow Plex to create smaller libraries).

I have removed the older library, which pointed to the one big folder, and started adding a new library for each new folder.

However, when adding a new library, I give it a name, then go to specify the new folder to pull the files from. The interface then errors, and says the server is unavailable. It happens over and over again. I have managed to get two new libraries but it has taken all day.

After going onto my Synology dashboard, the service has stopped. I have to manually restart it.

I have rebooted the Synology unit 3 times, and I have uninstalled the Plex install, and reinstalled it fresh from the website.

There's not a great deal else going on with the unit, as I tend to use this one purely for Plex means.

At a loss. Any advice or is this a known issue?

Up until recently we only used our Synology DS416 purely as storage for my library content but Plex was also installed on it.
I was using a mini mac for Sickbeard, Sabnzbd and Couch Potato
This was all working reasonably well but the mac had a few issues and needed to be wiped andas I found that we could run everything on the NAS i decided to migrate everything to there.
It now works pretty well but unless I keep the link for plex media centre as the mac ip address and port then my post processing from sickbeard does not work.
I have tried to put in the NAS ip address and local host but neither solve the issue
Even though the post processing is working I still get an error of

2016-10-26 20:40:26 CP Server Thread-4 :: PLEX: Error while trying to contact Plex Media Server: http error : error 401 : Unauthorized : error Content-Length: 91
Content-Type: text/html
Connection: close
X-Plex-Protocol: 1.0
Cache-Control: no-cache

I would like to get rid of mac so can anyone advise what the entry should be for media centre I would be grateful

The connection between these components works - no problem. I am able to browse through my movies and can see the titles and folders.
But when i choose a movie and try to "play" then happens NOTHING. No error message, just endless waiting ....
Otherwise everything works fine with the Plex-client on my Android-Tablet and the same Synology server.
The Apple TV 4 works also fine withe my other Plex-server on my Macbook.
Any suggestions?
Please help!

I see that the latest version available on plexpass could potentially fix an issue I am experiencing. What is generally the lead time between when a new version is released and when it eventually becomes available for platforms such as the Synology NAS?

Last night when we tried to log in to plex it says the server cannot be found. This has happened before but it came back up within an hour. It has been out for a day now. Does anything know what is happening?

Hello,

I have a Synology DS213j and I'm running the version 0.9.16.3 downloaded from Synology Packadge Center. But, in Plex website the current version is 1.1.4.2757-24ffd60 and when I download this version and try a manual install I have an error saying that the version is not compatible with my Synology.

I tried both ARMv7 and Intel versions, both with the same error.

Is that normal? Is my Synology DS213j too old for the new version?

Thanks

Gustavo

Hey guys,

I'm about to start my first install of Plex on DS916+ as I'm retiring my previous MacMini server setup.

I see that Synology has an older version (0.9.16.3) in app store and I was thinking to start with it unless recommended otherwise. Are there any major fixes in newer PMS versions in regard to Syno NAS-es or can I just go with the older version.

All my players tvOS + iOS should be fine with an older PMS build as far as I know.

i have a problem ever since updating plex it has not been pulling any posters or movie data

i have some new movies but it's not pulling them ? i checked every thing i can but still not downloading it
e.g is https://www.themoviedb.org/movie/127380-finding-dory

i upload the movie to my 2016 folder and still not downloading the cover or anything

before the update it worked fine with all the other movies? but i have about 9 new movies and it's not pulling any data or photos?

any help to get this working again

thanks
Paul

I noticed that PMS is not picking correctly some Albums covers during scan. I made some research and those Albums contains some letters, common in Scandinavian language.
I have tons of Scandinavian music but only recently I noticed the issue.
I use Mp3Tag 2.77 using ID3v2.3 ISO-8859-1 but the same problem occurs with the newest ID3v2.4 UTF-8.

Here an example of local agent log:

2016-06-12 13:50:07,153 (-b6ee4c0) :  INFO (audiohelpers:18) - Error getting file details for /volume1/iTunes Media/Music/Azaghal/Arvet II/01 Vihan Päivä.mp3: 'ascii' codec can't encode character u'\xe4' in position 55: ordinal not in range(128)
2016-06-12 13:50:07,176 (-b6ee4c0) :  CRITICAL (agentkit:1067) - Exception in the update function of agent named 'Local Media Assets (Albums)', called with guid 'local://47365' (most recent call last):
  File "/volume1/@appstore/Plex Media Server/Resources/Plug-ins-2bd156c/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/agentkit.py", line 1065, in _update
    agent.update(obj, media, lang, **kwargs)
  File "/volume1/@appstore/Plex Media Server/Resources/Plug-ins-2bd156c/LocalMedia.bundle/Contents/Code/__init__.py", line 280, in update
    updateAlbum(metadata, media, lang, find_extras, artist_extras=[], extra_type_map=extra_type_map)
  File "/volume1/@appstore/Plex Media Server/Resources/Plug-ins-2bd156c/LocalMedia.bundle/Contents/Code/__init__.py", line 365, in updateAlbum
    if os.path.exists(file):
  File "/data/jenkins/pms-deps-universal-v2/BUILD_TAG/linux-synology-i686/output/pms-depends-linux-synology-i686-release-b66d59b/lib/python2.7/genericpath.py", line 18, in exists
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 55: ordinal not in range(128)

Hi. Since the last update Plex will no longer find cover art for movies. It does download meta-data (such as short description, etc) but no cover or background art. When I tried a refresh on the whole library, I lost all cover art. I tried deleting the PhotoTranscoder folder but that didn't help either.

DSM 6.0.2-8451 Update 1
Plex (Synology) Version 1.1.3.2700

Any suggestions are welcome.

I just got an rs3617xs+ upgraded from the rs 3614xs+. Th sold one had a Xeon 3-1230 the new one had a xeon d-1531. When I go to install whether it is the Plex pass download or the regular one it says it is not compatible and it has been removed from the store even though I usually manual install. Can you please help me with this. I dont really have any other machines that stay on to install it on and need help. This system is very powerful and need it to run smoothy. Please help.

I cant access Plex over WAN, I have my Synology to force HTTPS, I have My valid certificate and I have it setup on my Synology, everything works except Plex, I notice that in the settings Server>>Networks It lets me add the path for the certificate but cant seem to do it right, can someone help me on this ? Can someone teach me how to properly do it ? I use Plex for all my media so its important the security when Plex is on my custom Synology where all my personal files are(What can I say Im a security freak). Thanks in advanced.

Hi, all,

PLEX Server for Synology v1.1.4.2757.
Since update most posters have disappeared.
Adding / replacing them doesn't work.(see below)
"This artwork was uploaded successfully"... but there is only un empty thumb checked on and no picture...
Refresh and update libraries changes nothing.
Other metadatas (textuals) are read correctly.

Maybe it's not only the very latest Plex server update problem but I can't confirm it.

What it is about ?

Configuration:
DS214play,
DSM 6.0.2-8451 Update 2
All movies are .mp4. All metadatas are incorporated into .mp4, even posters. Poster files are also included physically in each movie folder, with the same name as .mp4 files.
Guess I don't need (nor I want) Plex to look for metas anywhere outside my LAN.
Until update everything worked fine.

On another computer (same LAN) I use the old Plex Media Server for Mac (v0.9.12.19... as I wary to upgrade) with a copy of all libraries. Settings are identhical on both Plex Servers. No any problem.

Is it a bug of the new Plex Server for Synology ?
Is it a bug of the new Plex Server on all platforms ?
is it a new strategy towards users who don't want to sign into Plex ?
Maybe Plex doesn't like any more users who don't want Plex to download metas from network ?
;-)

Any advices would be welcome as the behavior of updated Plex is very disappointing.