feat: Added music support through Lidarr

[0-Pierre]

Description

Jellyseerr fully support music trough Lidarr 🚀 🎵

Metadata
We’re using the Lidarr API (api.lidarr.audio) to improve speed, as MusicBrainz (MB) often suffers from high latency and server overload issues.
Trade-off: The results are slightly less precise compared to the MB Search API.

Overview
The overview section pulls data from Wikipedia, ensuring multilingual support for more flexible and accurate descriptions.

Image Handling
Images are initially loaded from the provided links and cached locally.
The Lidarr API offers additional artist images that aren’t available in the Cover Art Archive (CAA).
If an image is missing, the system automatically falls back to CAA.

Caching
By default, images from CAA and Fanart are cached locally, as these sources tend to load slowly.
Cached images are stored in the /cache folder and can be cleared via the settings page using a dedicated job.
Other images are only cached if specific options are enabled.

Similar Artists / Trending
We use the ListenBrainz API to provide recommendations for similar artists and trending music. Missing images are completed through the Lidarr API, with a fallback to CAA.

Artist Groups
The /group endpoint is dedicated to artist groups (bands). For individual artists (persons), we merge data with the /person endpoint from TMDb to avoid duplicate entries.

Informations Points
There are cases where images aren’t available on either the CAA or the Lidarr API. In such instances, we need to upload them to the MusicBrainz database to ensure they are displayed. This aligns with the core purpose of MusicBrainz, a community-driven platform for sharing metadata.
For this reason, I’ve removed Deezer as a fallback. Encouraging community contributions is more in line with MusicBrainz’s philosophy. Additionally, using Deezer’s fallback wasn’t always reliable, as the matching wasn’t based on precise IDs, though it worked correctly about 95% of the time.

Screenshot (if UI-related)

To-Dos

• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Issues Fixed or Closed

• Closed:[Feature Request] Music / Audio support #96

[github-actions]

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

[gauthier-th]

@0-Pierre do not merge develop into this PR. Rebase on develop instead.
Merging develop is a very bad practice, it makes things harder for us to review and later to track changes.
It is written as well in our contribution guide.

Could you please rebase and remove all theses merge commits?

[0-Pierre]

@0-Pierre do not merge develop into this PR. Rebase on develop instead. Merging develop is a very bad practice, it makes things harder for us to review and later to track changes. It is written as well in our contribution guide.

Could you please rebase and remove all theses merge commits?

Apologies, I'm not very familiar with the GitHub processes and features. I'll do my best, but the first commit was automatically created during a rebase when I used the "Rebase current branch..." option.

[fallenbagel]

A preview for this feature is available as preview-music-support tag.

(In about 15-20 mins)

[AlessandroTischer]

