Plugins AudioDB and MusicBrainz keep re-appearing by themselves? #1714

New Issue

OVERLORD · 2026-02-06T21:16:55+03:00

OVERLORD commented

2026-02-06 21:16:55 +03:00

Originally created by @Gabriel-p on GitHub (May 21, 2020).

Describe the bug
A few days ago I noticed these two plugins, AudioDB and MusicBrainz, installed in my Jellyfin server. I removed them since I had never installed them in the first place. Today I noticed they are back. These are not even listed in the catalog of available plugins.

Uninstalling these plugins results in the log messages shown below.

System (please complete the following information):

OS: elementary OS 5.1.4 (based on Ubuntu 18.04.4 LTS)
Virtualization: [e.g. Docker, KVM, LXC]
Clients: Browser
Browser: Chrome 83.0.4103.61 (Build oficial) (64 bits)
Jellyfin Version: 10.5.5
Playback: [Direct Play, Remux, Direct Stream, Transcode]
Installed Plugins: None?
Reverse Proxy: [e.g. none, nginx, apache, etc.]
Base URL: [e.g. none, yes: /example]
Networking: [e.g. Host, Bridge/NAT]
Storage: [e.g. local, NFS, cloud]

Expected behavior
No plugins should be installed without my permission/acceptance?

Logs

[2020-05-21 12:10:16.904 -03:00] [INF] Deleting plugin directory "/usr/lib/jellyfin/bin"
[2020-05-21 12:10:17.126 -03:00] [ERR] Error processing request: "Access to the path '/usr/lib/jellyfin/bin' is denied". URL: "http://127.0.0.1:8096/Plugins/a629c0da-fac5-4c7e-931a-7174223f14c8"
[2020-05-21 12:10:57.256 -03:00] [INF] WS "http://127.0.0.1:8096/socket?api_key=f7b6ce7e8f2e46e69e183ef8594f8e7b&deviceId=TW96aWxsYS81LjAgKFgxMTsgTGludXggeDg2XzY0KSBBcHBsZVdlYktpdC81MzcuMzYgKEtIVE1MLCBsaWtlIEdlY2tvKSBDaHJvbWUvNzkuMC4zOTQ1LjEzMCBTYWZhcmkvNTM3LjM2fDE1Nzk0ODIzNDY5MzA1". UserAgent: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36"
[2020-05-21 12:11:01.984 -03:00] [INF] Deleting plugin directory "/usr/lib/jellyfin/bin"
[2020-05-21 12:11:02.155 -03:00] [ERR] Error processing request: "Access to the path '/usr/lib/jellyfin/bin' is denied". URL: "http://127.0.0.1:8096/Plugins/8c95c4d2-e50c-4fb0-a4f3-6c06ff0f9a1a"

Originally created by @Gabriel-p on GitHub (May 21, 2020). **Describe the bug** A few days ago I noticed these two plugins, AudioDB and MusicBrainz, installed in my Jellyfin server. I removed them since I had never installed them in the first place. Today I noticed they are back. These are not even listed in the catalog of available plugins. Uninstalling these plugins results in the log messages shown below. **System (please complete the following information):** - OS: elementary OS 5.1.4 (based on Ubuntu 18.04.4 LTS) - Virtualization: [e.g. Docker, KVM, LXC] - Clients: Browser - Browser: Chrome 83.0.4103.61 (Build oficial) (64 bits) - Jellyfin Version: 10.5.5 - Playback: [Direct Play, Remux, Direct Stream, Transcode] - Installed Plugins: None? - Reverse Proxy: [e.g. none, nginx, apache, etc.] - Base URL: [e.g. none, yes: /example] - Networking: [e.g. Host, Bridge/NAT] - Storage: [e.g. local, NFS, cloud] **Expected behavior** No plugins should be installed without my permission/acceptance? **Logs** ``` [2020-05-21 12:10:16.904 -03:00] [INF] Deleting plugin directory "/usr/lib/jellyfin/bin" [2020-05-21 12:10:17.126 -03:00] [ERR] Error processing request: "Access to the path '/usr/lib/jellyfin/bin' is denied". URL: "http://127.0.0.1:8096/Plugins/a629c0da-fac5-4c7e-931a-7174223f14c8" [2020-05-21 12:10:57.256 -03:00] [INF] WS "http://127.0.0.1:8096/socket?api_key=f7b6ce7e8f2e46e69e183ef8594f8e7b&deviceId=TW96aWxsYS81LjAgKFgxMTsgTGludXggeDg2XzY0KSBBcHBsZVdlYktpdC81MzcuMzYgKEtIVE1MLCBsaWtlIEdlY2tvKSBDaHJvbWUvNzkuMC4zOTQ1LjEzMCBTYWZhcmkvNTM3LjM2fDE1Nzk0ODIzNDY5MzA1". UserAgent: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36" [2020-05-21 12:11:01.984 -03:00] [INF] Deleting plugin directory "/usr/lib/jellyfin/bin" [2020-05-21 12:11:02.155 -03:00] [ERR] Error processing request: "Access to the path '/usr/lib/jellyfin/bin' is denied". URL: "http://127.0.0.1:8096/Plugins/8c95c4d2-e50c-4fb0-a4f3-6c06ff0f9a1a" ```

