# "Failed to Authenticate Using OAuth (1)" 12002: The Operation Timed Out
**URL:** https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124
**Category:** Support
**Created:** [March 17, 2024, 12:00pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124 "2024-03-17T12:00:13Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@ErryTing](https://community.mp3tag.de/u/ErryTing)
#### Post date: [March 17, 2024, 12:00pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/1 "2024-03-17T12:00:13Z")
MP3TAG is now randomly throwing out this error. I've done a couple things to attempt to fix it myself -- such as uninstalling and reinstalling, resetting configurations, revoking access, etc. Nothing has worked and now I'm stumped. Google is no help and neither is any of the threads posted in the past about this issue, as none of them have any posted solutions.
Any thoughts?
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [March 17, 2024, 12:02pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/2 "2024-03-17T12:02:36Z")
> [@ErryTing](#):
>
> I've done a couple things to attempt to fix it myself
Including this one?
> [@WSS: The time limit for the operation has been reached - Error 12002](https://community.mp3tag.de/t/wss-the-time-limit-for-the-operation-has-been-reached-error-12002/63852/2):
>
> If you search for [12002](https://community.mp3tag.de/search?q=12002%20order%3Alatest) in this forum you get many possible solutions. One of them is: File -\> Options -\> Networking: Increase the value for "Timout"
---
### Author:  [@ErryTing](https://community.mp3tag.de/u/ErryTing)
#### Post date: [March 17, 2024, 4:17pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/3 "2024-03-17T16:17:09Z")
I actually did not come across that one, I appreciate the reply. I'll get back to you if it fixes it.
- So far it seems like this has fixed the issue, I set the timeout to 10000 and seems to work now. Thank you for bringing that to my attention lol.
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [March 17, 2024, 4:25pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/4 "2024-03-17T16:25:00Z")
This value would be 10'000 seconds = 166 Minutes or nearly 3 hours.
I'm not sure, if you really want to wait that long until a Timeout occurs.
---
### Author:  [@ErryTing](https://community.mp3tag.de/u/ErryTing)
#### Post date: [April 8, 2024, 12:31pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/6 "2024-04-08T12:31:46Z")
So funnily enough, while it worked for a long while, it is now giving the failed to authenticate error again, lol. (Meant to reply to your post directly.
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [April 8, 2024, 1:01pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/7 "2024-04-08T13:01:17Z")
You get this error using which Musicbrainz-Websource-Script exactly?
Does it occure immediately if you start using Mp3tag on a new day?
Or does it occure after several search attempts?
---
### Author:  [@ErryTing](https://community.mp3tag.de/u/ErryTing)
#### Post date: [April 11, 2024, 12:52pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/8 "2024-04-11T12:52:49Z")
No only on the discog scripts. Musicbrainz works just fine.
---
### Author:  [@Denninger](https://community.mp3tag.de/u/Denninger)
#### Post date: [January 7, 2025, 12:49am UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/9 "2025-01-07T00:49:08Z")
Hello, I have the same problem.
**Situation**
In December I could use MP3tag (v3.28) searching Discogs. Now it fails with the (partly Dutch) error message:
> Failed to authenticate using OAuth (1).
> \>12002: 12002: Er heeft een time-out van de bewerking plaatsgevonden.
_Note, "Er heeft een time-out van de bewerking plaatsgevonden." is Dutch for: "The operation timed out."_
**What I tried so far**
- Remove the "mp3tag.cfg" from "%AppData%\Mp3tag". I even removed the _whole directory_ without results.
- I ran [CCleaner (free edition)](https://www.ccleaner.com/) to clean my system and [Spybot Search & Destroy (free edition)](https://www.safer-networking.org/compare-spybot-editions/) too. I removed the Immunization applied by Spybot, assuming it could be a problem like "using a firewall". But it was not...
- I revoked all the MP3tag authorizations in my account at [Discogs -\> Settings -\> Applications](https://www.discogs.com/settings/applications). _Not_ triggering a new authorization request, so I think there is no connection established for some reason. Therefore, I suspect the time-out occurs _before_ connecting tot [Discogs.com](http://Discogs.com).
- Increased the timeout in MP3tag from 10 (the default) to 120 seconds.
- I _only_ have this error when connecting to [Discogs](https://www.discogs.com/). Connecting to [freedb](https://gnudb.gnudb.org/) and [MusicBrainz](https://musicbrainz.org/) is _not_ a problem.
**Question**
Does anybody have a solution how to fix this?
Thanks in advance!
**My system and software versions**
- MP3tag version 3.28 (Dutch language).
- Windows 11 Pro version 24H2, build 26100.2605 (Dutch language). Including the latest updates.
**Found topics on this forum**
I did try the 'solutions' suggested from the following topics without fixing the time-out error.
- [Failed to authenticate to Discogs _(Feb 2022)_](https://community.mp3tag.de/t/failed-to-authenticate-to-discogs/56352).
_I don't use a firewall other than the default one in Windows 11. No specific rules and no changes between December 2024 and January 2025._
- [Failed to authenticate \>12002:12002 only for Discogs _(Oct 2021)_](https://community.mp3tag.de/t/failed-to-authenticate-12002-12002-only-for-discogs/54772).
_My system-time is accurate and disconnecting and reconnecting to the internet does not fix the time-out either._
- [Discogs authorization setup _(Okt 2014)_](https://community.mp3tag.de/t/discogs-authorization-setup/16278).
_Including the articles mentioned [there](https://community.mp3tag.de/t/discogs-authorization-setup/16278)._
- [Discogs and Oauth _(Dec 2014)_](https://community.mp3tag.de/t/discogs-and-oauth/16388).
_I do have an account at Discogs, logging in and revoking all 10 or so MP3tag authorizations [there](https://www.discogs.com/settings/applications) doesn't do the trick._
- [Failed to authenticate using OAuth (1) _(May 2016)_](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1/17968).
_I cannot find this "Pone Mod" script, so I assume I'm not using it. And I don't get the same error codes (12157 or 403) mentioned there._
- [Timeout when running Audible via API Tag Source on Mac _(Sep 2024)_](https://community.mp3tag.de/t/timeout-when-running-audible-via-api-tag-source-on-mac/66094).
_Although I'm running MP3tag on Windows 11 😉._
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [January 7, 2025, 6:17am UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/10 "2025-01-07T06:17:33Z")
Is MP3tag allowed at all to access the internet?
Try Help\>Check for new version and see if you get a reply.
Do other web sources work?
---
### Author:  [@Denninger](https://community.mp3tag.de/u/Denninger)
#### Post date: [January 7, 2025, 3:19pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/11 "2025-01-07T15:19:31Z")
Thanks and yes,
MP3tag tells me it is up-to-date (latest version)
I also tried MP3tag on another Windows 11 (not Pro) PC (2). The older MP3tag installation (v3.27) on that machine immediate came with an update request and has the same time-out issue as the Windows 11 Pro PC (1).
After updating it to version 3.28 PC (2) still has the same time-out problem as PC (1).
The same goes for a portable version of MP3tag: it asks for an update and has a time-out in the old (3.27) and the new (3.28) version...
Maybe it is my internet router?
Damn, yes! If I connect to my phone's hotspot (bypassing my normal internet router) Discogs _immediately_ asks for a new permission and _works_!
**It is my FRITZ!box 5530 fiber router!** _or my internet provider..._ 😅
Thanks and sorry for the fuzz, it must be some update in my router or internet provider...
Do you or anyone else know what data traffic might be blocked?
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [January 7, 2025, 3:36pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/12 "2025-01-07T15:36:13Z")
We just had a similar problem here, the cause of which was a fixed MTU setting in the router.
> [@Can not reach musicbrainz.org with WSS](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/4):
>
> Does your equipment not support MSS Clamping?
But that can't be the cause for you, as Fritz!boxes don't have such a setting option, as they support MTU clamping by default.
Or do you have another router between your PC and Fritzbox?
---
### Author:  [@Denninger](https://community.mp3tag.de/u/Denninger)
#### Post date: [January 10, 2025, 10:41pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/13 "2025-01-10T22:41:38Z")
Thanks Poster!
I don't use another router and I have no problems connecting and using [Musicbrainz.org](http://Musicbrainz.org) in my current configuration.
Is this MTU clamping also used to connect to [Discog.com](http://Discog.com)? Or any specialized ports?
If I make a VPN-connection (using Windscribe) I can connect to [Discog.com](http://Discog.com) without problem. So I think it is my internet-provider.
I would like to know what to ask them. I mean: what port or network traffic is probably blocked?
As a test, I added a screenshot of the NETSH-command suggested in the "[Can not reach musicbrainz.org with WSS)](https://community.mp3tag.de/t/can-not-reach-musicbrainz-org-with-wss/66972/4)" you suggested. Maybe this gives another insight.
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [January 11, 2025, 5:24pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/14 "2025-01-11T17:24:58Z")
> [@Denninger](#):
>
> Is this MTU clamping also used to connect to [Discog.com](http://Discog.com)? Or any specialized ports?
It is called MSS Clamping.
It happens all the time because your Fritz!box has this feature by default. That means that normally there should not arise any MTU-size problems. You can not test with ping and the df-flag if lowering the mtu-size anyway shows any success because discogs does not answer to ping commands. So you could only test it with lowering the mtu-size for your actually used net-adapter, but I don't think that this is the reason for your problem. Anyway: Just test it with an MTU-size of 1400.
Open a windows command prompt with administrative rights and enter:
`netsh interface ipv4 set subinterface "Ethernet, zwart (HP, Realtek)" mtu=1400 store=persistent`
Don't forget to set it back to 1500 later.
Do you have these problems with discogs only with the webscript and Mp3tag or do these timeouts also occur when you access [discogs.com](http://discogs.com) with a browser?
I can see, that you have WLAN and Ethernet both connected. How do you access the internet, with WLAN or Etrhernet?
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [January 11, 2025, 8:34pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/15 "2025-01-11T20:34:08Z")
> [@poster](#):
>
> You can not test with ping and the df-flag if lowering the mtu-size anyway shows any success because discogs does not answer to ping commands.
I think that was a wrong assumption on my part regarding the behavior of the ping command. It is true that [discogs.com](http://discogs.com) does not respond to ping. However, this apparently only comes into effect when the ping command reaches the address.
In my test, ping -f -l 1470 [discogs.com](http://discogs.com) results in the package not getting through because of the defragmentation ban. If I reduce the value to 1460, the command goes through and I get timeouts because only then is [discogs.com](http://discogs.com) reached and, as stated, does not respond to pings.
Conclusion: You can definitely carry out tests with the defragmentation flag even though the addressee does not respond to pings.
---
### Author:  [@Denninger](https://community.mp3tag.de/u/Denninger)
#### Post date: [January 27, 2025, 5:39pm UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/16 "2025-01-27T17:39:07Z")
Thanks and sorry for responding so late.
I tested the MTU-settings and pinging as suggested with command: `ping -f -l 1460 discogs.com`
Resulting in:
- "Request timed out" on mtu=1500 .
- "Packet needs to be fragmented but DF set" on mtu=1400
Just as you predicted.
Strange thing is: MP3tag is now working with both mtu-settings.
So I think my provider opened a port again?
Anyway MP3tag is working with Discogs again now. Thanks!
P.S. I never had a problem with the Discogs website in my browsers. Only MP3tag not connecting to it 😉
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [November 23, 2025, 9:08am UTC](https://community.mp3tag.de/t/failed-to-authenticate-using-oauth-1-12002-the-operation-timed-out/64124/17 "2025-11-23T09:08:06Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.