App.plex.tv is unable to connect to “XXXXXX” securely

[ChuckPa]

@Nield

1. The PlexData share method is hardly new. It was released in PMS 1.19.5 for all users. There were 2-3 months of preview / adjustments before & after initial launch. It is an optional method intended for those who do not possess / wish to use the SSH shell method.

2. Please see:

PlexData share for QNAP systems

Introduction We’ve made a change which will make administering PMS easier on QNAP systems without interfering with QNAP’s philosophy and functionality in any way. This functionality is available as of PMS 1.19.5 and higher versions. Primary goals were: Ability to backup and restore your Plex installation (metadata) without use of the command line. Allow easy access to log files and plug-ins when PMS isn’t operating. Improve feedback to you (the admin) about PMS’s operational state a…

3. One thing which QNAP will permit, because it doesn’t know any better and I cannot prevent, is uninstalling PMS from one Volume and then reinstalling on a different volume. In these scenarios, you end up with a fully orphaned (previous) installation.

4. Installing applications on QTS is a ‘batch’ installation. The installation scripting has no way to provide constructive feedback. If I were to check and inform you you’re installing on the wrong volume, there is no means to get you that message.

5. If there is an orphaned installation on the NAS,
   a. It can be found via SSH
   b. It can be removed via SSH

I am working with QNAP to see if there is a way to add an interactive message mechanism to their QDK (developer’s kit)