Install and Configure a ReadyMedia (miniDLNA) Server on Linux

Updated 20 October 2026.

ReadyMedia, formerly miniDLNA, shares a media library with compatible players on your local network. It is a small server for files you already have. It does not turn every video into a format every television can play.

Check the package for your distribution

On Debian and many Ubuntu installations, the package and service are called minidlna. The Debian package page identifies the package; other distributions can use different paths or service arrangements.

sudo apt update
sudo apt install minidlna
systemctl cat minidlna

These commands are a Debian-style example, not a universal Linux installer. Inspect the installed service and configuration before editing. Put only files you intend to share in the library.

Configure the media folders

Back up /etc/minidlna.conf, then edit the existing settings. This example assumes the folders already exist:

media_dir=V,/srv/media/videos
media_dir=A,/srv/media/music
media_dir=P,/srv/media/photos
friendly_name=Home Media
inotify=yes
port=8200
network_interface=enp3s0

Replace enp3s0 with your actual trusted LAN interface, found with ip link. Do not paste that interface name unchanged. The configuration manual explains the A, V and P prefixes, repeated media directories and interface binding.

Give the service permission to read the files

The account running the service needs to traverse the parent folders and read the media. Check the unit, local package configuration and folder permissions. A directory inside a private home folder may be inaccessible even when the media file itself is readable.

Use a dedicated shared folder and appropriate group access. Do not make your whole home directory world-readable or use chmod 777 as a discovery fix. Also check the database directory is writable by the service.

Start and inspect the service

sudo systemctl enable --now minidlna
sudo systemctl restart minidlna
systemctl status minidlna --no-pager
journalctl -u minidlna -n 50 --no-pager

The daemon manual documents command-line behavior. Avoid starting a second manual daemon while systemd already runs one. Give a large library time to scan and read the logs before rebuilding its database.

Keep access on the trusted local network

Discovery normally uses SSDP on UDP 1900, with media served over the configured TCP port, 8200 in this example. Scope any firewall allowance to the trusted LAN and correct interface. Do not forward these ports from the internet or disable the whole firewall.

Guest Wi-Fi isolation, separate VLANs and multicast filtering can prevent discovery even when the service works. First test a client on the same trusted network.

Separate discovery from playback problems

If the server appears but a file will not play, check the television or player supports its container, codecs and subtitles. ReadyMedia is not a general-purpose transcoder. Our video metadata guide explains how to inspect those properties.

FAQs

Are miniDLNA and ReadyMedia different servers?

ReadyMedia is the project name formerly known as miniDLNA; many packages still use the minidlna name.

Why can the server not read my videos?

Check the service account, parent-directory access, file permissions and whether the storage is mounted.

Why does the TV see the server but reject a movie?

The player may not support the file’s container, video codec, audio codec or subtitles.

Should I open the server to the internet?

This setup is for a trusted LAN. Do not add public port forwards for discovery or media access.