Lidarr
Lidarr is required. Aurral uses it to add artists and albums, read library state, and surface queue and history status.
Connection
Section titled “Connection”During onboarding or in Settings → Integrations → Lidarr, provide:
- The URL Aurral can reach (often
http://lidarr:8686in Docker) - Your Lidarr API key
- Default quality profile, metadata profile, tag, monitoring option, and search-on-add behavior
- Optional Davo’s Community Lidarr Guide for discovery-friendly quality profiles and naming
Library access check
Section titled “Library access check”Aurral tests that it can read files at the paths Lidarr reports. If this fails, confirm the shared /data mount described in Shared storage.
On mixed Windows and Docker setups, run Test library access to auto-detect path mappings. Aurral translates host paths such as N:\Music\... into mounted container paths such as /music/Music/.... You can review or edit mappings under Settings → Playlists → Path mappings.
Path mappings apply to Aurral reading files. If Navidrome runs outside Docker, enable Use host paths in playlist files under Settings → Integrations → Navidrome so M3U playlists use host paths instead. See Navidrome.
Safety
Section titled “Safety”Artist and album changes go through Lidarr. Aurral does not write directly into your root music library.