r/Lidarr • • Aug 18 '25

Lidarr Update - (The Start of) The Fix

349 Upvotes

Note: I am not a developer, just pasting things from Discord.

There's an ongoing issue with the Lidarr metadata server., This issue affects anything that requires fresh metadata, including searches and adding artists.

(The Start of) The Fix**, As of August 17, we have started routing a portion of all API traffic to the new metadata server. This portion will increase over time until everything is going through the new metadata server.

What does this mean? Some searches/adds/imports will work! Yay! But the cloudflare cache needs to rebuild, so you may see a smaller percent actually working properly until it gets built up, and you may still experience metadata server issues for a majority of your actions.

Which requests will work and which won't is entirely random. You can't influence this, and we ask that you bear with us during this phase.

Why? While the metadata server is currently functional, some testing and work (see below) still remains. We figure this is a better solution than a longer closed beta (with only some of you users) and just letting everyone loose on the server at once and seeing it crash and burn within 5 minutes.

A couple of notes:

  1. Artist images are currently broken. This means you're going to probably lose your Lidarr artist images until they are working again and rebuild.

  2. The ordering of search results is not working right. This means that sometimes when you text search for artists, it might return things like cover bands, but not the real band. ID-based searches should work fine.

We recommend that if you did use an alternate metadata server during this outage, that you please revert. This will help build up cloudflare cache and make things better for everyone.

As always, thank you for your patience. The mod team here appreciates that the vast majority of users here have been patient and civil.

You can always find the latest update in the pinned messages for this channel (click the pin icon at the top right on PC, and the channel name/pin tab on mobile).

https://discord.com/channels/264387956343570434/1028840582270955612/1407087532746735677


Update

Some thoughts after 24 hr of "new metadata", The fix is entirely on the server side. You don't need to do any changes to your Lidarr (unless you switched to an alternative metadata source), Which requests go to the new server and which go to the old is effectively random. There's no prioritization, but more popular artists/albums have a higher change of being cached because of more requests., All requests go through the cache first, so if the request is already cached, you'll get a response., A text search is different from an ID search. If one is cached, the other isn't (necessarily) cached. For the moment, ID searches seems to have a higher chance of being cached., Similarly, each album is a separate request. So you might be able to add artists, with 0 tracks, and you might be able to see some albums for that artist. This will eventually fix itself.,

For the moment, most requests fail. This will improve over time, first as more requests are cached, and later as we increase the ratio of requests that go to the new server. You'll still be seeing the Unable to communicate with LidarrAPI. error for a little while, this is expected.

How can I find a musicbrainz ID?, Navigate to the artist or album on Musicbrainz., Find the ID at the end of the URL, OR on the Detail page, under MBID., The ID will be a long string of letters and numbers, separated by dashes, e.g: 710e234d-e1e2-4f30-89ec-01bd71f6e4a3, Prefix the ID with lidarr: in the Add New/search box, e.g: lidarr:710e234d-e1e2-4f30-89ec-01bd71f6e4a3, Remember that an ID search is still likely to fail (for now)


r/Lidarr • • Jul 25 '25

discussion Lidarr Metadata Update!

200 Upvotes

See https://github.com/Lidarr/Lidarr/issues/5498#issuecomment-3118306944

It sounds like the devs are getting close to long-term solution! This is breath of fresh air as blampe's metadata instance has been struggling to keep up with everyone moving over, and self-hosting metadata is still quite cumbersome (although the guides are improving)


r/Lidarr • • Jun 13 '25

discussion Have we forgotten what open source means?

174 Upvotes

Looking at the servarr discord this morning… There’s something genuinely disturbing/infuriating going on there. https://imgur.com/a/JIofJqc

How is this not a bad look for the community?

A couple of community forks of Lidarr have popped up that work as a temporary bandaid to the closed source metadata server by creating its own open source solution.

The moderator(s) of the Servarr community have actively shut down any discussion of this idea - in the past the moderator(s) went as far as to say that an alternative was ‘impossible’, and now that this has been proven to be wrong he is claiming that discussing anything that isn’t the ‘official’ Lidarr will result in time outs or bans.

Is this an open source project or not? Is the community not meant to derivate and improve, as is the spirit of open source? Why are we calling an open source project that is a fork of a fork ‘official’? Why are we tolerating a solution that completely prohibits open source contributions, and furthermore why are we promoting a community that is gate keeping discussions about this?


r/Lidarr • • Apr 03 '26

discussion Musicseerr - a self-hosted music request and discovery project built around Lidarr

172 Upvotes

Hello everyone, my name is Harvey - I'm a backend software engineer from the UK. I've been really into self-hosting, privacy, etc recently and for the past 6 months I have been working on this project, Musicseerr.

