Package Details: plex-media-server

Git Clone URL: (read-only, click to copy)
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: 350
Popularity: 0.189999
First Submitted: 2014-10-14 22:11 (UTC)
Last Updated: 2024-07-10 22:33 (UTC)

Latest Comments

1 2 3 4 5 6 .. 107 Next › Last »

techwiz commented on 2024-03-24 16:59 (UTC)

@frank1x I think that error is benin and can be safely ignored. amdgpus.ids should contain a list of AMD GPU PCI ID numbers in the format VVVV:DDDD where V is the Vendor ID and D is the Device ID. You can probably find the file in the mesa or kernel sources and copy it in place (or just make it an empty file) if you want to supress the error.

frank1x commented on 2024-03-24 16:46 (UTC) (edited on 2024-03-24 16:48 (UTC) by frank1x)

I don't understand why I get the following error when transcoding with an AMD card, if it plays without problems, but the error still appears:

mar 24 08:23:58 archlinux plexmediaserver[273701]: /data/jenkins/conan_build/1113263720/conan/.conan/data/libdrm/2.4.115-3/plex/stable/build/73ee780ba6ea3ef381da6e7f229c475bfaf477ca/meson-install/share/libdrm/amdgpu.ids: No such file or directory
mar 24 08:23:59 archlinux plexmediaserver[273701]: /data/jenkins/conan_build/1113263720/conan/.conan/data/libdrm/2.4.115-3/plex/stable/build/73ee780ba6ea3ef381da6e7f229c475bfaf477ca/meson-install/share/libdrm/amdgpu.ids: No such file or directory
mar 24 08:23:59 archlinux plexmediaserver[325043]: /data/jenkins/conan_build/1113263720/conan/.conan/data/libdrm/2.4.115-3/plex/stable/build/73ee780ba6ea3ef381da6e7f229c475bfaf477ca/meson-install/share/libdrm/amdgpu.ids: No such file or directory

I don't use docker, just the installation of "yay -S plex-media-server" But that route seems to be from docker, I don't know.

fryfrog commented on 2024-03-01 16:36 (UTC)

@NoIdea, a good way to know you're doing something wrong in Linux is to run something as root or to set permissions to 777. The top of the plexmediaserver.service file explains the right way to do this. You should have a setup with a user per service, shared group and running w/ umask 002. Your existing folders should be 775 and folders 664.

# Be sure to use `systemctl edit plexmediaserver` to modify this service with an override.conf because
# direct changes will be overwritten by package updates.
# A user per service w/ shared group setup would have an override like:
# [Service]
# Group=sharedgroupname
# UMask=002

NoIdea commented on 2024-03-01 16:29 (UTC)

For those having trouble with seeing mounted drives due to user permissions this is how i fixed it

Made a new directory, below is my example, you can try a new directory in /mnt but i just wanted it separate personally

sudo mkdir /storage/NAS

change the mount point of the drive to /storage/NAS

Then i made permissions read/write for the whole folder, it is just media files so i was ok with these broad permissions. If you used a directory in /mnt be careful not to set anything else in mnt as 777

sudo chown -R 777 /storage

plex saw the folder fine and is able to delete from the filesystem as well, if you dont want to delete from inside plex you can chown 775 instead of 777

techwiz commented on 2024-02-09 01:08 (UTC) (edited on 2024-02-09 01:19 (UTC) by techwiz)

@jmarmstrong1207, negative, this is a configuration problem not a bug.

If it were possible to fix via PKGBUILD, it would be impossible to cover all possible configurations, so you have to use a configuration that will work within the restrictions created by your system. Otherwise, if your software didn't respect your configuration, your software could just do whatever it wanted, which would not be very safe. Unfortunately, the issue in this case is your disk configuration not Plex itself.

edit: alternatively, you can modify your local service file or add a .conf file that sets the user to be your user instead of 'plex' but I would generally advise against running background services connected to the internet under your user as it potentially exposes you to exploits via that service.

jmarmstrong1207 commented on 2024-02-09 01:00 (UTC) (edited on 2024-02-09 01:01 (UTC) by jmarmstrong1207)

@techwiz I wonder, wouldn't it be better if PKGBUILD was modified so this permission problem didn't need to be manually fixed by the end user? e.g. Having the Plex server be run as the user instead of the 'plex' user. External drives are pretty common for a plex server setup.

techwiz commented on 2024-02-08 23:28 (UTC)

@jmarmstrong1207, sounds like a permissions problem. KDE is probably mounting as your user while Plex is running as 'plex' user. Snapd I think might run the app under your user like it would if you launched it manually from cli.

I'd suggest manually mounting the drive and adding a line to /etc/fstab so you can just do 'sudo mount -a' when you plug it in to auto-mount using fstab rules.

jmarmstrong1207 commented on 2024-02-08 23:22 (UTC)

Hey, I have an issue where the server cannot detect external drives mounted at /run/media/$USER/ by KDE. The Snap version of plexmediaserver sees them perfectly fine though. Do you know what the issue could be?

Euler23 commented on 2023-12-21 08:11 (UTC)

Please remove the out-of-date tag on this project. The provided package is the version mentioned in the out-of-date request.

haxis commented on 2023-07-23 20:56 (UTC)

This is what I had to do in order to get plex-media-server working on my machine 1. yay -S plex-media-server 2. created a home directory for user plex because the install did not do that /home/plex 3. created Movies directory in /home/plex/Movies 4. added my movies to /home/plex/Movies 5. chown -R plex:plex Movies 6. usermod -aG plex username - adds your normal username to the plex group (must use your actual username) 7. chmod -R 777 /home/plex/Movies After I did all of that the plex app in my living room picked everything up from my Arch box.