Skip to content
Serverküche
Search

Loading search …

Applications Difficulty: Intermediate

Navidrome: Stream Your Own Music Like Spotify

Stream your music collection from anywhere – no subscription, no tracking: Navidrome behind Traefik, with app support via the Subsonic standard and backups.

· Last updated: · 12 min read ·Duration: approx. 50 minutes
Table of contents

Your painstakingly assembled music collection sits on a hard drive while you pay for Spotify on the go? Navidrome turns your own files into a streaming service: a web interface, mobile apps, access everywhere – and nobody analyzes what you listen to.

What are we building?

A personal music streaming server with Navidrome (v0.64.2) behind Traefik. By the end you browse your collection in the browser by album, artist and genre, stream on demand – and connect the app of your choice (Symfonium, DSub, play:Sub …) via the Subsonic standard to listen on the go too. On top of that we create separate accounts for housemates, set up transcoding for mobile networks and let Navidrome back up its own database.

Navidrome is written in Go and correspondingly frugal. On a netcup VPS, docker stats reports about 48 MiB of RAM for the running container at under 1 % CPU – the music collection itself is what takes up space, not the server.

For audiobooks and podcasts it is the wrong tool, though: Navidrome thinks in albums and tracks, not chapters, and does not remember your listening position across devices. Use Audiobookshelf for those – the two run side by side on the same server without trouble.

Prerequisites

  • A server with Traefik running and Docker Compose
  • A subdomain pointing at the server – YOUR_DOMAIN below
  • Your music files (MP3, FLAC, …) with proper metadata (tags) – Navidrome builds the library from them
  • Enough disk space for the collection: one hour of MP3 at 320 kbit/s takes about 140 MB, the same hour as FLAC two to three times that, depending on the material
🍳 Recommendation Ad

VPS 1000 G12.5

4 vCores · 8 GB RAM · 128 GB SSD

from €14.50/month

Navidrome is frugal; for large collections mostly the storage space matters.

Go to netcup →

💶 1 month free:

Single use, valid for VPS 1000 G12.5. Redeem in the cart →

💶 €5.95 voucher for new netcup customers: always valid · not for domains or VPS Lite

All netcup vouchers →

Step by step

Step 1: Create the project

Navidrome needs two folders: one for the music (read-only) and one for its database/index. Create the project:

Terminal
mkdir -p /opt/navidrome/data /opt/navidrome/music && cd /opt/navidrome

The container will not run as root but under UID 1000 – the usual first user on a Debian system, which keeps Navidrome away from everything but its own files (more on that in Users & permissions). For the process to be able to write its database, the directory has to belong to it:

Terminal
chown -R 1000:1000 /opt/navidrome

Step 2: Get the music onto the server

Copy your music into the music folder – ideally cleanly structured (Artist/Album/Track.mp3). rsync over SSH is well suited for the transfer:

Terminal
rsync -av --progress ~/Music/ root@YOUR_SERVER_IP:/opt/navidrome/music/

What matters is good metadata: Navidrome reads artist, album, title, year and cover from the files’ tags, not from the filenames. Poorly tagged files end up unsorted in the library. The folder structure still isn’t irrelevant – Navidrome processes the collection folder by folder, and logs it that way too.

You don’t have to worry much about formats: Navidrome reads MP3, FLAC and Opus from the same folder without complaint. Don’t forget the permissions after copying, otherwise the container won’t see the new files:

Terminal
chown -R 1000:1000 /opt/navidrome/music

Step 3: The Compose file

Replace YOUR_DOMAIN:

YAML
services:
  navidrome:
    image: deluan/navidrome:0.64.2
    restart: unless-stopped
    user: "1000:1000"
    environment:
      ND_MUSICFOLDER: /music
      ND_DATAFOLDER: /data
      ND_SCANNER_SCHEDULE: 1h        # look for new files hourly
      ND_BACKUP_PATH: /data/backup   # Navidrome backs up its database itself
      ND_BACKUP_SCHEDULE: "0 4 * * *"
      ND_BACKUP_COUNT: 7
    volumes:
      - ./data:/data
      - ./music:/music:ro        # mount the music read-only
    networks: [proxy]
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.navidrome.rule=Host(`YOUR_DOMAIN`)"
      - "traefik.http.routers.navidrome.entrypoints=websecure"
      - "traefik.http.routers.navidrome.tls.certresolver=le"
      - "traefik.http.routers.navidrome.middlewares=navidrome-only-me"
      - "traefik.http.middlewares.navidrome-only-me.ipallowlist.sourcerange=YOUR_IPV4/32,YOUR_IPV6_PREFIX::/64"
      - "traefik.http.services.navidrome.loadbalancer.server.port=4533"

networks:
  proxy:
    external: true

The :ro on the music volume is deliberate: Navidrome should only read your files, never modify them. ND_SCANNER_SCHEDULE: 1h has it look for new music hourly.

