The guide walks you through installing Plex Media Server on Fedora 36 by adding its official repository, installing the package, and enabling the service so you can stream media from any device on your network. It starts with clear prerequisites: root access, a recent kernel, and an updated DNF, reminding you to run sudo dnf update before anything else so you don’t hit dependency hell. After adding the Plex repo and installing plexmediaserver, the tutorial shows how to enable and start the service immediately with systemctl and gives quick troubleshooting tips like checking SELinux or missing codecs that can stop the daemon from running properly. Finally, it explains how to access the web interface on localhost, highlights port considerations for firewalls, and encourages readers to experiment with libraries and remote access once the core setup is complete.

Install Plex Media Server on Fedora 36 Linux: A Step‑by‑Step Guide for Real Users

If you’ve ever tried to set up a media server on Fedora and ended up staring at the terminal until your eyes hurt, this is for you. We’ll walk through adding Plex’s official repository, installing the package, and getting it running so you can stream from your phone or laptop without fighting with SELinux.

Prerequisites & why they matter

• Root access – You’ll need to run a few commands as root (or prefix them with sudo).

Without it, the package manager won’t be able to touch system files.

• A recent kernel and updated DNF – Plex requires libstdc++‑11; on Fedora 36 that comes with the default repo, but if your system is out of sync you’ll hit dependency hell.

Run sudo dnf update before anything else.

Add the official Plex repo

sudo dnf install -y dnf-plugins-core
curl https://downloads.plex.tv/plex-media-server-new/2.12.6.5-ffb8e3c9/plexmediaserver.repo | sudo tee /etc/yum.repos.d/plex.repo

Plex’s own repo holds the latest stable build, which often pulls in newer dependencies that the Fedora repos lag behind on. Skipping this step usually means you’ll end up with an older binary that can’t play 4K streams.

Install the server package

sudo dnf install plexmediaserver

After the installer finishes, DNF will automatically pull in libstdc++-11 and other goodies.

If you see a message about missing glibc‑devel, just ignore it—Plex doesn’t need it for runtime.

Enable and start the service

sudo systemctl enable --now plexmediaserver.service

Enabling makes Plex boot automatically; starting it now lets you test immediately.

You’ll notice a short pause while the daemon pulls its database – that’s normal, but if it hangs forever, check your network connection.

Accessing Plex from a browser

Open http://localhost:32400/web on any machine in your LAN. The first run will prompt you to create an admin account and scan for media libraries.

Tip: If you’re behind a firewall or using VPN, make sure port 32400 is reachable; otherwise Plex won’t discover itself.

Troubleshooting common hiccups

• “Failed to start plexmediaserver.service” – Run journalctl -u plexmediaserver --no-pager and look for “Permission denied”. On recent Fedora releases, SELinux can block the binary. A quick fix:

  sudo setenforce 0   # temporarily disables SELinux

If that solves it, add a proper policy instead of leaving SELinux off.

• Audio/Video not playing in web app – This usually means the ffmpeg binary that Plex ships with is missing codecs for your file. Install rpmfusion-free-release and libdvdcss2 if you’re dealing with commercial media.
• “Could not open library” error after a kernel update – I’ve seen this happen when the kernel bumps from 5.14 to 5.15, breaking the libstdc++ ABI. Re‑installing Plex after the update usually clears it:

  sudo dnf reinstall plexmediaserver

That’s all the heavy lifting. Once you’re up and streaming, the real fun starts: organizing your library, setting up remote access, or adding plugins. If anything feels off, just ping me in the comments – I’ve been through more Plex headaches than I care to admit.