Install WatchMyMedia on Fedora
One package runs the server as a system service. It starts with the computer, and new versions come with the system's other updates. Everything here is typed in a terminal.
You'll need
- Fedora 45 or 44 on an Intel or AMD (x86_64) or ARM (aarch64) processor. Other releases, and systems built on Fedora, aren't tested.
-
An account that can use
sudo. - Your movies and TV shows in folders on that computer, or on a drive or share it mounts, with movies and TV shows in separate folders.
On Debian or Ubuntu, install the Debian and Ubuntu package. On another distribution or a NAS, run it with Docker. On Unraid, install it from Community Applications.
-
Download and install the package
These two lines fetch the newest package for an Intel or AMD processor and install it:
curl -fLo watchmymedia.rpm "https://downloads.watchmy.media/rpm/latest?arch=amd64" sudo dnf install ./watchmymedia.rpmOn an ARM computer, change
amd64toarm64in the first line.uname -mprintsaarch64on ARM andx86_64on Intel or AMD. The same files are on the Download page, with their sizes.dnf says skipped OpenPGP checks for 1 package from repository: @commandline. It doesn't check the signature of a file you hand it; Check the key and the file has the lines that do.
The package holds the server and the FFmpeg it converts video with. dnf adds packages beside it: the libraries a GPU needs, about 25 of them on a system with no desktop, and
acl, for a command in step 3. The install then does three things:- It makes a
watchmymediauser, and a service of the same name that runs the server as that user, now and each time the computer starts. - It adds WatchMyMedia's repository to dnf, so new versions come with the system's updates.
- It prints the address to open.
To have dnf fetch the package from that repository instead of a file, add the repository first.
- It makes a
-
Open it in a browser
On the computer itself, open
http://localhost:27587. From another computer or a phone on the same home network, use the address the install printed, such ashttp://192.168.1.20:27587.hostname -Iprints the computer's addresses again.Setup opens: create your account, which becomes the admin, and add a free TMDB key for posters. Set up your server goes through every step. If another device can't open the address, a firewall may be in the way: that is step 4.
-
Let the server read your folders
The server runs as its own
watchmymediauser, not as you, so it reads only what that user may read. A folder everyone can read, as folders under/srvor/mntoften are, works as it is. A folder inside your home folder doesn't: Fedora closes home folders to other users.When you add a folder the server can't read, setup and Settings › Libraries say so and give the command that lets it in. For a folder called Movies in the home folder of a user called alex, it is:
sudo setfacl -R -m u:watchmymedia:rX /home/alex/MoviesThe folders above it have to let that user through as well. For a home folder:
sudo setfacl -m u:watchmymedia:x /home/alexThat lets the server pass through your home folder to Movies. It still can't list or read anything else there, or change anything in Movies. Then check the folder again in the browser. Drives, shares and recordings, further down, has the other cases.
Fedora also runs SELinux, which the package leaves as it is. This package has not yet been run on a Fedora system with SELinux enforcing, so if a folder still can't be read after these commands, this entry says how to see whether SELinux refused it.
-
Open the firewall
The package never changes the firewall. Fedora Workstation's lets the server's port through as it comes. Fedora Server's doesn't, so let the server through it:
sudo firewall-cmd --permanent --add-service=watchmymedia --add-service=mdns sudo firewall-cmd --reloadwatchmymediais TCP port 27587, the only port browsers and the apps connect to.mdnslets the apps find the server by name on your network; without it, type the server's address into the app.
You're done when systemctl status watchmymedia says active (running) and the browser opens your library.
Add the repository first
Installing the file is enough, because the package adds the repository itself. The other way round also works: add the repository and its key, then let dnf fetch the package, which it checks against the key.
sudo curl -fLo /etc/pki/rpm-gpg/RPM-GPG-KEY-watchmymedia https://downloads.watchmy.media/rpm/RPM-GPG-KEY-watchmymedia
sudo curl -fLo /etc/yum.repos.d/watchmymedia.repo https://downloads.watchmy.media/rpm/watchmymedia.repo
sudo dnf install watchmymedia
Check the key and the file
The key belongs to Eldwick Software, which makes WatchMyMedia. Whenever dnf asks whether to import it, compare the fingerprint it shows with this one before you answer yes:
3C3CE93DA59EBE83C4B3ED24CB959CFB56BCDBB9
To check a package file you downloaded before installing it, fetch the key, look at it, give it to rpm, and ask rpm about the file:
curl -fLO https://downloads.watchmy.media/rpm/RPM-GPG-KEY-watchmymedia
gpg --show-keys RPM-GPG-KEY-watchmymedia
sudo rpm --import RPM-GPG-KEY-watchmymedia
rpm -K watchmymedia.rpm
The second line prints the fingerprint above. The last should answer digests signatures OK; anything else means the file is not the one WatchMyMedia published.
Stop using the repository
Change enabled=1 to enabled=0 in /etc/yum.repos.d/watchmymedia.repo. Updates to
WatchMyMedia keep that change, and you then update by installing a newer file.
Drives, shares and recordings
Files you add later
The first command in step 3 covers what is in the folder now. Files added later usually open to everyone and need nothing more. If yours don't, give the folder a default as well, which every new file and folder inside it takes:
sudo setfacl -R -d -m u:watchmymedia:rX /home/alex/Movies
Where the server writes
Reading is enough to play a library. The server writes only where it records live TV, where you delete a title from the web
app, and where it saves a subtitle or a trailer beside a video. For those folders, use rwX in place of
rX, with the default too:
sudo setfacl -R -m u:watchmymedia:rwX /srv/media/Recordings
sudo setfacl -R -d -m u:watchmymedia:rwX /srv/media/Recordings
A folder several accounts share
For a media folder outside anyone's home folder, a group does the same job. This makes one called media, for the server and for alex:
sudo groupadd media
sudo usermod -aG media watchmymedia
sudo usermod -aG media alex
sudo chgrp -R media /srv/media
sudo chmod -R g+rwX /srv/media
sudo find /srv/media -type d -exec chmod g+s {} +
sudo systemctl restart watchmymedia
The find line makes new files take the folder's group. The restart puts the server in its new group; alex signs
out and in again for theirs.
A drive
A drive the desktop mounts when you plug it in, under /run/media and your user name, is yours alone. The
server can't read it, and it isn't there until you sign in. For a library, mount the drive when the computer starts, with a
line in /etc/fstab. lsblk -f shows each drive's UUID and file system. For a drive with a Linux file
system, such as ext4:
UUID=… /mnt/media ext4 defaults,nofail 0 2
Then give its folders to the server as above. A drive formatted exFAT or NTFS keeps no Linux permissions, so the line sets them for the whole drive. This one lets everyone read it:
UUID=… /mnt/media exfat defaults,nofail,umask=022 0 0
Add uid= and the number id -u watchmymedia prints if the server should write there too. An NTFS
drive takes the same options, with the type your system uses for NTFS (ntfs3, or ntfs-3g from the
package of that name). Make the folder first (sudo mkdir /mnt/media), and after changing the file run
sudo systemctl daemon-reload and sudo mount -a.
A share on a NAS or another computer
Mount it when the computer starts too, not from the file manager. For a Windows (SMB) share, install
cifs-utils and add a line like this, where the credentials file holds a username= line and a
password= line and only root can read it:
//nas.local/Movies /mnt/movies cifs credentials=/etc/nas-credentials,uid=watchmymedia,gid=watchmymedia,nofail,_netdev 0 0
For an NFS share, install nfs-utils. The NAS decides who may read an NFS share, so export it readable by everyone,
or by the user number id -u watchmymedia prints:
nas.local:/volume1/Movies /mnt/movies nfs defaults,nofail,_netdev 0 0
Convert video on the GPU
Without a GPU the server converts video on the processor, which works but is slower. With one, the package's FFmpeg reaches
it through the system's own driver, so the driver is what you install. The watchmymedia user is already in the
render and video groups, which own the GPU, so there is no group to add.
Fedora builds its own AMD and Intel drivers without H.264 and HEVC, the two formats nearly every conversion uses. With Fedora's packages alone, expect the server to convert in software. The drivers that have both are in RPM Fusion, a separate repository you turn on yourself: its Configuration page has the lines.
- AMD:
mesa-va-drivers-freeworld, from RPM Fusion's free repository. -
Intel:
intel-media-driver, from RPM Fusion's nonfree repository. Older Intel GPUs uselibva-intel-driver, from its free one. - Intel Quick Sync: add Fedora's
libvplandintel-vpl-gpu-rtto the Intel driver. - NVIDIA: RPM Fusion's NVIDIA page has the steps for NVIDIA's driver. This page names no package for it, because none has been checked.
Then open Settings › Transcoding in the web app. Its Encoder section names the encoder in use and whether it passed its test. If the server fell back to software, a banner says so, with Test again and Choose another.
What has been checked: the package names, and what each driver is built with, read from Fedora's and RPM Fusion's package lists and build files. None was installed, and nobody has yet converted a video on an Intel, AMD or NVIDIA GPU with this package, so this page can't promise that yours will be used.
Update it
New versions come from WatchMyMedia's repository, with the system's other updates. To update only WatchMyMedia now:
sudo dnf upgrade --refresh watchmymedia
Check for updates, under Settings › General, says when a newer version is out and gives the same line. An update restarts the server, which stops anything playing or recording, so pick a quiet moment.
Back up first: 2.0.0 changes the server's database, and going back to 1.8.0 afterwards needs a backup made before the update.
sudo -u watchmymedia watchmymedia backup makes one. If the system updated it before you could,
Updates and backups says which backup to use.
The service, its files and its logs
-
The service is called
watchmymedia.systemctl status watchmymediasays whether it is running, andsudo systemctl restart watchmymediarestarts it, which stops anything playing or recording. -
Logs go to the system's journal:
sudo journalctl -u watchmymedia. Add-fto watch new lines arrive, or-bfor the lines since the computer started. -
Your library's data, which is its database, artwork and backups, is in
/var/lib/watchmymedia. Video being converted is in/var/cache/watchmymedia. Both are closed to the computer's other users. -
The settings file is
/etc/watchmymedia/config.yaml. Every option in it starts commented out, because nearly everything is set in the web app. Edit it withsudoedit /etc/watchmymedia/config.yaml, then restart the service. Its first lines say how to move the two folders above. -
The server's own commands run as its user, so that they use the same folders. A backup, for example:
sudo -u watchmymedia watchmymedia backup.
Remove it
sudo dnf remove watchmymedia
This stops the service and removes the program and the video being converted. It keeps your library's data in
/var/lib/watchmymedia, and a settings file you changed as /etc/watchmymedia/config.yaml.rpmsave,
which the next install puts back, so installing the package again carries on where you left off. Your video files are never
touched.
To delete the library's data too, which can't be undone, run sudo rm -r /var/lib/watchmymedia. Removing the
package doesn't remove the watchmymedia user.
If it doesn't work
Written on November 18, 2026, for WatchMyMedia 1.7.0, the first release with this package; not yet followed step by step on a real Fedora system. The package was installed, updated and removed in containers of Fedora 45 and 44, where rpm also accepted the key, and the folder commands in step 3 and after it were run in a Fedora 45 container. Step 1 and Add the repository first were run in Fedora 45 containers against this site's repository, where both installed 1.7.0, dnf showed the fingerprint above, and the repository updated. SELinux, the firewall, the drive and share lines and everything about GPUs have not been tried. Update it gained the 2.0.0 backup note on November 21, 2026.