# Failed to authenticate using oauth (1) - mp3tag 2.98

**URL:** https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-mp3tag-2-98/46741
**Category:** Support
**Created:** [October 15, 2019, 11:19am UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-mp3tag-2-98/46741 "2019-10-15T11:19:02Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [October 15, 2019, 11:38am UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-mp3tag-2-98/46741/6 "2019-10-15T11:38:01Z")

</div>

and what about this:

> [@\[F\] Discogs - Error \>\> 401 : UNAUTHORIZED](https://community.mp3tag.de/t/f-discogs-error-401-unauthorized/17761/5):
>
> Hey all, thanks for the error reports. This is what happened: Discogs changed the API access to be HTTPS-only on March 14. Please see the corresponding [announcement](https://www.discogs.com/de/forum/thread/347984#7056344) on the Discogs API Forums. This implies, that all Discogs Tag Sources now need to use HTTPS, i.e., [https://api.discogs.com](https://api.discogs.com). I've updated the official Discogs Tag Source that ships with Mp3tag to use HTTPS (see the release notes for v2.74). Other Tag Sources that are published via the forums need to be updated by their correspondin…

---

_[View the full topic](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-mp3tag-2-98/46741)._