# New problem with chroma fingerprint matching
**URL:** https://discourse.beets.io/t/new-problem-with-chroma-fingerprint-matching/1601
**Category:** Help
**Created:** [December 6, 2020, 5:02pm UTC](https://discourse.beets.io/t/new-problem-with-chroma-fingerprint-matching/1601 "2020-12-06T17:02:22Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@uberguy](https://discourse.beets.io/u/uberguy)
#### Post date: [December 6, 2020, 5:02pm UTC](https://discourse.beets.io/t/new-problem-with-chroma-fingerprint-matching/1601/1 "2020-12-06T17:02:22Z")
Good day. I’ve suddenly got an odd problem. I’ve been using beets for about a year with pretty much no issues once I figured out how to really use it. I am running Ubuntu 20.04 with a Docker container using the linuxserver/beets image. I think it was on Friday that I started getting this error when importing:
> chroma: fingerprint matching b’/downloads/A/Benedictine Monks/Benedictine Monks Of Santo Domingo De Silos - - 00 - .mp3’ failed: response is not valid JSON
I have spent my weekend trying to figure out what could have changed. I was working on some other things and did a couple of updates so likely that’s where I screwed something up. I haven’t touched my beets configuration, however.
Here is my config.yaml:
> plugins: the fetchart embedart convert scrub replaygain lastgenre chroma web discogs
> directory: /music
> library: /config/musiclibrary.blb
> art\_filename: albumart
> threaded: yes
> original\_date: no
> per\_disc\_numbering: no
>
> convert:
> auto: yes
> ffmpeg: /usr/bin/ffmpeg
> opts: -ab 320k -ac 2 -ar 48000
> max\_bitrate: 320
> threads: 1
> never\_convert\_lossy\_files: yes
>
> paths:
> default: %the{$albumartist}/$original\_year - $album%aunique{} [%upper{$albumtype}]/$track - $title ($bitrate)
> singleton: “#Non-Album/$artist - $title”
> comp: “#Compilations/%the{$albumartist}/$original\_year - $album%aunique{} [%upper{$albumtype}]/$track - $title ($bitrate)”
> albumtype\_soundtrack: Soundtracks/%the{$album}/$track - $title ($bitrate)
>
> discogs:
> user\_token: XXXXXXXXXXXXXXXXXX
>
> import:
> write: yes
> copy: no
> move: yes
> resume: ask
> incremental: yes
> quiet\_fallback: skip
> timid: no
> log: /config/beet.log
>
> lastgenre:
> auto: yes
> source: album
>
> embedart:
> auto: yes
>
> fetchart:
> auto: yes
>
> replaygain:
> auto: no
>
> scrub:
> auto: yes
>
> replace:
> ‘^.’: \_
> ‘[\x00-\x1f]’: \_
> ‘[\<\>:"?\*|]’: \_
> ‘[\xE8-\xEB]’: e
> ‘[\xEC-\xEF]’: i
> ‘[\xE2-\xE6]’: a
> ‘[\xF2-\xF6]’: o
> ‘[\xF8]’: o
> ‘.$’: \_
> ‘\s+$’: ‘’
>
> web:
> host: 0.0.0.0
> port: 8337
Any clue where I should be looking to sort this out?
---
### Author:  [@uberguy](https://discourse.beets.io/u/uberguy)
#### Post date: [December 6, 2020, 5:07pm UTC](https://discourse.beets.io/t/new-problem-with-chroma-fingerprint-matching/1601/2 "2020-12-06T17:07:09Z")
I should have added, this is how I’m calling beets
> docker exec -u abc -it beets /bin/bash -c “beet -vv import /downloads/A”
---
### Author:  [@adrian](https://discourse.beets.io/u/adrian)
#### Post date: [December 7, 2020, 12:45pm UTC](https://discourse.beets.io/t/new-problem-with-chroma-fingerprint-matching/1601/3 "2020-12-07T12:45:13Z")
Hello! I think the Acoustid servers may be having problems. See this thread, for example:
>
>
> I'm adding new releases in MB database and I was curious after tagging why the fingerprint wasn't on the website and...
---
### Author:  [@uberguy](https://discourse.beets.io/u/uberguy)
#### Post date: [December 8, 2020, 9:39pm UTC](https://discourse.beets.io/t/new-problem-with-chroma-fingerprint-matching/1601/4 "2020-12-08T21:39:42Z")
That was it! Working perfectly today. Thank you very much for the response. I spend so much time screwing stuff up that I always figure I’ve done it yet again. 😄