OVERLORD added the bug label 2026-02-06 21:16:55 +03:00

OVERLORD closed this issue

2026-02-06 21:16:56 +03:00

OVERLORD commented

2026-02-06 21:16:58 +03:00

@dkanada commented on GitHub (May 21, 2020):

No plugins should be installed without my permission/acceptance?

Plugins are basically just parts of the server that we were able to remove from the core repository with some extra work. Unfortunately, there are about six to ten sections that can be plugins but we haven't yet had the time to fully separate them. This includes TMDB, TVDB, MusicBrainz, AudioDB, and several other providers or utilities. The reason you can't remove MusicBrainz or AudioDB is because although we were able to turn them into plugins, we can't yet remove them from the server, which means they have to get bundled in the main executable for now. Basically, we all agree with you, and we're working on pulling more code out over time as a result.

@dkanada commented on GitHub (May 21, 2020): > No plugins should be installed without my permission/acceptance? Plugins are basically just parts of the server that we were able to remove from the core repository with some extra work. Unfortunately, there are about six to ten sections that **can** be plugins but we haven't yet had the time to fully separate them. This includes TMDB, TVDB, MusicBrainz, AudioDB, and several other providers or utilities. The reason you can't remove MusicBrainz or AudioDB is because although we were able to turn them into plugins, we can't yet remove them from the server, which means they have to get bundled in the main executable for now. Basically, we all agree with you, and we're working on pulling more code out over time as a result.

OVERLORD commented

2026-02-06 21:16:59 +03:00

@sparky8251 commented on GitHub (May 21, 2020):

Just to add onto what @dkanada said: This was originally done to solve a problem caused by inherited code that caused MusicBrainz to always be hit for lookups regardless of settings.

This was a major issue for the obvious reason, but also because MusicBrainz has a super low API calls per day limit that made it so typical music library scans can take multiple days due to rate limiting.

@sparky8251 commented on GitHub (May 21, 2020): Just to add onto what @dkanada said: This was originally done to solve a problem caused by inherited code that caused MusicBrainz to always be hit for lookups regardless of settings. This was a major issue for the obvious reason, but also because MusicBrainz has a super low API calls per day limit that made it so typical music library scans can take multiple days due to rate limiting.

OVERLORD commented

2026-02-06 21:17:00 +03:00

@Gabriel-p commented on GitHub (May 21, 2020):

Closing then.

Thank you @dkanada and @sparky8251 for explaining the root of the issue!

@Gabriel-p commented on GitHub (May 21, 2020): Closing then. Thank you @dkanada and @sparky8251 for explaining the root of the issue!

OVERLORD referenced this issue

2026-02-06 21:46:43 +03:00

Loosing identified films when library gets rescanned and NFS unstability #2122

OVERLORD referenced this issue

2026-02-06 23:08:02 +03:00

Delete Moved / Removed files from jellyfin database #3318