It started as I was looking for something to bridge a gap between slskd and Lidarr where I could search for music and request directly to Lidarr (A bit like the Jellyseerr/Arr flow) but I couldn't find anything. So, around 6 months and I've finally released Musicseerr into a v1. It currently supports the following features:

  • Search & Request - Search the full MusicBrainz catalogue and send requests to Lidarr

  • Built-in Player - Stream from Jellyfin, Navidrome, local files, or YouTube, with a 10-band EQ

  • Discovery - Personalised album recommendations based on your listening history

  • Home - Trending artists, popular albums, and genre-based sections

  • Scrobbling - ListenBrainz and Last.fm support

  • Library - Browse and filter your Lidarr library with full artist/album pages

  • Playlists - Create and manage playlists with playback support

  • Requests page - Track, retry, and cancel requests

I'm pretty proud of it but I still know that there's a lot that could be added, and it's definitely due some user testing! I'd love for anyone to give it a go, I'm always open to bug-reports/feedback/suggestions so feel free to send them to me on here, or on the discord linked in the Github/Website.

Thanks all and I hope it helps some of you :)


r/Lidarr • • Apr 21 '18

Beta Release!

166 Upvotes

Beta Release

We are proud to announce our first public beta release. We wanted to take the opportunity to once again thank all of those that have donated and supported us! We sincerely appreciate it!

For those that have never heard of Lidarr before, Lidarr is a music collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new tracks from your favorite artists and will grab, sort and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.

Few items recently added since last update that could use some testing from you guys:

  • Custom filtering of releases for manual album searches (Thanks Markus101)

  • Release status filtering in metadata profiles

  • Discography downloading

  • Manual album release selection

  • Album details page in UI

  • Import Lists (Billboard, Last.fm, Itunes)

  • Better artist import matching (based on rating)

  • Fuzziness on new artist search.

  • Single Album notifications

  • Track parsing improvements (using musicbrainz release tag to identify album, cleaning album title, cleaning track title)

  • Ratings for artists/albums (these come from musicbrainz currently so rate items there to improve this)

  • Album monitoring options on artist add (future, existing, missing, first, last)

  • Various other Core, Metadata, and UI improvements

Also for fun we wanted to share a few stats from our api thus far as well:

2600 unique users

600,000 requests per day

Top 5 artists from the user base:

  1. Eminem

  2. Coldplay

  3. Metallica

  4. Linkin Park

  5. Red Hot Chili Peppers

Thanks again to everyone testing and submitting bug reports. This has been extremely helpful! If anyone would like to volunteer to help with the Wiki, please let us know. Additionally we appreciate any and all donations to help us with server hosting. Please visit OpenCollective to donate.

Installation instructions: https://github.com/lidarr/Lidarr/wiki/Installation


r/Lidarr • • Feb 13 '26 Bravo Regret

discussion hi i created an app to help make lidarr a little better

164 Upvotes

I created an overseerr-like app called aurral that serves as a front end for lidarr. It lets you search and add artists and albums, change monitoring, discover new artists based on your library and listening history, as well as a built-in soulseek client that will automatically create and download weekly playlists for you based off your recommendations and send them straight to a navidrome/subsonic client.

I think it's really cool and I've been working hard on making it really reliable these last couple weeks with lots of help and support with our community on github and discord.

you should check it out if it sounds interesting to you!

https://github.com/lklynet/aurral


r/Lidarr • • Jun 17 '25

discussion Thanks devs! Appreciation post

118 Upvotes

Pretty sure most users of Lidarr never thought about the devs or all the work that has been done behind the scenes making this tool. I'd been using it for years and I hadn't. Now that there's a big problem everyone's coming out of the woodwork with complaints, suggestions on how they could do a better job (without realizing the behind-the-scenes complexities), etc. That just shows me how many actual users of this software there are, which is great. I've not yet seen someone come out with an alternative they're switching to. I'm sure a few folks are trying to make a brand new music app on their own to replace Lidarr, maybe they're finding out how daunting that is. Good on them for trying and I hope the best for them, if they succeed in making a better app and everyone switches to it, so be it. For now, I will continue to patiently wait for the hard-working devs to work their magic. I'm making a short list of music I will add once I'm able. Mostly I'm enjoying listening to the music that I already have, which is the main thing anyways.


r/Lidarr • • Dec 10 '25

The metadata server is MOSTLY back!

