How to Self-Host Music Player Daemon
Music Player Daemon long-running music playback service controlled by many local and remote clients, with playlists, library scanning, and flexible audio outputs. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Music Player Daemon is a good fit
Choose Music Player Daemon when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Install the distribution package or official binary, configure the music library, database, playlists, and selected audio output, then run it as a restricted service account.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Back up the MPD configuration and playlists; the music library should have its own backup and integrity policy.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Do not expose the unauthenticated control port to untrusted networks; use firewall rules, a VPN, or a trusted proxy layer.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
