unable to refresh OAuth token when downloading list

[agentmith]

Trying to update the Stardew Valley list Bustling Valley, and as soon as it does the initial checks in Wabbajack, it repeats the following below the mod download attempts in the wabbajack log:

00:01:53.172 [ERROR] (Wabbajack.Networking.NexusApi.ProxiedNexusApi) Nexus OAuth Token refresh failed: Bad Request
00:01:53.172 [INFO] (Wabbajack.Services.OSIntegrated.TokenProviders.NexusApiTokenProvider) Setting token nexus-oauth-info
00:01:53.186 [INFO] (Wabbajack.Networking.NexusApi.ProxiedNexusApi) Refreshing OAuth Token

I tried logging out and back into Nexus, but get this:

Your access to Nexus Mods has been temporarily suspended due to an abnormally high number of requests coming from your IP address. We do this to protect our services from malicious users and, more specifically, DDoS attacks.

This suspension will automatically lift so please try again in 10 minutes. Please do not contact us about this issue.

I have done nothing else that would be relevant to triggering this. I haven't visited the Nexus site and haven't downloaded anything else elsewhere. I tried this list last night and this morning and got the same results.

Wabbajack version 3.7.5.1

[agentmith]

Just tested on a Skyrim list, same issue.

[EzioTheDeadPoet]

use the settings to logout and back in

[EzioTheDeadPoet]

use the settings to logout and back in

(After that ~10 minute "ban" is cleared.)

[EzioTheDeadPoet]

The issue is known and we are working on finding ways to prevent it from happening.

[shadowkepe]

This appears to still be an issue. Just happened to me while attemping to download 'Ro' and 'Lost Legacy' both caused the bans.

[shadowkepe]

Found a solution to this issue - under the wabbajack settings - log out of NexusMods. Then log back in. This forces a refresh of the OAuth and the downloads work as intended.

[llouviere]

Looking at the code
Prepare in NexusDownloader.cs does not check for token expiration.
This means that the various VMs that rely on the Prepare to see if they should login, will only check to see if you've EVER logged in through Wabbajack.

I do not see where Wabbajack ever clears up the token file off your hard-drive, so in theory, it will not invalidate expired logins.

NexusLoginManager.cs RefreshTokenState() also checks to see if the OAuth.IsExpired is not true.

This is why shadowkepe's solution works. It forces a refresh of the token, which updates the expiration.