It appears that the MediaMonkey mirror of the MusicBrainz database needs updating.
Many new releases are not autotagging and MMW throws an error that the server is down.
But checking the debug logs the error is actually a 404 error.
For example the following query results in a 404 error
00000256 10:39:49 AM [20348] MM5 [35032](R) TIndyHTTP.GetResponseContent finished: URL: http://mb.mediamonkey.com:5000/ws/2/rec ... s&fmt=json, ResponseContent.Size: 93, ResponseCode: 404
Whereas a direct query to MusicBrainz
http://musicbrainz.org/ws/2/recording/8 ... s&fmt=json
returns
{"id":"8484f7a8-bb69-4437-80b1-fec1dfd15b4d","title":"A Brighter Tomorrow","length":185967,"tags":[{"name":"experimental","count":1},{"count":1,"name":"indie rock"},{"name":"noise","count":1}],"video":false,"first-release-date":"2026-02-06","disambiguation":""}
The error message that the server is down is also a bit misleading and should probably state that the track was not found as the server is running.
Autotag from web failing for newer releases
Moderator: Gurus
Re: Autotag from web failing for newer releases
Hi. You're right ... our MB server is a bit outdated.
How to make a debuglog in Windows - step 4b: https://www.mediamonkey.com/forum/viewt ... 30&t=86643
How to make a debuglog in MacOS - https://www.mediamonkey.com/forum/viewt ... p?t=109505
How to make a debuglog in MacOS - https://www.mediamonkey.com/forum/viewt ... p?t=109505