Plex plugin no longer starting

  • I rebooted my server and ran into these error messages when trying to start plexmediaserver:



    I noticed that Docker didn't work properly after the reboot, which made me realize that Plex didn't work either. I tried re-installing the plugins, but no success...

  • Just a hint, I installed a fresh OMV 3.0.59 system. When choosing between Plex as docker-image vs plex as omv-plugin I decided to install it via omv-plugin. Maybe it would be easier for you to manage plex via plugin then resolving the docker issues?

  • Just a hint, I installed a fresh OMV 3.0.59 system. When choosing between Plex as docker-image vs plex as omv-plugin I decided to install it via omv-plugin. Maybe it would be easier for you to manage plex via plugin then resolving the docker issues?

    I'm using the OMV-Plex-plugin and not Docker-plex. I meant the OMV-Docker-plugin isn't working either.

  • After reinstalling plexmediaserver-plugin I had the same error with the same error messages. By activating the plugin a folder '/opt/plexcodecs' was created with a symlink 'Codecs' in it. The symlink causes the error. I've deleted this symlink and created a folder called 'Codecs' and changed user and group to 'plex'. After that i could restart plexmediaserver with 'systemctl restart plexmediaserver' and - Voila - everything is running again.


    The reason for this is that the symlink 'Codecs' refers to '<plexmediaserver lib-path>/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/' which is itself a symlink to '/opt/Codecs'. The result is an infinite loop. The wrong symlink in '/opt/plexcodecs/Codecs' was set after activating the openmediavault-plugin. The error is maybe in there.


    Please have in mind as long as this error exist you have to repeat this procedure after each reinstallation.

  • No don't change it. This symlink ist the correct one. Somewhere in the process a symlink ist set, which is the other way around, like


    ln -s "${PLEX_HOME}/Library/Application Support/Plex Media Server/Codecs" "${PLEX_CODECS}/Codecs"


    It looks strange, but it's reproducible on my server by reinstalling the plugin. Last time I installed the plugin was some month ago (I don't know exactly), when I changed to OMV 3.0. At that time the install process of the plugin was ok.

  • The plex package itself must be adding the other symlink. Maybe the plugin could look for the wrong symlink and remove it.

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I did indeed have the same issue just an hour. But not after the first fresh plex-plugin install a couple days ago.
    The install wouldn't use the shared folder with old plex config on as talked about in another thread though so I tried to fix that and plex wouldn't start this time due to the same error as described above.
    Seems the omv plex-plugin creates the /opt/plexcodecs/Codec symlink and I remember it was in some discussions a while back.
    The symlink ${PLEX_HOME}/Library/Application Support/Plex Media Server/Codecs" "${PLEX_CODECS}/Codecs point to /opt/plexcodecs/Codec which points back to itself so I think the quickest fix is to not create the /opt/plexcodecs/Codec symlink and create a folder there instead.
    In that folder I now have a codec.


    As for the database folder it suddenly started using the shared folder after I copied old .../Plug-in Support/Database/ files to the /var/lib/.../Plug-in Support/Database/ folder and restarted the service in the UI. Not sure how this happened but /var/lib/plexmediaserver/ is now empty and the shared folder is growing so all good I think :)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!