Hi! I briefly tested the PR. Great work!
Some feedbacks (Warning! I'm quite a noob, so they might be wrong or due to inexperience):

1. If Jellyseerr is already configured and you try to request any kind of music related content, you get a generic error. The fact that Lidarr was not configured should have been highlighted in the popup error, in my opinion.
2. If an album doesn't have a cover, it is shown as it is hovered with the mouse, I think it's a bit odd.
3. When an album is displayed, it contains a certain number of tracks (I suppose disk 1). When it is then selected in Lidarr, it might contain a whole lot of other tracks. You can test with Green Day - American Idiot: in Jellyseerr 13 tracks are listed, in Lidarr they are 57.
4. There is no filter in the music panel. Is this just because it wasn't implemented yet or are there problems?
5. If an artist is not monitored in Lidarr and I request an album from said artist, the artist gets added, and it takes a lot (>1 min, nothing unbearable, but I noticed it) before the album is monitored and then searched. Is this wanted for any reason?

Thank you again for the work!

[0-Pierre]

Hi! I briefly tested the PR. Great work! Some feedbacks (Warning! I'm quite a noob, so they might be wrong or due to inexperience):

1. If Jellyseerr is already configured and you try to request any kind of music related content, you get a generic error. The fact that Lidarr was not configured should have been highlighted in the popup error, in my opinion.
2. If an album doesn't have a cover, it is shown as it is hovered with the mouse, I think it's a bit odd.
3. When an album is displayed, it contains a certain number of tracks (I suppose disk 1). When it is then selected in Lidarr, it might contain a whole lot of other tracks. You can test with Green Day - American Idiot: in Jellyseerr 13 tracks are listed, in Lidarr they are 57.
4. There is no filter in the music panel. Is this just because it wasn't implemented yet or are there problems?
5. If an artist is not monitored in Lidarr and I request an album from said artist, the artist gets added, and it takes a lot (>1 min, nothing unbearable, but I noticed it) before the album is monitored and then searched. Is this wanted for any reason?

Thank you again for the work!

@AlessandroTischer Hey! Thanks for your notes, here's some points :
1- I'm fairly certain that the exact same behavior applies to Movies and Shows with Sonarr and Radarr
2 - The behavior is consistent across Movies and Show cards without covers, but missing covers are more frequent for Music, making it more noticeable. I can implement a fix to prevent the 'hovered' style from being applied to any card (Movies, TV, or Music) when a cover is missing.
3 - This occurs because I haven't configured the same release selection method used by Lidarr, such as choosing the best metadata or the most recent release. The current implementation is still very basic.
4 - Exactly, I’ve only configured the sorting options and nothing beyond that.
5 - Here's how the system currently works: if the artist doesn't already exist, it's first created in Lidarr without monitoring any of their albums. We then give Lidarr time to fetch all the metadata for the artist's discography. After about 40 seconds, the requested album is set to monitored. If multiple requests come in quickly, the system waits 30 seconds between each new request and checks at the end if all the requested albums are now monitored. It’s a very basic and somewhat crude solution, but it works. Without this process, I was encountering errors and unmonitored albums when users spammed requests. It can definitely be improved in the future, but for now, I prioritized getting a stable and reliable solution in place quickly.

On my end, I’m using it in production with all my users, and so far, I haven’t encountered any major bugs or errors causing server crashes. I’ll continue monitoring the logs. 👀 🔥

[gssariev]

Hey, @0-Pierre just popping by to say awesome work! It's fun to finally be able to play around with music requests, even though it's just a preview. Sharing some additional feedback as a Plex/Jellyseerr user:

• No music library(s) syncing - in the initial setup process, only the movie and series type libraries are visible making it impossible to sync what music is currently available with Jellyseerr
• Requesting an album by a monitored artist throws an error in Lidarr:

LidarrErrorPipeline Invalid request Validation failed: -- ForeignAlbumId: This album has already been added. LidarrErrorPipeline FluentValidation.ValidationException: Validation failed: -- ForeignAlbumId: This album has already been added.: Validation failed: -- ForeignAlbumId: This album has already been added.

Unmonitoring either the artist/album and making the request again results with the same error. The only work around that I've found so far is to remove the artist altogether from Lidarr and request it again. That way, it get added to Lidarr the way you described above; however, the following is observed:

• Artist is unmonitored
• Album is monitored
• Download starts
• Download is stuck at importing and after roughly 2-3 min requires manual import

Additionally, the artist gets added to Lidarr without a metadata profile; unsure if that is expected behavior. For context, I am running everything on Windows 11 and have tried using both the official Lidarr service as well as with ghcr.io/hotio/lidarr:pr-plugins, both experiencing the same.

Once again, thanks for putting in the work and time to make this!

[0-Pierre]

Hey, @0-Pierre just popping by to say awesome work! It's fun to finally be able to play around with music requests, even though it's just a preview. Sharing some additional feedback as a Plex/Jellyseerr user:

• No music library(s) syncing - in the initial setup process, only the movie and series type libraries are visible making it impossible to sync what music is currently available with Jellyseerr
• Requesting an album by a monitored artist throws an error in Lidarr:

LidarrErrorPipeline Invalid request Validation failed: -- ForeignAlbumId: This album has already been added. LidarrErrorPipeline FluentValidation.ValidationException: Validation failed: -- ForeignAlbumId: This album has already been added.: Validation failed: -- ForeignAlbumId: This album has already been added.

Unmonitoring either the artist/album and making the request again results with the same error. The only work around that I've found so far is to remove the artist altogether from Lidarr and request it again. That way, it get added to Lidarr the way you described above; however, the following is observed:

• Artist is unmonitored
• Album is monitored
• Download starts
• Download is stuck at importing and after roughly 2-3 min requires manual import

Additionally, the artist gets added to Lidarr without a metadata profile; unsure if that is expected behavior. For context, I am running everything on Windows 11 and have tried using both the official Lidarr service as well as with ghcr.io/hotio/lidarr:pr-plugins, both experiencing the same.

Once again, thanks for putting in the work and time to make this!

@gssariev Thank you for your tests! I actually haven't tested it in a Plex setup situation yet. I'll review all the issues you reported and will get back with a commit to fix them. 😉

[mr2toyou]

@0-Pierre great work so far, I was hoping one day we would get this added. Some items I am seeing so far;

Running in docker with emby
Settings -> Emby -> Emby libraries, music library missing
Manage music /Manage Album showing [object Object] instead of Artist
clearing data from lidarr only available after going to requests.
2025-01-14T23:01:34.912Z [error][Media]: [Lidarr] Failed to remove album: 404 Not Found

"play on" not showing for available media player

[github-actions]

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

[fallenbagel]

You should only have the en.json using the pnpm i18n:extract for the i18n locales. The rest of the translation strings should be updated through weblate.

Could you remove those translation files and rebase?

[0-Pierre]

You should only have the en.json using the pnpm i18n:extract for the i18n locales. The rest of the translation strings should be updated through weblate.

Could you remove those translation files and rebase?

Sure, i'm fixing all the requested issues and I'll take care of that 👍

[0-Pierre]

@gssariev Hello! I'll be pushing a new commit that resolves all the Plex-related issues. However, I'm having trouble reproducing your other issues, as everything seems to be working perfectly on my end — requests are sent and downloaded properly. I even set up a Plex test server, and everything is running smoothly with the same Docker version you're using.

I've also implemented proper mapping for the Plex music library since Plex doesn't handle it like other libraries. They rely solely on release IDs, so we’re now mapping those to release-group IDs to ensure the database gets the correct entries. Gotta love Jellyfin for handling things more consistently in this area, lol.

Let me know if you encounter any additional issues!

[gssariev]

@gssariev Hello! I'll be pushing a new commit that resolves all the Plex-related issues. However, I'm having trouble reproducing your other issues, as everything seems to be working perfectly on my end — requests are sent and downloaded properly. I even set up a Plex test server, and everything is running smoothly with the same Docker version you're using.

I've also implemented proper mapping for the Plex music library since Plex doesn't handle it like other libraries. They rely solely on release IDs, so we’re now mapping those to release-group IDs to ensure the database gets the correct entries. Gotta love Jellyfin for handling things more consistently in this area, lol.

Let me know if you encounter any additional issues!

Excited to test it out and will report any finding once available! The Lidarr issue could also be something on my end...

[gssariev]

@0-Pierre I built the image from your repository (unsure if that's the best approach), and I can confirm that my Music library does get detected and everything is being synced up, and is reflected in Jellyseerr. From the logs, I can also see that it correctly identifies some of my music as not having a MusicBrainz ID, which I expected as that music doesn't have an entry in their database - all good here.

When it comes to Lidarr...it's a bit of a mixed bag and I think the issues mainly stem from the ghcr.io/hotio/lidarr:pr-plugins version I am running with https://github.com/TrevTV/Lidarr.Plugin.Tidal plugin. The request go through if the artist is not present in the Lidarr database and take a long time to get imported (like maybe 5+ min); however, no download is initiated for albums of artists that are already being monitored/are in the Lidarr database. If I manually trigger the search from within Lidarr, everything runs smoothly and music gets imported quickly.

Running the official Lidarr service, with a bunch of indexers, seems to work better and is more consistent with what you described (initial delay of X seconds, unmonitored album, etc.); however, if the album requested is already monitored, the request screen gets stuck in a loop, but I get the same message as you in the logs and nothing else:

2025-01-16 18:20:33 jellyseerr-lidarr | 2025-01-16T17:20:33.898Z [info][Notifications]: Sending notification(s) for MEDIA_AUTO_APPROVED {"subject":"Unsainted (2019)"} 2025-01-16 18:20:33 jellyseerr-lidarr | 2025-01-16T17:20:33.985Z [info][Lidarr]: Album already exists in Lidarr, monitoring it in Lidarr {"albumTitle":"Unsainted","mbId":"924ff4f6-f0b9-4cfe-ab28-cb80a164e440"}

Ultimately, the request doesn't go through in that case. If I restart the container I can see it displayed as 'pending'.

[flo1t]

Hi @0-Pierre. Thanks for you great work!

I've just set it up, but all my requests are failing with the error "Metadata profile does not exist":
2025-01-16T17:17:45.652Z [error][Lidarr]: Failed to add album to Lidarr {"options":{"mbId":"a3159fb4-2ad3-4678-ba51-36fbc8b8430d","foreignAlbumId":"a3159fb4-2ad3-4678-ba51-36fbc8b8430d","title":"From Zero","qualityProfileId":4,"profileId":4,"metadataProfileId":4,"rootFolderPath":"/music","monitored":false,"tags":[],"searchNow":false,"images":[{"url":"/MediaCoverProxy/18914127a38bfd109faaebb359c3ce62836629c03ec646ee9802a0decbb85c10/from-zero-66db0c50877a9.jpg","coverType":"cover","extension":".jpg","remoteUrl":"http://assets.fanart.tv/fanart/music/f59c5520-5f46-4d2c-b2c4-822eabf53419/albumcover/from-zero-66db0c50877a9.jpg"},{"url":"/MediaCoverProxy/ee31fb45ac89c03626fafcd1c36de64bb5e78c7279e5851651c9e6b27ee067b1/40742283189-1200.jpg","coverType":"disc","extension":".jpg","remoteUrl":"https://imagecache.lidarr.audio/v1/caa/4a32e308-fbd4-4643-a419-ee90a2ee5b40/40742283189-1200.jpg"}],"addOptions":{"monitor":"none","monitored":false,"searchForMissingAlbums":false},"artist":{"foreignArtistId":"f59c5520-5f46-4d2c-b2c4-822eabf53419","artistName":"Linkin Park","qualityProfileId":4,"metadataProfileId":4,"rootFolderPath":"/music","monitored":false,"monitorNewItems":"none"}},"errorMessage":"400 Bad Request: [\n {\n \"propertyName\": \"Artist.MetadataProfileId\",\n \"errorMessage\": \"Metadata profile does not exist\",\n \"attemptedValue\": 4,\n \"severity\": \"error\",\n \"errorCode\": \"MetadataProfileExistsValidator\",\n \"formattedMessageArguments\": [],\n \"formattedMessagePlaceholderValues\": {\n \"propertyName\": \"Artist. Metadata Profile Id\",\n \"propertyValue\": 4\n }\n }\n]"}

As I've just setup lidarr and I'm new to it, it might could just be a configuration issue within lidarr.

Edit: It works, when I select the quality profile "Any", but not with any other profile.

[TiddlyQwert]

Just wanted to leave a comment that I am running this PR without any issues. Everything seems to work, just waiting for Lidarr to fix their metadata issues which should hopefully be soon. Will continue to run this PR and watch for issues. Excited to see this officially added. https://www.reddit.com/r/Lidarr/comments/1ktitdq/searching_for_new_artists_failedunable_to/?sort=new

[schmitzkr]

looks like lidarr has fixed things...
Lidarr/Lidarr#5498 (comment)

[putergod]

looks like lidarr has fixed things... Lidarr/Lidarr#5498 (comment)

No they haven't. I've been getting a lot of these failures today, and even using the MB ID has only been 50% successful.

[yroyathon]

looks like lidarr has fixed things... Lidarr/Lidarr#5498 (comment)

No they haven't. I've been getting a lot of these failures today, and even using the MB ID has only been 50% successful.

Not to get too far off topic here, but Lidarr has rolled out the fix to their metadata servers. They have to ease into it (currently only 1% of un-cached requests goto the new servers) and build up the metadata cache, or the millions of lidarr requests will bring the new servers down. So the fix is in production, it's just going to take some weeks/months of building up the cache before they can crank the lever up to 100%. More artists and albums get added to the cache every hour, so it's just a matter of time. Hitting Refresh Artists in your Lidarr tasks a few times a day will help get Your artists/albums in the cache sooner, but still expect that to take a few weeks. Otherwise it will still happen just less often, as Lidarr automatically does that task once a day.

[Lain2077]

hi, here to say the same thing as Tiddly. using it without any issues except covers not being loaded which I suspect is because it relies on lidarr's metadata service (and 32bit int bug on permissions), . I have an external metadata provider and the request pipeline is a smooth as it can get. Could be nice to actively separate each section for a search considering Music is now flooding Movies/Series and vice versa.

[zapteryx]

It seems that under the global/default permissions for users, I'm unable to select Request Music or Auto-Request Music. However, when selecting the generic parent Request checkbox, all request checkboxes including the music checkbox are selected. Same situation with Auto-Request. Is anyone able to replicate this?

I am using the fallenbagel/jellyseerr:preview-music-support tag for context.

Edit: It also seems that on the search page, all results have their images re-requested on every render

I have a fix for the permission issue here! :)

https://github.com/zapteryx/jellyseerr/tree/lidarr

Looks like the new permissions went past the 32-bit integer limit and caused the bitwise operations to fail.

(also PR'd the fix into 0-Pierre's repo in the meantime)

Permissions issue is fixed here ^

[vayan]

With the changes we recently made to the cache ttl and some other improvements, we're now up to 97% of our API hits going to the cache first. Some number of those are stale and still hitting the metadata server, but this is right where we want it to be.

Lidarr/Lidarr#5498 (comment)

They are back up to 97% hits on MBID searches now 🙏

[kimicake]

From what I've read there doesn't seem to be any separation between music searches and movie/TV searches, is that something that's planned?

[losthymns]

I built and deployed an docker instance of Jellyseerr from the preview-music-support tag about a week ago, and it was working well for the first few days. However, for the last few days the Popular Artists and Albums sections in the Discover tab are empty, as is the Music tab. I don't see any errors in the logs. I've restarted the instance (with a persistent /app/config). I've replicated the behaviour in both Firefox and Chrome, including private browser sessions. Interestingly, in the browser dev tools I can see that the requests to the /music endpoint are returning 200 OK with results. So the problem seems to be with rendering, not the API itself.

Quick followup: I search for a specific artist or album, I get relevant search results and can request them successfully. It's just the discovery tab and music tab that that aren't working correctly.

Ever figure this out? Same thing is happening to me.

Is there something wrong with my config? Why doesn't the music tab show a single thing, or is this expected behavior at this point?

[dnlrsr]

I built and deployed an docker instance of Jellyseerr from the preview-music-support tag about a week ago, and it was working well for the first few days. However, for the last few days the Popular Artists and Albums sections in the Discover tab are empty, as is the Music tab. I don't see any errors in the logs. I've restarted the instance (with a persistent /app/config). I've replicated the behaviour in both Firefox and Chrome, including private browser sessions. Interestingly, in the browser dev tools I can see that the requests to the /music endpoint are returning 200 OK with results. So the problem seems to be with rendering, not the API itself.

Quick followup: I search for a specific artist or album, I get relevant search results and can request them successfully. It's just the discovery tab and music tab that that aren't working correctly.

Ever figure this out? Same thing is happening to me.

Is there something wrong with my config? Why doesn't the music tab show a single thing, or is this expected behavior at this point?

Can't reproduce. Only Music DB is missing in slider config, but I think this will come later. The existing sliders (album...) are working as expected.

But guys this is still WIP. Don't expect something to work as expected. You are on a feature/dev branch and by definition they can break. Wait for offical release and then report bugs.

[languagegame]

Minor bug. When managing Jellyseerr user permissions, if the Manage Requests permission is added to a user, that user is also supposed be granted Auto-Approve, Auto-Approve Movies, Auto-Approve Series, and Auto-Approve Books. However, at least on Chrome, it does not automatically add Auto-Approve Music, so the user still has to manually add that one whereas all the other auto-approve permissions were granted automatically.

[arukaraz]

Current state of the metadata server

• Everything seems to be back up. Servers are handling the load.
• We have disabled Spotify lists for now. We will bring them back online soon.
• We have removed the block on scripts, though there should not be a need for them now.
• The process to get updates from Musicbrainz is a few hours behind the normal schedule.
  In short, if you have been patient like we asked you to be, you can now jump back in. Thank you for your patience, we appreciate you!

Lidarr/Lidarr#5498 (comment)

[Pachinko0]

Current state of the metadata server

• Everything seems to be back up. Servers are handling the load.
• We have disabled Spotify lists for now. We will bring them back online soon.
• We have removed the block on scripts, though there should not be a need for them now.
• The process to get updates from Musicbrainz is a few hours behind the normal schedule.
  In short, if you have been patient like we asked you to be, you can now jump back in. Thank you for your patience, we appreciate you!

Lidarr/Lidarr#5498 (comment)

I came straight the moment i read this.
Its so exciting! Hopefully we can get lidarr support with latest versions 🙌🏻

[elmpp]

Just for the avoidance of doubt here, this isn't expected to work with readarr at all (albeit an instance set up for audiobook-only management)?

This PR seems to support successfully adding the readarr instance (non-default in my case), searching and other actions right through to the actual (failing) request action

---

Otherwise, already very thankful for the lidarr support. Works well in my limited testing 👏

---

E2A i see another ebook support PR

[yroyathon]

I've been so happy that Lidarr has been returned to most of its functionality, that I forgot about this for a moment. I successfully requested an album with Jellyseerr, and it was grabbed and imported via Lidarr. Woo!

Just curious, what are the road blocks in getting this very functional PR merged to the main branch here?

[cociweb]

I hope this will be the first thing after the jellyseerr and overseerr merge into seerr.... @sct what is your opinion?

[janstadt]

This looks great. What is the status of getting this mainlined?

[Pachinko0]

If this works indeed please get it Rebased at least with the latest changes, its a NEED!
I think it will be easier for them to merge it once they migrate to Seer entirely.

@0-Pierre

[SpawnInsane]

I have been running this build with no problems for the last 4 months. It's ready to go imo.

[janstadt]

I have been running this build with no problems for the last 4 months. It's ready to go imo.

Just curious, I presume you built your own image based off of this branch? If not, is there an image floating around that someone could pull to test this out?

[baudneo]

From this thread, there is this image tag -> fallenbagel/jellyseerr:preview-music-support

[janstadt]

From this thread, there is this image tag -> fallenbagel/jellyseerr:preview-music-support

Excellent. Thanks @baudneo.

[SirWobbyTheFirst]

Still a time frame for merging would be nice, I'm waiting for this and the SSO integration to be merged before I can deploy jellyseer.

[foozalex]

It’s free software so please just be patient. They don’t owe you anything. Maybe this will never be merged and that’s fine.

[addisonbabcock]

Also a gentle reminder that everytime you comment on a Github PR it emails everyone who has participated or followed that PR. So let's keep the comments relevant to the code and not a bunch of "me too!" spam, please.

[QuixThe2nd]

Super excited to learn Lidarr integration is being worked on! I setup a fresh install of the preview-music-support image and /discover/music throws an HTTP 500. Could this be a misconfiguration on my end?

https://jellyseerr.yazdani.au/api/v1/discover/music?page=1&days=7 is throwing:

{"message":"Unable to retrieve fresh music releases."}

From Docker logs:

jellyseerr  | 2025-11-08T02:32:08.563Z [error][API]: Failed to retrieve fresh music releases {"error":"fetch failed","stack":"TypeError: fetch failed\n    at node:internal/deps/undici/undici:13502:13\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async ListenBrainzAPI.get (/app/dist/api/externalapi.js:55:26)\n    at async /app/dist/routes/discover.js:590:35"}
jellyseerr  | Warning: data for page "/discover/music" is 264 kB which exceeds the threshold of 256 kB, this amount of data can reduce performance.
jellyseerr  | See more info here: https://nextjs.org/docs/messages/large-page-data
jellyseerr  | 2025-11-08T02:32:09.786Z [error][API]: Failed to retrieve fresh music releases {"error":"fetch failed","stack":"TypeError: fetch failed\n    at node:internal/deps/undici/undici:13502:13\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async ListenBrainzAPI.get (/app/dist/api/externalapi.js:55:26)\n    at async /app/dist/routes/discover.js:590:35"}
jellyseerr  | 2025-11-08T02:32:15.752Z [error][API]: Failed to retrieve fresh music releases {"error":"fetch failed","stack":"TypeError: fetch failed\n    at node:internal/deps/undici/undici:13502:13\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async ListenBrainzAPI.get (/app/dist/api/externalapi.js:55:26)\n    at async /app/dist/routes/discover.js:590:35"}
jellyseerr  | 2025-11-08T02:32:26.773Z [error][API]: Failed to retrieve fresh music releases {"error":"fetch failed","stack":"TypeError: fetch failed\n    at node:internal/deps/undici/undici:13502:13\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async ListenBrainzAPI.get (/app/dist/api/externalapi.js:55:26)\n    at async /app/dist/routes/discover.js:590:35"}
jellyseerr  | 2025-11-08T02:32:33.007Z [error][API]: Failed to retrieve fresh music releases {"error":"fetch failed","stack":"TypeError: fetch failed\n    at node:internal/deps/undici/undici:13502:13\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async ListenBrainzAPI.get (/app/dist/api/externalapi.js:55:26)\n    at async /app/dist/routes/discover.js:590:35"}

[M0NsTeRRR]

Closed in favor of #2132 as discussed with the author of this PR.

Please use this discussion #2160 as a place to discuss testing / questions related to the work-in-progress Music support feature. This will allow the PR #2132 comments to be used for code review instead of general discussion.