# Tag Sources/Cover Art Errors **URL:** \ **Category:** Support\ **Created:** [July 17, 2016, 9:26am UTC](https://community.mp3tag.de/t/tag-sources-cover-art-errors/18115 "2016-07-17T09:26:17Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Sludge](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/s/e36b37/32.png) [@Sludge](https://community.mp3tag.de/u/Sludge)\ **Post date:** [July 17, 2016, 9:26am UTC](https://community.mp3tag.de/t/tag-sources-cover-art-errors/18115/1 "2016-07-17T09:26:17Z")
Suddenly the Tag Sources/Cover Art server seem to be throwing back errors to MP3TAG. The Amazon servers seem to be throwing back "400: Bad Request" errors for everything (including searches that I know worked only about 6 hours ago). Maybe another attempt by Amazon to stop non-browser clients from accessing anything on their servers perhaps? As I know how stupidly "protective" their policies are. Discogs shows "401: UNAUTHORIZED", but I know this has always been flakey at best. MusicBrainz is actually working (mostly). ---
**Author:** ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)\ **Post date:** [July 17, 2016, 2:38pm UTC](https://community.mp3tag.de/t/tag-sources-cover-art-errors/18115/2 "2016-07-17T14:38:57Z")
> [@Sludge](#): > > The Amazon servers seem to be throwing back "400: Bad Request" errors for everything (including searches that I know worked only about 6 hours ago). No problem here. Check your system date and time whether they are correct. Maybe your bios-battery is empty. ---
**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\ **Post date:** [February 9, 2026, 12:26pm UTC](https://community.mp3tag.de/t/tag-sources-cover-art-errors/18115/3 "2026-02-09T12:26:20Z")
Closed on February 9, 2026, 12:26pm UTC