116 Upvotes
  • The metadata updates from Musicbrainz are a little bit delayed and may take 3 hours to appear. Refreshes before this time are useless.

  • Release groups with (unknown) status do not sync. They must be Official.

  • Text searches are somewhat working, and improving each day as the cache expires. In the meantime, adding by MusicBrainz ID works well. How can I find a MusicBrainz ID?

  • Images are mostly working again. Some are not; we're aware of the issue.

  • Spotify lists are enabled again. Currently, Spotify lists only work for artists who have a Spotify link associated with them on Musicbrainz, but we're working on that.

If you are unable to search for an artist in Lidarr, follow the on-screen instructions to use the correct prefix.


r/Lidarr • • May 23 '25

unsolved Searching for new artists failed..."Unable to communicate with LidarrAPI."

116 Upvotes

Anyone else getting this error this morning?

I was searching for new music on my Lidarr install, and the following error message appears for all searches:

"Search for 'kiss' failed. Unable to communicate with LidarrAPI."

[EDIT - removed log block...it wasn't really necessary anyhow, except to extract the URL that I discuss next.]

Hitting https://api.lidarr.audio/api/v0.4/search?type=all&query=kiss in a browser gets an Internal Server Error. Assuming the issue is external to my installation.


r/Lidarr • • Oct 04 '24 Take My Silver

discussion Soularr! A Python script to connect Lidarr to Soulseek!

106 Upvotes

Hello! I've made a python script "Soularr" to connect Soulseek and Lidarr! It uses the Slskd client for soulseek and bridges the gap between the Lidarr API and the Slskd API to download and import any album from your "wanted" list in Lidarr.

Here's a quick little demo video.

View the project on github! Install instructions are in the readme. Give it a try and let me know if you have any issues. I've seen a few people ask for something like this on this sub and the soulseek sub. So let me know if you give it a try.

Thank you!

EDIT (2024-10-07): I finalized the dockerized version today. If you haven't already check the repo again and give it a try. Thanks again!

We also setup a discord server for the project today. Feel free to join if you need help troubleshooting or just want to talk about the project.

https://discord.gg/EznhgYBayN


r/Lidarr • • Sep 22 '25

"The metadata server is back online, but is still rate-limited!"

98 Upvotes

Note: I am not a developer. I am creating a new post to pin to this subreddit that accurately reflects the current message on Discord, which is always the authoritative source. Please see the previous post if you would like context.

(PLEASE READ BEFORE POSTING AN ISSUE)

The metadata server is back online, but is still rate-limited!

  • If you get a 503 or "LidarrAPI" error, please be patient and try again later. There is nothing you can do except wait.

  • Your albums might show 0/0 tracks, or you might get errors on refreshing an artist.

  • Lists are not working. Some tracks may go Unmapped.

  • The new metadata server is now being hit 100% of the time, but rate limiting is in place. We're still recommending people wait.

  • If you were running a cachewarming script, these are now blocked. Please turn them off.


r/Lidarr • • Sep 14 '25

The Lidarr devs are asking users to please turn off any warming scripts temporarily.

95 Upvotes

Not a developer, reposting from Discord.

The Lidarr devs are asking users to please turn off any warming scripts temporarily. We will also begin blocking the useragent of the script soon. We are asking this of you so that we can get an idea of the actual load hitting the server, in an attempt to evaluate where we can increase the hits to it without overloading it. This will make things better for everyone. We will advise when you are able to start running your warmer scripts again. Thank you for your help in getting us to 100% stable!


r/Lidarr • • Jun 14 '25

discussion Thank you Lidarr devs

94 Upvotes

I'll put on my crotchety old man pirate pants and say, I remember getting denial of service for Google books etc before the *arr apps came along.

This is god damned good software.


r/Lidarr • • Jul 16 '25

discussion Guide for setting up your own MB mirror + lidarr metadata, lidarr-plugins + tubifarry

92 Upvotes

EDIT (May-15, 2026): I said I wouldn't update this anymore, but wanted to share a note that today I updated the guide to support the recent schema change from musicbrainz with the migration to postgres18. Either continue to run your current environment without updating it, or wipe it and start over with the same guide which has been updated to support the latest version (no more mq/redis, adds valkey, postgres 18 instead of 16, new db schema, etc). Same link as before: HERE.

EDIT (Jul-21, 2025): Blampe has merged my PR, and this guide is now live in his repo. The authoritative guide can be found HERE.

EDIT (Jul-19, 2025): Guide below is updated as of today but I've submit a pull request with Blampe to add to his hearring-aid repo, and do not expect to update the guide here on reddit any longer. Until the PR is approved, you can review the guide with better formatting in my fork on github. Once the PR is approved, I will update the link here to his repo.

As a final note here, if you've followed the guide and found it's not returning results, trying doing a clean restart as I've seen this fix my own stack at setup. Something like:

cd /opt/docker/musicbrainz-docker
docker compose down && docker compose up -d

And also try restarting Lidarr just to be safe. If still having issues, please open an Issue on blampe's repo and I'll monitor there. Good luck!

ORIGINAL GUIDE
Tubifarry adding the ability to change the metadata server URL is a game changer, and thought I'd share my notes as I went through standing up my own musicbrainz mirror with blampe's lidarr metadata server. It works fine with my existing lidarr instance, but what's documented is for a new install. This is based on Debian 12, with docker. I've not fully walked through this guide to validate, so if anyone tests it out let me know if it works or not and I can adjust.

Debian 12.11 setup as root

install docker, git, screen, updates

# https://docs.docker.com/engine/install/debian/#install-using-the-repository

# Add Docker's official GPG key:
apt-get update
apt-get install ca-certificates curl
install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc
chmod a+r /etc/apt/keyrings/docker.asc

# Add the repository to Apt sources:
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/debian \
  $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
  tee /etc/apt/sources.list.d/docker.list > /dev/null
apt-get update

apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin git screen

apt-get upgrade -y && apt-get dist-upgrade -y

generate metabrainz replication token

  1. Go to https://metabrainz.org/supporters/account-type and choose your account type (individual)

  2. Then, from https://metabrainz.org/profile, create an access token, which should be a 40-character random alphanumeric string provided by the site.

musicbrainz setup

mkdir -p /opt/docker && cd /opt/docker
git clone https://github.com/metabrainz/musicbrainz-docker.git
cd musicbrainz-docker
mkdir local/compose

vi local/compose/postgres-settings.yml   # overrides the db user/pass since lidarr metadata hardcodes these values
---
# Description: Overrides the postgres db user/pass

services:
  musicbrainz:
    environment:
      POSTGRES_USER: "abc"
      POSTGRES_PASSWORD: "abc"
      MUSICBRAINZ_WEB_SERVER_HOST: "HOST_IP"   # update this and set to your host's IP
  db:
    environment:
      POSTGRES_USER: "abc"
      POSTGRES_PASSWORD: "abc"

  indexer:
    environment:
      POSTGRES_USER: "abc"
      POSTGRES_PASSWORD: "abc"
---

vi local/compose/memory-settings.yml   # set SOLR_HEAP and psotgres shared_buffers as desired; I had these set at postgres/8g and solr/4g, but after monitoring it was overcommitted and not utilized so I changed both down to 2g -- if you share an instance, you might need to increase these to postgres/4-8 and solr/4
---
# Description: Customize memory settings

services:
  db:
    command: postgres -c "shared_buffers=2GB" -c "shared_preload_libraries=pg_amqp.so"
  search:
    environment:
      - SOLR_HEAP=2g
---

vi local/compose/volume-settings.yml   # overrides for volume paths; I like to store volumes within the same path
---
# Description: Customize volume paths

volumes:
  mqdata:
    driver_opts:
      type: none
      device: /opt/docker/musicbrainz-docker/volumes/mqdata
      o: bind
  pgdata:
    driver_opts:
      type: none
      device: /opt/docker/musicbrainz-docker/volumes/pgdata
      o: bind
  solrdata:
    driver_opts:
      type: none
      device: /opt/docker/musicbrainz-docker/volumes/solrdata
      o: bind
  dbdump:
    driver_opts:
      type: none
      device: /opt/docker/musicbrainz-docker/volumes/dbdump
      o: bind
  solrdump:
    driver_opts:
      type: none
      device: /opt/docker/musicbrainz-docker/volumes/solrdump
      o: bind
---

vi local/compose/lmd-settings.yml   # blampe's lidarr.metadata image being added to the same compose; several env to set!
---
# Description: Lidarr Metadata Server config

volumes:
  lmdconfig:
    driver_opts:
      type: none
      device: /opt/docker/musicbrainz-docker/volumes/lmdconfig
      o: bind
    driver: local

services:
  lmd:
    image: blampe/lidarr.metadata:70a9707
    ports:
      - 5001:5001
    environment:
      DEBUG: false
      PRODUCTION: false
      USE_CACHE: true
      ENABLE_STATS: false
      ROOT_PATH: ""
      IMAGE_CACHE_HOST: "theaudiodb.com"
      EXTERNAL_TIMEOUT: 1000
      INVALIDATE_APIKEY: ""
      REDIS_HOST: "redis"
      REDIS_PORT: 6379
      FANART_KEY: "5722a8a5acf6ddef1587c512e606c9ee"   # NOT A REAL KEY; get your own from fanart.tv
      PROVIDERS__FANARTTVPROVIDER__0__0: "5722a8a5acf6ddef1587c512e606c9ee"   # NOT A REAL KEY; get your own from fanart.tv
      SPOTIFY_ID: "eb5e21343fa0409eab73d110942bd3b5"   # NOT A REAL KEY; get your own from spotify
      SPOTIFY_SECRET: "30afcb85e2ac41c9b5a6571ca38a1513"   # NOT A REAL KEY; get your own from spotify
      SPOTIFY_REDIRECT_URL: "http://host_ip:5001"
      PROVIDERS__SPOTIFYPROVIDER__1__CLIENT_ID: "eb5e21343fa0409eab73d110942bd3b5"   # NOT A REAL KEY; get your own from spotify
      PROVIDERS__SPOTIFYPROVIDER__1__CLIENT_SECRET: "81afcb23e2ad41a9b5d6b71ca3a91992"   # NOT A REAL KEY; get your own from spotify
      PROVIDERS__SPOTIFYAUTHPROVIDER__1__CLIENT_ID: "eb5e21343fa0409eab73d110942bd3b5"   # NOT A REAL KEY; get your own from spotify
      PROVIDERS__SPOTIFYAUTHPROVIDER__1__CLIENT_SECRET: "81afcb23e2ad41a9b5d6b71ca3a91992"   # NOT A REAL KEY; get your own from spotify
      PROVIDERS__SPOTIFYAUTHPROVIDER__1__REDIRECT_URI: "http://172.16.100.203:5001"
      TADB_KEY: "2"
      PROVIDERS__THEAUDIODBPROVIDER__0__0: "2"   # This is a default provided api key for TADB, but it doesn't work with MB_ID searches; $8/mo to get your own api key, or just ignore errors for TADB in logs
      LASTFM_KEY: "280ab3c8bd4ab494556dee9534468915"   # NOT A REAL KEY; get your own from last.fm
      LASTFM_SECRET: "deb3d0a45edee3e089288215b2d999b4"   # NOT A REAL KEY; get your own from last.fm
      PROVIDERS__SOLRSEARCHPROVIDER__1__SEARCH_SERVER: "http://search:8983/solr"
# I don't think the below are needed unless you are caching with cloudflare
#      CLOUDFLARE_AUTH_EMAIL: "UNSET"
#      CLOUDFLARE_AUTH_KEY: "UNSET"
#      CLOUDFLARE_URL_BASE: "https://UNSET"
#      CLOUDFLARE_ZONE_ID: "UNSET"
    restart: unless-stopped
    volumes:
      - lmdconfig:/config
    depends_on:
      - db
      - mq
      - search
      - redis
---

mkdir -p volumes/{mqdata,pgdata,solrdata,dbdump,solrdump,lmdconfig}   # create volume dirs
admin/configure add local/compose/postgres-settings.yml local/compose/memory-settings.yml local/compose/volume-settings.yml local/compose/lmd-settings.yml   # add compose overrides

docker compose build   # build images

docker compose run --rm musicbrainz createdb.sh -fetch   # create musicbrainz db with downloaded copy, extract and write to tables; can take upwards of an hour or more

docker compose up -d   # start containers
docker compose exec indexer python -m sir reindex --entity-type artist --entity-type release   # build search indexes; can take up to a couple of hours

vi /etc/crontab   # add to update indexes once per week
---
0 1 * * 7 root cd /opt/docker/musicbrainz-docker && /usr/bin/docker compose exec -T indexer python -m sir reindex --entity-type artist --entity-type release
---

docker compose down
admin/set-replication-token   # enter your musicbrainz replication token when prompted
admin/configure add replication-token   # adds replication token to compose
docker compose up -d

docker compose exec musicbrainz replication.sh   # start initial replication to update local mirror to latest; use screen to let it run in the background
admin/configure add replication-cron   # add the default daily cron schedule to run replication
docker compose down   # make sure initial replication is done first
rm -rf volumes/dbdump/*   # cleanup mbdump archive, saves ~6G
docker compose up -d   # musicbrainz mirror setup is done; take a break and continue when ready

lidarr metadata server initialization

docker exec -it musicbrainz-docker-musicbrainz-1 /bin/bash   # connect to musicbrainz container
cd /tmp && git clone https://github.com/Lidarr/LidarrAPI.Metadata.git   # clone lidarrapi.metadata repo to get access to sql script
psql postgres://abc:abc@db/musicbrainz_db -c 'CREATE DATABASE lm_cache_db;'   # creates lidarr metadata cache db
psql postgres://abc:abc@db/musicbrainz_db -f LidarrAPI.Metadata/lidarrmetadata/sql/CreateIndices.sql   # creates indicies in cache db
exit
docker compose restart   # restart the stack

If you've followed along carefully, set correct API keys, etc -- you should be good to use your own lidarr metadata server, available at http://host-ip:5001. If you don't have lidarr-plugin, the next section is a basic compose for standing one up.

how to use the lidarr metadata server

There are a few options, but what I recommend is running the lidarr-plugins branch, and using the tubifarry plugin to set the url. Here's a docker compose that uses the linuxserver.io image

cd /opt/docker && mkdir -p lidarr/volumes/lidarrconfig && cd lidarr

vi docker-compose.yml   # create compose file for lidarr
---
services:
  lidarr:
    image: ghcr.io/linuxserver-labs/prarr:lidarr-plugins
    ports:
      - '8686:8686'
    environment:
      TZ: America/New_York
      PUID: 1000
      PGID: 1000
    volumes:
      - '/opt/docker/lidarr/volumes/lidarrconfig:/config'
      - '/mnt/media:/mnt/media'   # path to where media files are stored
    networks:
      - default

networks:
  default:
    driver: bridge
---

docker compose up -d

Once the container is up, browse to http://host_ip:8686 and do initial set.

  1. Browse to System > Plugins

  2. Install the Tubifarry prod plugin by entering this URL in the box and clicking Install:
    https://github.com/TypNull/Tubifarry

  3. Lidarr will restart, and when it comes back up we need to revert to the develop branch of Tubifarry to get the ability to change metadata URL;

    1. Log into lidarr, browse again to System > Plugins

    2. Install the Tubifarry dev plugin by entering this URL in the box and clicking Install:
      https://github.com/TypNull/Tubifarry/tree/develop

  4. Lidarr will not restart on it's own, but we need to before things will work right -- run docker compose restart

  5. Log back into lidarr, navigate to Settings > Metadata

  6. Under Metadata Consumers, click Lidarr Custom -- check both boxes, and in the Metadata Source field enter your Lidarr Metadata server address, which should be like http://host_ip:5001 and click save. I'm not sure if a restart is required but let's do one just in case -- run docker compose restart

  7. You're done. Go search for a new artist and things should work. If you run into issues, you can check lidarr metadata logs by running
    docker logs -f musicbrainz-docker-lmd-1

Hopefully this will get you going, if not it should get you VERY close. Pay attention to the logs from the last step to troubleshoot, and leave a comment letting me know if this worked for you, or if you run into any errors.

Enjoy!


r/Lidarr • • Dec 20 '24

solved [GUIDE] Lidarr - Soularr - Slskd Automation

88 Upvotes

I have decided to post here my config and share how to make it work. There are some who have failed import problems including me but I finally solved my import problem and permission issue after so many trial and error.

Although, this automation is not perfect, I have found this easier than the other. I also have MeTube container for my backup. Below is the summary of what this automation does.

  1. You want to download music or albums from an artist, you go to Lidarr and search.

  2. Lidarr will communicate to soularr and say to slskd "Hey slskd, my buddy lidarr wants to download this, can you please check if this is available to you"

  3. Slskd will then get the message and say "I got it, I will download it if it is available"

  4. After it finishes the download, slskd will inform soularr that the download is complete.

  5. Soularr will inform lidarr that it is ready for import. Lidarr will say "Ok thank you let me save it on my music library then".

For those who have permission issue or have failed import, you need to make the PUID and GUID for both Lidarr and Soularr the same. For example, I have set PUID 99 and GUID 100 for Lidarr, you need to set also in Soularr PUID 99 and GUID 100.

I'm using Unraid and below is my config.

Lidarr => Lidarr unraid config (I'm using LSIO)

Soularr => soularr unraid config (There's no template for unraid, you need to create on your own by going to Docker > Add Container

Slskd => slskd unraid config

Soularr-lidarr connection (config.ini) => config.ini

Soularr-slskd connection (config.ini) => config.ini

I hope this helps. Let me know if you have questions.


r/Lidarr • • Mar 10 '26

unsolved How to Prevent Lidarr From Downloading Ultra Mega Fuck You Deluxe Album Every Time?

77 Upvotes

I recently set up a media server for my family. I'm using slskd + lidarr +soularr. I've never had issues finding the albums I want, but it's getting incredibly annoying when I request an album like Mellon Collie, and instead of just giving me the 24 tracks I want, Lidarr decides I want the 96 or 110 track version of the album, then never finds it, and thus never imports it.

The point is automation, so I'm finding it a bit annoying to have to go babysit every. single. release I request.


r/Lidarr • • Aug 29 '25

discussion Dream turned into a Nightmare

76 Upvotes

I had a dream last night that Lidarr was fixed and running better than ever. I ran to my computer and realized it was a nightmarr.


r/Lidarr • • Dec 10 '25

discussion Completely Broken, Change is Needed

72 Upvotes

The devs have broken their own tool and have basically left the community to resolve their problem.

The Metadata server they force us to use has not worked in months. The devs do not allow natural way to change away from their specific server without "hacking" your build in some manner via plugins or scripts.

When questions are asked they have the audacity to say, "use the MusicBrainz ID instead". Well if you copy paste the "lidarr:##", it still doesn't work.
To be clear, I am not talking about not finding downloads via indexers. I am talking strictly just trying to add an artist to the library for monitoring comes up empty all the time.

I have done a clean bare-metal reinstall. I have run a docker image. Nothing works from the official channels. The fact that everyone points to plugins or alternative branches of the project shows this. The official subreddit for a tool should not be full of hacks and alternative 3rd party forks of the tool to make things works.

I am not attacking the devs work, I am sure they work hard. They need to admit they don't have an answer for the issues caused by their own Metadata server and let us properly change it somehow without having to rely on yet another 3rd party tool. The fact that nothing comes up when looking for an artist or an album hours after they said it should be back up is proof of this.

Edit: Since someone didnt like my use of the word "forced", I mean that it is the only option unless you go out of your way to change it. Lidarr is presented as a tool that should work for managing media out of the box. One should not have to download a new tool and then go in and start adding 3rd party components to have it work from the get-go

Edit2: I wanted to clarify a few things, I have a separate working instance of lidarr using plugins. My issue is not that this not work for me. I am using a separate install presented on the offical webpage as my basis of what is not working though. My issue is that the official standard install seems to break constantly for just adding artists, not talking at all about indexers or getting the actual music. Just literally being able to hit "Add New" and actually adding it to my pool of artists. The community has seemingly said that this is fine and that they will point their metadata server to something else than the official one.

This was a fine answer, months ago, when we were told it would be resolved and used as a temporary workaround. Currently however this should not be the "new standard" to download a community tool, then hack it to function as you would expect it to out of the box. If you are brand new to Lidarr one should not have to join a discord or search through forums to find out that everyone else is just modifying their build to have it be functional. Someone new to Lidarr should also not be expected to know that the "dev" branch is the apparently the only functional version of the tool, as I have been DMed to change over to that by multiple people at this point. A new user is not going to know about of these issues, especially because the official webpage makes no mention of any issues. You are expected to hit a wall and go debug it and find this out via the community.

What I am asking for is just a native way to change that server since the current coded Metadata server is the biggest problem in this. Maybe even a notice on the offical web portal that says something, anything about these issues at all.


r/Lidarr • • Jan 18 '26

discussion The Plugin branch will be no more

68 Upvotes

I don't know if anyone cares, but some Docker users will need to update their containers in the future.

The plugin branch is no longer maintained and has been merged onto nightly. It will soon reach develop and master.

Plugins are now enabled by default on Lidarr 🎉


r/Lidarr • • Dec 02 '25 Bravo

discussion The Free, Clunky Music Helper for Lidarr You Never Knew You Don't Need: Part 3

67 Upvotes

Alright, look. I know what you're thinking: "Another update? Really?" (And sorry if I broke some instances yesterday and today).

Just to be clear I will not add anything new for the ones that used develop. Yes this time I just pushed everything from develop into master.

So here we are again with Tubifarry, the Lidarr plugin that started as a "simple" YouTube downloader and somehow evolved into... whatever this is now.

What's really new?

Nothing if you tested develop

Some web clients:

  • Lucida, DABmusic, and Subsonic

If a service supports Subsonic, congrats, you can probably use it like with HiFi.

Lyrics? 📜
Want synced lyrics with your music? Of course you do not. But still, Tubifarry can fetch them.

Custom Metadata Sources 🧩
MusicBrainz is great, but sometimes it's missing info. Now you can pull additional metadata from Discogs and Deezer, but don't build your library with it, that will probably go wrong. Just add it to MusicBrainz if you miss something!

MetaMix
The crown jewel of overthinking. It combines albums from multiple sources to add missing ones. If MusicBrainz is missing something, it'll grab it from Discogs or Deezer. It's like metadata Frankenstein and also feels like it.

Similar Artists 🧷
Search for an artist with a ~ prefix (e.g., ~Pink Floyd) and get a list of similar artists from Last.fm. Because I like tinkering with things that have no use case.

Plus All the Old Stuff:

  • YouTube downloads (still janky)

  • Slskd integration for Soulseek

    • (Yeah Soularr and SoulSync are there too no need for this I know)

  • Soundtrack fetching from Radarr/Sonarr

  • Codec Tinker for audio conversion

  • Queue Cleaner for handling failed imports

Why Should You Care?

  • Still free (no Tidal/Deezer/Qobuz subscription required)

  • More download sources than you probably ever need

  • Metadata from multiple places because why not

  • Lyrics support for your karaoke dreams, but LrcGet does not implement enhanced lyrics so no way you can use it for karaoke

  • Automated searching so you can be lazy. I have no clue how to set up the external search applications, so sorry for that.

The Catch?

It's more complex now. Way more. And honestly, you probably don't use any of the features. But they're there if you want them. Or don't. I'm not your boss.

Should You Use It?

( ̄﹏ ̄;)

Probably not and as long as you're happy with your current setup, stick with that.

Repo link: Tubifarry on GitHub

Enjoy! Or don't. 🎧


r/Lidarr • • Aug 19 '25

discussion Sync YouTube playlists with Lidarr using Youtubarr

64 Upvotes

Hey r/Lidarr folks,

I’ve been working on a tool called Youtubarr that lets you sync YouTube (Music) playlists directly into Lidarr as import lists. Only Spotify and some other providers offer native Lidarr connectors, but since I am a Youtube Music user, I decided to build this.
Youtubarr is a small Django app that fetches your YouTube playlist’s artists and creates a feed that Lidarr can consume.

Here some features:

  • Supports public and unlisted playlists via API key

  • Sync your Liked Music (LM) playlist (playlist ID is LM)

  • Comes with Docker (+ Compose) for easy deployment

  • UI to manage playlists, blacklist items, and see MusicBrainz IDs

You can find the GitHub repository and instructions here: https://github.com/DireDireCrocs/Youtubarr

I'm open for feedback and feature requests! The setup process is a bit manual due to getting API keys from the Google Cloud Platform.

If for some reason this post is against rules, please remove it.


r/Lidarr • • Sep 17 '25

discussion Spotify -> Lidarr Fix

59 Upvotes

I got tired sitting around and trying to get the Spotify list to import, so I made a small python project here: https://github.com/jackedtechbro/mbid_to_lidarr

Bring your own list of artists as artists.txt, set up your the .env file, and this app will get the Musicbrainz ID of the artist and add it to your Lidarr instance

note: this is not a warming script. This is just a workaround for importing artists

also just for fun: SUMMARY ADDED=198, EXISTS=87, LOOKUP_ERROR=421, ADD_ERROR=0, DRY_RUN=0

out of ~800 artists, I got 421 artists that hit a 503 error in Lidarr. That cache is building, but maybe I listen to a lot more obscure artists


r/Lidarr • • Aug 28 '25

discussion So excited to hear the metadata server is being rebuilt

59 Upvotes

What are some alternatives people are using while they wait? I’ve been using Spotizerr to rip all of my Spotify playlists before I cancel my subscription. Kinda tedious buts working. Have it setup on a separate machine to avoid messing with my Servarr install on my NAS


r/Lidarr • • Jan 02 '18

Development Update - Dec 2017

57 Upvotes

First we would like to thank all of our supporters that have donated to Lidarr, contributors that have submitted code, and all of our testers who continue to help us identify bugs and issues.

We appreciate all of you and wanted to give a quick update to everyone on recent development as well as upcoming plans. We have been hard at work for the last 8 months in getting this project off the ground and we are proud to say that we have a somewhat functional result. As you all know we have deviated slightly from Sonarr/Radarr and have based Lidarr on the Sonarr V3 work (Thanks especially to the the Sonarr Team). In the last 2 months we have pushed 87 commits to develop branch and made 30,287 line changes. Some of the more prominent developments are:

  • Metadata Profiles

  • Extended Qualities and Quality Grouping

  • In-App Updates (Use "nightly" channel to get dev channel updates as they are committed and built)

  • Functional Metadata Server (https://github.com/lidarr/LidarrAPI.Metadata)

  • Ability to cancel bulk import lookup at any point

  • Working Extras Files (Kodi/Emby metadata)

  • Kodi library notifications

  • Headphones and Gazelle (RED/Apollo) Indexer support

Though we still have a long way to go, we feel we are getting closer to a beta release every day. Current blockers to beta that we want to get implemented are:

  • Robust Track Parsing and Identification

  • Better initial metadata release picking for Albums

  • Manual user album release selection

  • Search and add by album

Thus these are the issues we will be putting most of our time to over the next few weeks. Additionally, we have uploaded a website on Lidarr.audio which was forked from the Sonarr/Radarr site (Thanks again guys).

We wish everyone a happy new year and we hope to have a beta out Soon™ (Unless of course someone else asks when it will be) Feel free to hit us up on discord with questions or contributions. Thanks again to everyone supporting us!