Skip to content

Media app shows an empty library or no folders

TroubleshootingDeployrr v6.0+CurrentMediaHost systemDocker ComposeDocker

You installed a media app such as Plex, Jellyfin, Emby, Navidrome, Sonarr, Radarr or Lidarr. One of these happens:

  • The library is empty after you add it.
  • The folder browser inside the app shows no media folders, or an empty one.
  • Only some of your files show up.
  • Sonarr, Radarr or Lidarr do not list /data/media1 as a root folder.

The app runs in a container and sees your files at a different path than your server does. In v6, the media apps see your folders like this:

Folder on your server Path inside the app
Media Folder 1 /data/media1
Media Folder 2 /data/media2
Media Folder 3 /data/media3
Downloads Folder /data/downloads

For the paths of every app, including books, photos and audiobooks, see the App reference.

Navidrome gets the media folders but not the Downloads Folder. If your library is fine but finished downloads never reach it, see Sonarr, Radarr or Lidarr don’t import finished downloads.

The library is empty when one of these is true:

  • The folder on your server is empty or not mounted.
  • You set a media folder after you installed the app, so the app never got it. This is most often Media Folder 2 or 3. These apps don’t install without at least one media folder set.
  • The library in the app points at the server path instead of the /data path.
  • Your user cannot read the folder.
  • The app has not scanned the folder yet.

Work through the checks below in order. Stop when your library fills.

  1. In Deployrr, go to System > Folders. Note the path next to Media Folder 1. If it says NOT SET, set it as shown in Set a folder, then go to check 2.

  2. List the folder on the server. Replace YOUR_MEDIA_FOLDER with the path from step 1:

    Terminal window
    ls YOUR_MEDIA_FOLDER
  3. Look for your media type folders, such as movies and tv. If the list is empty, the problem is on the server, not in the app.

If your media is on a NAS and the list is empty, the share is not mounted:

When the files show on the server again, restart the app from Apps > Manage Apps: pick the app and choose Restart, or Start if it is stopped. See Install and manage apps from the Apps menu.

An app only gets the media folders that were set when you installed it. To see why the order matters, watch Deployrr 5 walkthrough: Setup Folders at 22:17 (shows Deployrr v5; menus differ in v6).

  1. Look inside the app’s container. Replace APP with the app’s name, such as jellyfin:

    Terminal window
    sudo docker exec APP ls /data

    With the Deployrr bash aliases: dexec APP ls /data.

  2. Look for media1, and media2 or media3 if you use them. If a folder is missing, the app does not have it.

  3. To confirm, read the app’s compose file. Replace YOUR_DOCKER_FOLDER with your Docker folder path, HOSTNAME with your server’s hostname and APP with the app’s name:

    Terminal window
    grep MEDIADIR YOUR_DOCKER_FOLDER/compose/HOSTNAME/APP.yml

    A line that starts with # is off. For example, # - $MEDIADIR1:/data/media1 means the app has no Media Folder 1.

  4. If the lines are off, but you set the folder in System > Folders, reinstall the app. Reinstalling keeps the app’s data but replaces its compose file, so make the backups on that page first. For a running app, start the reinstall from Apps > Browse Apps. Manage Apps shows Reinstall only for a stopped app.

  5. If the lines are on and the path in .env changed, recreate the app. Go to Tools > Stack Manager > Recreate and pick the app. See Stack Manager. With the Deployrr bash aliases: dcrec APP.

Recreating does not turn on a media folder that was off. Only a reinstall does. To pick the right action for other changes, see Restart, Recreate or Reinstall an app. For the full explanation, see Apps you installed before you set a media folder.

In the app, add the library with the /data path, not the path on your server. Do not type a path like /home/YOUR_USER/media/movies. The app cannot see that path.

Pick the folder for one media type, such as /data/media1/movies or /data/media1/tv, not /data/media1 itself. Use your own folder names; these are examples.

Jellyfin

  1. Go to Admin > Dashboard, then Server > Libraries.
  2. Click Add Media Library.
  3. Pick the content type, such as movies or shows, and give the library a name.
  4. Add a folder and browse to /data/media1/movies. If the browser doesn’t show it, type the path.
  5. Save the library.

Emby

  1. Open the server dashboard and go to Library.
  2. Click Add Media Library.
  3. Pick the Content Type and enter a display name.
  4. Under Library Paths, click + and browse to /data/media1/movies, or type the path and click OK.
  5. Save the library.

Plex

Add a library, pick its type, then add a folder and pick /data/media1/movies. The menu names change between Plex versions, so follow what your Plex shows.

Sonarr, Radarr and Lidarr

  1. Go to Settings > Media Management.
  2. Under Root Folders, add a root folder. In Sonarr and Radarr the button is Add Root Folder. In Lidarr it is Add (+), and you also give the folder a Name.
  3. Pick the folder for that app’s media, such as /data/media1/tv for Sonarr, /data/media1/movies for Radarr or /data/media1/music for Lidarr.

Do not use /data/downloads or a folder inside it as a root folder. Sonarr, Radarr and Lidarr need the download folder and the root folder to be different places. If finished downloads don’t reach the root folder, see Sonarr, Radarr or Lidarr don’t import finished downloads.

To link these apps to each other and to a media server, see Connect your apps to each other.

Apps run as your Linux user and its main group. Deployrr makes your user the owner only of a folder it creates for you. A folder that already existed keeps its own owner. A folder owned by root, or a NAS share your user cannot read, gives an empty or partial library.

  1. Check the owner. Replace YOUR_MEDIA_FOLDER with your path:

    Terminal window
    ls -ld YOUR_MEDIA_FOLDER
  2. For a local folder owned by root, check the path again. Make sure it is your media folder and not / or your home folder.

  3. Make your user the owner. Replace YOUR_USER with your Linux username and YOUR_MEDIA_FOLDER with your path. The command assumes your main group has the same name as your user, which is the default on most systems:

    Terminal window
    sudo chown YOUR_USER:YOUR_USER YOUR_MEDIA_FOLDER
  4. If the folder holds subfolders you cannot read, run ls -ld on one of them. Fix the owner the same way.

To see a root-owned mount folder fixed by hand, watch Rclone SMB mount on Ubuntu/LXC: folder owner at 11:09 (manual setup).

On a NAS mount, the NAS decides who can read. Check the share permissions on the NAS, and that the account you mount with can read the share. See UDMS part 07: Permission Denied Errors (manual setup). For more, see The app cannot read or write the folder.

A new library can take a while to fill. Media servers scan in the background, and big libraries can take a long time.

  1. Open the app.
  2. Find the library and start a scan, or refresh it. The menu text depends on the app.
  3. Wait, then check again.
  1. Run sudo docker exec APP ls /data/media1 with your app name. You see your media type folders.
  2. Open the app. The library shows your titles.
  3. In Sonarr, Radarr or Lidarr, the root folder list shows a path under /data/media1.