Trying to use self hosted music brainz server

[neilanthonystuckey]

I am trying to use the new custom lidarr metadata source option. I have my own music brainz server stood up and i can get to the web ui at mylocal ip and port 5000. I can search and see valid results in music brainz server.

I upgraded the lidarr docker image to ghcr.io/linuxserver-labs/prarr:lidarr-plugins-2.13.0.4661

i installed the plugins branch to https://github.com/TypNull/Tubifarry/tree/develop

set the custom lidarr metadata source to the music brainz server http://mylocalip:5000

Getting API errors when search for artists in lidarr

Fatal|LidarrErrorPipeline|Request Failed. GET /api/v1/search

[v2.13.0.4661] NzbDrone.Core.MetadataSource.SkyHook.SkyHookException: Search for 'acdc' failed. Unable to communicate with LidarrAPI.

Api|[GET] /api/v1/search?term=acdc: 503.ServiceUnavailable (355 ms)

i thougt maybe the lidarr.db needed changed so i ran

sudo docker exec -it lidarr2 sqlite3 /config/lidarr.db "INSERT INTO Config (Key, Value) VALUES ('metadatasource', 'http://mylocalip:5000/api/v0.4/');"

Any idea what i may be missing to host my own lidarr metadata server ?

[TypNull]

I'm not sure what's going on, but the 503 error suggests a service issue. Have you tried accessing the API endpoints manually?
Does the MusicBrainz Docker container expose these endpoints directly, or is the reverse proxy supposed to rewrite certain paths?
The lidarr.db isn’t related to this. It looks like a routing or availability problem, not a metadata formatting issue.

If you modify your database I can not really provide support as this could result in database corruption. Even if this is not the issue here. Modifying the database is not recommended and not necessary with Tubifarry.

So first question did you try to hit the API endpoints manually? And did you restart after the plugin installation?

[TypNull]

No, I believe you'd need to hit http://<ip>:<port>/api/v0.4/ with the specific path included.
On api.musicinfo.pro it seems like these two are pointing to the same endpoint.
One quick question, though, you're still seeing a 503 Service Unavailable error right?
And enable trace logs to see where the requests go e.g. : |Trace|HttpClient|Req: [GET] https://api.musicinfo.pro/search?type=all&query=test
Edit: Even if I build it so the settings are properly updated, Lidarr doesn’t seem to reload them automatically. When you change the endpoint, you’ll need to restart Lidarr. Not sure why, normally Lidarr handles that on its own. I’ll include a fix for this in the next release.

[neilanthonystuckey]

Omg I bet I'm just missing the lidarr restart. I'm not home but I'll try asap. Thanks again !

[neilanthonystuckey]

Got it even though i set the user abc pass abc in the postgres.env file i had to adjust the docker-compose.yml file as well. I enabled trace logs in lidarr and saw it rigt away. Now lidarr is connecting to MB server ! thanks for the help !

Internal server error

Oops, something went wrong!

Error:

DBI connect('dbname=musicbrainz_db;host=db;port=5432','abc',...) failed: connection to server at "db" (192.168.48.8), port 5432 failed: FATAL:  password authentication failed for user "abc" at lib/MusicBrainz/Server/Connector.pm line 63

[TypNull]

That's a issue of MB. Not that I can help with that. Your user or pass is wrong😅

[neilanthonystuckey]

Actually that was not the issue it was DNS getting in the way "db" (192.168.48.8) thats a different container that MB server db. they both had the same hostname. I had to adjust the MB server network and all dockers that are going to access MB server to a different docker network and it worked.