Remote access not working everytime, depending app (plex media server installed on NAS OMV)

Plex Media Server Remote Access
,
1

Server Version#:

  • Version 1.12.1.4885 (installed on my NAS running on Openmediavault 4)

Player Version#:

  • web client Version 4.8.1
  • mac os app Version 1.3.1.916-1cb2c34d

Hello,

I’m a new user of Plex and I have some issues with the remote access. My Plex server (version 1.12.1.4885) is installed on my NAS which runs on Openmediavault 4.

I have allowed the remote access, but it displays the message that my server is not available outside my network.

37
371484×337 111 KB

But, despite this message when I connect to my Plex account by a web browser (web client Version 4.8.1) outside my network I have access to my libraries and I can read my medias. The server access is flagged as indirect, but still displays that is not available outside my network…

24
24482×138 45 KB

When I try to access by the Mac os application (Version 1.3.1.916-1cb2c34d), it displays an error windows (error code : - 13). The player displays my libraries but it is not able to read any content, each time I try it displays the error window.

26
26930×506 38.1 KB

If any one could help me to find the good settings to have the remote access working well on my different applications, and to understand why the remote status is not consistent with my real access?

Thank you :victory_hand:

2

Your troubles my just be beginning. The minimum version of the server to work with the current versions of clients is 1.13+, current version is 1.17.

If you installed via the OMV plugin, you can’t go past 1.14 without breaking Plex. Docker or standard install via the override.conf file are you options.

3

Ho ok I see, thank you for your answer.

Does it mean that the OMV plugin is not maintained anymore?

And, would you know a good tutorial to run Docker on OMV and then install Plex server by it?

I’m also a newbie on OMV btw :upside_down_face:

4

The plugin is not maintained anymore.

Don’t know how big a hurry or what your Linux skill level is but there is a new installer that should be packaged soon with Plex that might be able to update without destroying your setup.

Otherwise, if you track down where Plex was installed you can follow the directions on how to create an override.conf file and continue on with your current setup.

Lastly there are youtube videos on omv/plex/docker like techno dad life https://www.youtube.com/watch?v=BNfk7ji4oh4 that can get you up and running.

1 Like
5

You are welcome to try the new installer. It has been tested on:

Debian, Ubuntu, Redhad, Fedora, Gentoo, Duvuan, Oracle, Both variants of PMS Docker, and even WSL2 (not supported but might work for you).

If there is anything it doesn’t like, it will complain and show the issue. It will not install and break a system.

PMS 1.17.0.1812 (1709 repackaged to include the new DEB installer) is at the bottom.

1 Like
6

Hello, thank you for your answer.

To be sure about what to try, your solution is to use this new installer to run Plex on Docker? Or to replace the Plex media server previously installed on OMV with the Plex OMV plugin by this new one?

Could you help me more step by step to understand how to use this installer without do mistake?

Thank you

7

The packaging (DEB file) I’ve created is as universal as I can currently make it.

It can:

  1. Install on Linux systems where cat /proc/1/comm returns init
  2. Install on Linux systems where cat /proc/1/comm returns systemd
  3. Upgrade an existing Docker container. (avoids the fuss of recreating a new container)
    (docker returns s6-svscan or tiny)

From the command line, it is the normal dpkg -i filename.deb

As I show in the first post of the thread, you’ll see what errors look like (which make it stop).
and how normal output looks (including final summary)

When it detects it’s running in a docker container, it reports:

Docker detected. Preinstallation validation not required.
8

I tried to install the recommanded packaging 1.17.0.1812 and this is the error I had in my terminal:

dpkg -i plexmediaserver_1.17.0.1812-5ee2fc50a_armhf.deb
Selecting previously unselected package plexmediaserver.
(Reading database ... 48930 files and directories currently installed.)
Preparing to unpack plexmediaserver_1.17.0.1812-5ee2fc50a_armhf.deb ...
PlexMediaServer installer: Pre-installation Validation.  
PlexMediaServer installer: Pre-installation Validation complete.  
Unpacking plexmediaserver (1.17.0.1812-5ee2fc50a) ...
dpkg: error processing archive plexmediaserver_1.17.0.1812-5ee2fc50a_armhf.deb (--install):
 trying to overwrite '/usr/sbin/start_pms', which is also in package plexmediaserver-installer 1.12.1.4885-1046ba85f-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for mime-support (3.60) ...
Errors were encountered while processing:
 plexmediaserver_1.17.0.1812-5ee2fc50a_armhf.deb
9

When I connect to a Plex media player it displays me a message to dowload and install a new version of the server. It recommand me the version 1.17.0.1841. It seems to be a different version from the one you shared me. Do you think I should try this one?

10

What you’re reporting there is something I hadn’t planned on but is fatal.

Is that running as root? it doesn’t look like it

Also, what happens when you remove the old PMS package?

(I know nothing about OMV )

12

Hello,
I removed the old PMS package and the installation of the new one worked :slightly_smiling_face:

But, I meet exactly the sames issues for the remote access that I described in the first message of this topic :confused:

13

Did you allow port 32400 through your firewalls? Both your router and the one on OMV?

15

This topic was automatically closed after 90 days. New replies are no longer allowed.