The three ND_BACKUP_* lines switch on Navidrome’s built-in database backup: it writes a consistent copy of its SQLite database to /data/backup at 4 a.m. and keeps the last seven of them. Navidrome creates the folder itself on the first run. That costs next to nothing and saves your playlists, user accounts and play statistics if an update goes sideways – details in “Maintenance & backups”.

navidrome-only-me lets only your own address through until setup is finished; everyone else gets 403 Forbidden. As long as no admin account exists, the instance otherwise belongs to whoever opens the page first – and scanners sometimes find new hostnames via the public certificate transparency logs within seconds of startup. Look up your addresses on your own computer, not on the server: curl -4 -s https://ifconfig.me for IPv4, curl -6 -s https://ifconfig.me for IPv6 (take the first four blocks). If you have no IPv6, drop the second entry including the comma – but only then: browsers prefer IPv6, and an IPv4-only list locks you out yourself. More on this in Hardening Traefik.

Step 4: Start and check the scan

Terminal
docker compose up -d

Navidrome scans the library on first start. You can follow it in the log – --no-log-prefix drops the container name in front of every line, which would otherwise make them needlessly wide:

Terminal
docker compose logs --no-log-prefix | grep "Scanner:"
Ausgabe
time="2026-09-30T23:48:38Z" level=info msg="Scanner: Starting scan" fullScan=true numLibraries=1
time="2026-09-30T23:48:39Z" level=info msg="Scanner: Completed processing folder" audioCount=1 elapsed=318.9ms imageCount=0 library="Music Library" plsCount=0 tracksImported=1 tracksMissing=0 folder="DJ Backup/Cronjobs"
time="2026-09-30T23:48:39Z" level=info msg="Scanner: Completed processing folder" audioCount=2 elapsed=318.1ms imageCount=0 library="Music Library" plsCount=0 tracksImported=2 tracksMissing=0 folder="Serverkueche Quartett/Kuechenklaenge"
time="2026-09-30T23:48:39Z" level=info msg="Scanner: Finished scanning all libraries" duration=333.7ms

Every folder gets its own line (the ones for the empty artist folders are left out here). tracksImported shows how many tracks were recognized there – three in total in this example. For large collections the first scan takes correspondingly longer; the Finished scanning all libraries line marks the end.

The same log tells you the backup is scheduled:

Terminal
docker compose logs --no-log-prefix | grep "periodic backup"
Ausgabe
time="2026-09-30T23:48:36Z" level=info msg="Scheduling periodic backup" schedule="0 4 * * *"

Step 5: Create the admin account

Open https://YOUR_DOMAIN/. On first access you create the administrator account:

The Navidrome first-run screen for creating the admin account
On first start you set the admin's username and password

Pick a username and a strong password. The interface is out on the open internet and the admin account is the only thing protecting it – don’t reuse a name you already use elsewhere. Afterwards you land directly in your library.

Don't leave the wizard sitting open

Until the admin exists, anyone who can reach the page can create that first account. The navidrome-only-me lock from step 3 closes this window – so only remove it afterwards.

Once the admin account exists, remove the lock again: delete the two lines containing navidrome-only-me from the compose.yaml and apply the change:

Terminal
docker compose up -d

Step 6: Browse the library

The web interface shows your music by album, artist, genre and recently added – with cover grids and search:

The Navidrome album overview with the recognized albums and artists
The library: albums with cover, artist and filter options

Clicking an album opens the track list; double-clicking a track starts playback in the built-in player at the bottom:

An opened album with track list and the running player at the bottom
Album view with track list – the built-in player at the bottom is playing the first track

The sidebar on the left switches between albums, artists, songs and the automatic lists (“Recently Added”, “Most Played”); the search field and ADD FILTER narrow down the current view. The refresh icon in the top right triggers an immediate scan if you don’t want to wait for the next interval.

Step 7: Accounts for housemates and family

Don’t share the admin account. Everyone who listens gets their own – that way each person has their own playlists, favourites and play statistics, and nobody can accidentally change server settings. You create the account in the interface under Users via CREATE:

The form for creating a new Navidrome user with username, password and library selection
A new account: username, password – and the “Is Admin” switch stays off

Leave the Is Admin switch off. Under Libraries you pick which libraries the account may see; leave the selection empty and the default libraries apply. Each of these accounts then works in the mobile apps exactly the same way.

Step 8: Connect mobile apps via Subsonic

Navidrome speaks the Subsonic API – an established standard supported by many music apps. That’s how you listen to your collection on the go with the app of your choice. In the app you enter:

  • Server: https://YOUR_DOMAIN
  • Username/password: your Navidrome account

Recommended apps: Symfonium or Tempo (Android), play:Sub or substreamer (iOS). That’s the advantage of an open standard: if you don’t like an app, you swap it out without changing anything on the server. Navidrome announces itself as an OpenSubsonic server – an extension of the old Subsonic protocol that lets newer apps additionally request things like lyrics or extended metadata.

You can check whether the API answers at all without any app, using a single call – the error about the missing user is exactly the expected result here:

Terminal
curl -s "https://YOUR_DOMAIN/rest/ping.view?v=1.16.1&c=test&f=json"
Ausgabe
{"subsonic-response":{"status":"failed","version":"1.16.1","type":"navidrome","serverVersion":"0.64.2 (10114574)","openSubsonic":true,"error":{"code":10,"message":"missing parameter: 'u'"}}}

If that answer comes back, domain, certificate and the Traefik route are fine – then a connection problem is down to the credentials or the app.

Step 9: Set up transcoding for mobile networks

Pulling full-resolution FLAC files over a shaky mobile connection ends in stutters and a burnt-through data plan. Navidrome can therefore shrink the stream on the way out (transcoding) – the image already ships the required ffmpeg, you don’t have to install anything.

This is configured per player, not per account: every app that has connected once shows up in the interface under Players as its own entry. Open it and set Transcoding and Max. Bit Rate:

The Navidrome player settings with a transcoding profile and a maximum bit rate set
Per player: transcoding profile “mp3 audio” and 128 kbit/s as the ceiling

The available profiles are aac audio, flac audio, mp3 audio and opus audio, with bit rates from 32 to 320 kbit/s. mp3 audio at 128 kbit/s is a good compromise for the road and plays on any device.

You can measure that it works: a track that comes down the wire as the original at 48,693 bytes arrives at only 24,349 bytes with a 32 kbit/s ceiling – half the data, with the original file on disk untouched. Simply leave the browser’s player without transcoding, and you keep listening in full quality at home.

When things go wrong

The page responds with 403 Forbidden. The lock from step 3 doesn’t let your address through. Usually the IPv6 is missing or has changed – look up both addresses again (see there), correct sourcerange and restart with docker compose up -d.

The library stays empty. Either there are no files in the mounted music folder, or the permissions are wrong. Check: docker compose logs --no-log-prefix | grep "Scanner:" shows tracksImported. If it’s 0 everywhere, check the path and that the music folder is owned by UID 1000 (see Users & permissions).

Tracks appear unsorted or without cover art. The files’ metadata is incomplete – Navidrome sorts by tags, not by filenames. What it actually reads from a file is shown by docker compose exec navidrome /app/navidrome inspect "/music/Artist/Album/Track.mp3": under rawTags you get the tags exactly as they sit in the file. If album or albumartist are missing there, re-tag the files (e.g. with Picard) and let Navidrome rescan.

New music doesn’t show up. The scan only runs hourly (ND_SCANNER_SCHEDULE). Trigger an immediate scan via the refresh icon in the top right of the web interface, or wait for the next interval. If the files were just uploaded, what’s usually missing is the chown -R 1000:1000 from step 2.

The app won’t connect. Almost always the server URL: it must be https://YOUR_DOMAIN (with https://, no path). If the ping.view call from step 8 answers cleanly, it’s the credentials – since version 0.64.1 Navidrome additionally throttles repeated failed logins through the Subsonic API, so after a few typos a short break helps.

Playback stutters on large FLAC files over mobile. The bandwidth isn’t enough for the original. Set a transcoding profile and a ceiling for your app’s player (step 9) – the entry only appears under Players after the app has connected once.

Your problem is not listed? Search all error messages →

Maintenance & backups

  • Updates. Occasionally bump the image tag (deluan/navidrome:0.64.2) to the current version and docker compose up -d; Navidrome migrates its database at start. The rest runs through your normal update process. Before a version jump, a fresh database backup is worth it – 0.64.0, for example, re-encoded all internal IDs and touched every table doing so; the log afterwards says Full scan required after migration and the first start takes longer than usual. Staying current is still worth it: the 0.64 series closed several reported security vulnerabilities.

  • Back up the database (built in). With the ND_BACKUP_* variables from step 3, Navidrome creates the backup itself. To take one right now:

    Terminal
    docker compose exec navidrome /app/navidrome backup create
    Ausgabe
    time="2026-09-30T23:45:06Z" level=info msg="Backup complete" elapsed=10.9ms path=/data/backup/navidrome_backup_2026.09.30_23.45.06.db

    The files then sit in /opt/navidrome/data/backup and are around 700 KB for a small collection. There is navidrome backup restore to put one back and navidrome backup prune to clear out old ones.

  • Two-part backup. Your music is the valuable, irreplaceable part – it belongs in your Restic backup anyway (or you have it elsewhere). The data folder with the index, play statistics, playlists and user accounts is small and should be backed up too; use the backup files from the previous point rather than the live navidrome.db – an SQLite file copied away while in use can be inconsistent.

  • Check the database. If the interface starts showing odd errors, a built-in check tells you whether the database is still intact:

    Terminal
    docker compose exec navidrome /app/navidrome doctor
    Ausgabe
    Checking database integrity...
    Integrity check passed.
    Checking foreign keys...
    Foreign key check passed.
    Database is healthy.
  • Low effort. After setup, maintenance mainly means dropping new music into the folder – the hourly scan handles the rest. As the collection grows, watch the disk space (df -h); music adds up fast. The service itself stays small: 48 MiB of RAM in operation, and at around 348 MB the image mostly carries the bundled ffmpeg.

You might also like