HTTP 503 error, can't scan Acoustid

Hi!

Got a problem since maybe one day Picard doesn’t let me check any files via AcoustID. I get a quick “Network error” and the log says something like this:

    webservice._handle_reply:387: Network request error for http://api.acoustid.org:80/v2/lookup: Error transferring http://api.acoustid.org:80/v2/lookup - server replied: Service Unavailable (QT code 403, HTTP code 503)
D: 21:39:40,069 webservice._handle_reply:398: Retrying http://api.acoustid.org:80/v2/lookup (#1)
D: 21:39:40,074 webservice.ratecontrol._slow_down:191: ('api.acoustid.org', 80): slowdown; delay: 16000ms -> 32000ms; ssthresh: 0; cws: 1.000
D: 21:39:40,078 webservice.ratecontrol.get_delay_to_next_request:119: ('api.acoustid.org', 80): Last request was 76 ms ago, waiting 31924 ms before starting another one
D: 21:39:40,082 webservice.ratecontrol.get_delay_to_next_request:119: ('api.acoustid.org', 80): Last request was 80 ms ago, waiting 31920 ms before starting another one

How do I move on to search for errors on my part?

1 Like

Ah, thanks! Also a lesson to check that part of the forum first…

I still got AcoustID errors:

Even if something is wrong with AcoustID, why are fingerprints not visible in MusicBrainz anymore?

Fingerprints are not sent to or or stored on MusicBrainz servers, but only on AcoustID. The MusicBrainz pages have code that calls to AcoustID to get the AcoustID ids, but if AcoustID is down, then that code won’t be able to get those ids.

3 Likes

Looking at https://acoustid.org/stats it looks like AcoustId got an unusual amount of traffic (both lookup and submission) the last 10 days:

3 Likes