Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Plex Media Server suddenly not working. Is problem with Plex or Unraid???

Featured Replies

Hi.

 

I've been using PMS for a long time with no problems whatsoever. Yesterday however, after a reboot of my Unraid box Plex has failed to start at all.

 

I am using Unraid 6.0-beta9, which I updated from beta8 yesterday, to see if that fixed things. I am also using PlexMediaServer-0.9.10.1.585.

 

The PMS configuration page in Unraid shows Plex as Stopped, and both the input boxes for the directories are blank. If I try to put anything in the directory boxes, nothing happens when I click 'Apply' If I hit 'Done' and go back into the PMS settings page, the boxes are blank again.

 

The Unraid log after reboot is as follows:

 

/usr/bin/tail -f /var/log/syslog 2>&1

Sep 22 10:34:06 Tower avahi-daemon[1880]: Files changed, reloading.

Sep 22 10:34:06 Tower avahi-daemon[1880]: Service group file /etc/avahi/services/afp.service changed, reloading.

Sep 22 10:34:06 Tower emhttp: shcmd (85): /usr/local/sbin/emhttp_event svcs_restarted

Sep 22 10:34:06 Tower emhttp_event: svcs_restarted

Sep 22 10:34:06 Tower emhttp: shcmd (86): /usr/local/sbin/emhttp_event started

Sep 22 10:34:06 Tower emhttp_event: started

Sep 22 10:34:07 Tower avahi-daemon[1880]: Service "Tower" (/etc/avahi/services/smb.service) successfully established.

Sep 22 10:34:07 Tower avahi-daemon[1880]: Service "Tower-AFP" (/etc/avahi/services/afp.service) successfully established.

Sep 22 10:34:28 Tower su[2243]: Successful su for unraid-plex by root

Sep 22 10:34:28 Tower su[2243]: + ??? root:unraid-plex

Sep 22 10:38:15 Tower su[2311]: Successful su for unraid-plex by root

Sep 22 10:38:15 Tower su[2311]: + ??? root:unraid-plex

 

The last four entries relate to two attempts to start Plex.

 

The monitor attached to the server itself shows the following:

 

Tower login: modprobe: ERROR: could not insert 'kvm_amd' : Operation not supported

mkdir: cannot create directory ** No such file or directory

stat: cannot stat **: No such file or directory

chown: cannot access **: No such file or directory

 

Thanks on advance for any suggestions...

  • Author

Sorry, just realised this was posted in the wrong section! Can someone move it for me please?

I am not an expert but I had a similar problem with Plex and it was a permission problem!! what I did was I Telnet to the server and change the owner to nobody and the group to users manually!! and then Plex started!!  also make sure that in the Plex settings you use the user nobody!!

Will move.  Is Plex in this instance a docker container, a VM, or a Plugin?

  • Author

Thanks for the replies, and thanks also for moving the post jonp!

 

It is running as a plugin. Someone on the Plex forums suggested it might be a startup bug in latest version of PMS, and suggested moving to an older version. I've tried the oldest 64bit version (which is not that old at all  - 3/4 weeks I think), but that made no difference.  I tend to think that afc might be right and that it is a permissions problem. I know next to nothing about Linux permissions and would be very grateful if someone could show me some example commands.

 

What is further puzzling me is that today I did a complete Unraid reinstall. I had been planning to do it for some time, and so did it now in the hopes it might also solve my Plex problem; it did not... When reinstalling it I only copied my pro key plus disk.cfg, ident.cfg, network.cfg and share.cfg. Would any of these files contain information that might affect Plex working?

 

Thanks in advance.

  • 2 weeks later...

Thanks for the replies, and thanks also for moving the post jonp!

 

It is running as a plugin. Someone on the Plex forums suggested it might be a startup bug in latest version of PMS, and suggested moving to an older version. I've tried the oldest 64bit version (which is not that old at all  - 3/4 weeks I think), but that made no difference.  I tend to think that afc might be right and that it is a permissions problem. I know next to nothing about Linux permissions and would be very grateful if someone could show me some example commands.

 

What is further puzzling me is that today I did a complete Unraid reinstall. I had been planning to do it for some time, and so did it now in the hopes it might also solve my Plex problem; it did not... When reinstalling it I only copied my pro key plus disk.cfg, ident.cfg, network.cfg and share.cfg. Would any of these files contain information that might affect Plex working?

 

Thanks in advance.

Can you try running needos docker version of Plex and see if that works?

If you are having pms start up trouble you likely have a permission problem

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.