Package Details: plex-media-server

Git Clone URL: (read-only)
Package Base: plex-media-server
Description: The back-end media server component of Plex.
Upstream URL:
Keywords: DLNA
Licenses: custom
Conflicts: plex-media-server-plexpass
Submitter: alucryd
Maintainer: fryfrog (tixetsal)
Last Packager: fryfrog
Votes: 314
Popularity: 0.72
First Submitted: 2014-10-14 22:11
Last Updated: 2019-11-28 15:28

Pinned Comments

fryfrog commented on 2019-03-22 16:55

Flagging Out of Date:

This package is the non-plexpass package, it gets updated less frequently. Be sure to flag the right package. You can find the plexpass version at

Current Issues:

The plex user's home directory needs to be changed, but likely can't if Plex Media Server was running when you upgrade. The package will tell you what to do, but of course that is easy to miss. The soluiton is to run sudo systemctl stop plexmediaserver ; sudo usermod -d /usr/lib/plexmediaserver plex ; sudo systemctl start plexmediaserver.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

user98170 commented on 2019-11-21 04:48

Pacman works just fine for everything else. Able to install, remove and upgrade everything except Plex. That's why I figured it was specific to this package.

techwiz commented on 2019-11-21 04:44

@user98170, Uhh... Well I would say that you probably want to reinstall pacman and/or base-devel. That error seems to be related to your system not this package. Maybe try the forums for more help.

user98170 commented on 2019-11-21 04:33

Been experiencing an issue for a few days now. Don't know what to do. Keep getting:

==> ERROR: Unknown download protocol: https -> Downloading plexmediaserver- /usr/share/makepkg/source/ line 72: Aborting...: command not found ==> ERROR: Failure while downloading Aborting...

techwiz commented on 2019-11-20 18:23

@j1simon, yes you can modify the PKGBUILD to meet your needs and maintain your patched repo yourself. As fryfrog mentioned, the change is trivial and the maintenance would be equally trivial for you. Asking the community, which agreed on “The Arch Way,” to bend over for your request is of course going to be met with resistance. Sorry for the inconvenience, but this is how we’ve all agreed things should be.

j1simon commented on 2019-11-20 17:32

I don't agree again. There are a way to solve this but someone decides doesn't use it because ¿the Arch way?

fryfrog commented on 2019-11-20 17:29

@j1simon: It doesn't matter if you agree or not, the Arch way is to not start or restart daemons and so that is how all the packages I manage operate. I personally would love if Arch came up w/ a way for packages to notify that they need restarting, so that at the end of a big upgrade, a user could be presented w/ all the services that might need restarting... but that doesn't exist.

You are of course welcome to take this AUR package and modify it how you'd like it to work. Keeping it up to date is as easy as changing a couple version fields and updating the checksums.

j1simon commented on 2019-11-20 17:24

I don't agree. Every time Plex is upgraded, I have to restart Plex service manually because the service is in a state of error after upgrade. That should never happen if the update was correct.
For that is the .install file and this package uses it. In the post_upgrade() section it would be necessary to check if the service is started and if that is the case to restart it.

techwiz commented on 2019-11-20 14:41

@j1simon refer to this reddit post from 2013 that does a good job of explaining why Arch packages don’t start or stop services:

The gist is that it’s up to the user to configure and run their software, and as such many packages don’t ship with a default config that makes sense to run out of the box. Since we don’t know if the user wants to start the service right away or if the default config is good enough, pacman does not manage services, it just installs them.

j1simon commented on 2019-11-20 10:10

Why is not the service restarted when upgraded?

techwiz commented on 2019-10-31 02:37

@ectospasm: “ tl;dr, my ~/.cache/pikaur directory was a symlink to an NFS share, and for whatever reason this location was causing the bsdtar unpacking of the rpm to have permissions of 750, not 755.”

This makes sense as an NFS mount is not a local file system. Your NFS server is (correctly) defining your permissions as the file system is local to the server not your machine. Glad you figured out your issue.