Unable to connect to Bethesda for Add-Ons

[SuperFly]

I am unable to access any new add-ons with a fresh install of the game, and am limited to the few that I already had selected/installed from previous playtimes.
It gives me 'Bethesda.net has encountered an error. Please try again'
'Error Code 2000'.
I know Bethesda log-in went belly-up, but DOOM64 still connects and I re-signed my agreements there, after hearing of bugs being caused by that after the change.

THIS bug, however, is totally ♥♥♥♥♥♥♥ unsat because the convenient Add-ons are an advertised function of the game, now.

Does ANYONE know how to fix this garbage and regain access to the add-on frontend?
Please don't bother posting "these WADs are available at XYZ", "you should just play X source port" or similar useless responses -- I know, and don't care.

I am only interested in getting this official Unity version to function fully.
This issue is also happening in Ultimate DOOM.

[Thermal Lance]

Have you tried reinstalling?

Maybe something broke given that it seems to work fine on my end.

Or perhaps it’s a problem with your Bethesda account itself?

[SuperFly]

This is occurring on a fresh re-installation -- and I connected to/re-signed my agreements on my Bethesda account (through DOOM64) only minutes before having this problem with DOOM/DOOM2.

The little dot icon beside 'BETHESDA.NET' is also showing as red, instead of green.

All 3 games were re-installed at the same time.

[PainkilleR]

The only way I could get a 'Bethesda.net has encountered an error. Please try again' message is by blocking an outbound connection for DoomII.exe in firewall. That said the error code is -1 and not 2000.

[SuperFly]

Originally posted by PainkilleR:

The only way I could get a 'Bethesda.net has encountered an error. Please try again' message is by blocking an outbound connection for DoomII.exe in firewall. That said the error code is -1 and not 2000.

That's definitely not my issue, but interesting that it could be port-related.
Another small detail is that in both games, I had an add-on pre-activated (Sigil/No Rest, respectively) when I installed them.
(no change in error/function when disabling them and trying again/restarting)

I'm glad to hear nobody else is experiencing this -- but it's also disheartening to know that it's an obscure problem happening to "only me".

[SuperFly]

This error persists for me.

I made sure to troubleshoot everything I could think of -- including re-installs/reboots -- and ensured the add-ons I still have available were not pre-activated.

The error code remains the same when trying BETHESDA.NET option, and Add-On menu still reports "You must sign into your Bethesda..."

Any further ideas?

[PainkilleR]

Try to disable steam cloud for Doom II, then go to C:\Users\username\Saved Games\ and delete id Software folder (or only id Software\DOOM 2 folder), delete folder Bethesda Softworks (or Bethesda Softworks\DOOM 2) from C:\Users\username\AppData\LocalLow.

[SuperFly]

Originally posted by PainkilleR:

Try to disable steam cloud for Doom II, then go to C:\Users\username\Saved Games\ and delete id Software folder (or only id Software\DOOM 2 folder), delete folder Bethesda Softworks (or Bethesda Softworks\DOOM 2) from C:\Users\username\AppData\LocalLow.

I did both of these -- and while it wiped my 2x available add-ons, and gave me re-login prompts to Bethesda -- the 'Error Code: 2000' persisted. I even made sure to re-sign the TOS agreements before logging in.

The Add-On frontend gave the same 'must log in' reports, and I had to re-place the previous data folder to regain access to the installed mods.

Weirder, is that my BethSoft account works just fine for DOOM64, and I already re-authorized the TOS in that game.

[SuperFly]

UPDATE:

Following the recent consolidation of titles, I was given fresh authentication prompts and log-in was a success -- as was grabbing new add-ons.

Thanks to everyone that helped.
Problems with connection do persist, with error Codes -1 and 40901.