'There was a problem logging in (Error 14403)'

Eyo!

Been starting a HCSSF char… and was playing last friday… but i’ve keep getting this error 14403 all the evenings since…
I’ve opened a ticket at Battle.net but they keep sending me here… since their solutions arent working for me… such a Checking firewall, anit-virus, restart pc & router, disable background apps, flushing the DNS…

The 14403 code arent helping much, it doesnt say whats wrong… Hope you guys are able to help me, im start to get abstinences xD

Thanks in advance!

Two players reported the same problem on the German forums… no real fix.

Not much can be done since no one seems to know what’s causing this error… check your D3Debug.txt file ?

Make sure your BNet App is up-to-date…

What to look for in the D3Debug.txt ?
Dunno if theres something with the account… i can logon the free trail no problem

Not sure, to be honest… look for error messages towards the end of the file… something that might give a clue about the problem. The D3Debug.txt file gets rewritten each time you launch D3… so you could launch it with the free trial account and save the debug info on your desktop… and then launch it with your normal account and compare the two debug files. Check if the debug file with the normal account is shorter for example…

That’s possible… there are also some cases on the Korean and Russian forums:

You can perform a soft reset of your account if you wish by changing the password:

  • exit Diablo 3 completely
  • exit Battle.Net
  • go into your Account Settings and change the password (https://account.battle.net/security)
  • Reload the BNet App and launch D3… see if it will let you log in.

Are you using “Parsec” (remote desktop software) ?

No this is not related to parsec, ai is mixxing smth up there parsec error is 14003 and this is 14403 this is the root cause to this error: – CAuthHandler::OnGetLogonFormResult(14403, „JSON error: Status has no name.(14403) token: 2“, 0, )

[/quote]

quick side note n battle net it’s working it has smthto do with the -launch parameter

interesting… doesn’t affect everyone though.

I can launch a game in Europe both with the -launch parameter or through BNet.

Did it solved it for you ?

sadly not yet, already tried like everything reseting winsocket, enable a firewall passthrough disable it completly reinstall os and drivers, start as other user, weird thing is that it’s since the bnet update on friday and tried it in a different network as well and with a account of a friend to test

if everyone which has the same erro could post theri d3debug file so i can compare, the onliest thing i saw with a working client is that the worker id on the server side is different, so would like to know what we all have in common, maybe only one worker is messed up or smth on bliz side or we have a special driver or smth if you could also sen me the input of msinfo32 to see maybe we have a special piece of hardware in common or smth

1 Like

BNet released a newer version… now: 2.49.0.15846

and couldn’t replicate on a working client

will test, only in beta client notthing yet fpr me and will inform you if it fixed smth

sadly still persits, if people could post ther d3debug im especially looking for these lines: ===== Battle.net Platform : Connect =====
2025.10.14 12:42:34.656002600 I 10:42:34.656739 [BGS] |event=Connection metering enabled.|connection_id=1 (D:\BuildServer-Dev\1\work\code\branches\2_8_0\build\package_cache\bgs-sdk\6.5.1\src\low\core\connection_handler.cpp:263)
2025.10.14 12:42:34.656298800 I 10:42:34.657070 [BGS] |event=Connection to Battle.net ready.|connection_id=1|address=eu.actual.battle.net|port=1119 (D:\BuildServer-Dev\1\work\code\branches\2_8_0\build\package_cache\bgs-sdk\6.5.1\src\low\core\connection_handler.cpp:283)
2025.10.14 12:42:34.656495700 ===== Battle.net Platform : Connected to Battle.net =====
2025.10.14 12:42:34.656856900 ===== Battle.net Platform : Authentication.Logon =====
2025.10.14 12:42:34.657128000 [Telemetry] (FCS): [15184]: Failed to load rules from the cache. Failed to parse the protocol buffer.
2025.10.14 12:42:34.733168900 >>> Logon Queue: Queued Position 1 - <1 minute left…
2025.10.14 12:42:35.037975700 – CAuthHandler::OnGetLogonFormResult(14403, “JSON error: Status has no name.(14403) token: 2”, 0, )
2025.10.14 12:42:35.038396600 >>> ((no hero selected)) OnlineService::BnetService::Logout
2025.10.14 12:42:35.038895800 >>> ---------------- ModalNotificationManager::SetOkNotification: There was a problem logging in. (Code 14403)
2025.10.14 12:42:35.052842300 >>> (no hero selected) OnlineService::BnetService::LogoutSynchronously
2025.10.14 12:42:35.115192400 I 10:42:35.115917 [BGS] |event=Disconnected|method=OnDisconnectComplete|address=eu.actual.battle.net|port=1119|status=0 (D:\BuildServer-Dev\1\work\code\branches\2_8_0\build\package_cache\bgs-sdk\6.5.1\src\low\core\connection_handler.cpp:245)
2025.10.14 12:42:35.115450600 >>> (no hero selected) ===== Battle.net Disconnected logoutRequested=yes =====
2025.10.14 12:42:35.115613900 >>> Settings::ResetGameAccountSettings
2025.10.14 12:42:35.115818300 >>> (no hero selected) ===== Battle.net Logged Out =====

You probably have it from your other account… but this is what I get :
(I’m currently connected to the Europe BNet and Europe D3)

2025.10.14 07:51:13.948243000 ===== Battle.net Platform : Connect =====
2025.10.14 07:51:14.648944600 I 11:51:14.649720 [BGS]
2025.10.14 07:51:14.649140200 I 11:51:14.649984 [BGS]
2025.10.14 07:51:14.649250500 ===== Battle.net Platform : Connected to Battle.net =====
2025.10.14 07:51:14.649439800 ===== Battle.net Platform : Authentication.Logon [SSO] =====
2025.10.14 07:51:14.649644600 [Telemetry] (FCS): [17308]: Failed to load rules from the cache. Failed to parse the protocol buffer.
2025.10.14 07:51:14.796949000 >>> Logon Queue: 0 or less time remaining: endTime=1760442674s 500103mu now=1760442674s 797725mu
2025.10.14 07:51:15.246050000 >>> (no hero selected) InvokeAccountLevelInfoUpdated
2025.10.14 07:51:15.246247400 >>> Boubou#1741 BnetRID::GameAccountLogon id={id=10231599, program=D3, region=2}
2025.10.14 07:51:16.699404000 >>> Boubou#1741 BnetRID::GameAccountLogon_SelectGameAccountCallback code=0
2025.10.14 07:51:16.699844600 SendWarden3Custom hero:(no hero selected) id:270 Version: 2.8.0.99920 CustomMessageId: 270 CustomMessage: ?? CustomMessageDestination: 7 count:0 attribute_spaceused: ??
2025.10.14 07:51:16.947382400 >>> (no hero selected) BnetService::OnGenerateSSOToken code=0
2025.10.14 07:51:16.947605300 SendCustom hero:(no hero selected) id:6 Version: 2.8.0.99920 CustomMessageId: 6 CustomMessage: ???EU??c?c?abccb???c??b?e?f??abb??? CustomMessageDestination: 0 count:0
2025.10.14 07:51:17.195885700 >>> BnetRID::GameAccountLogon_OnInitialLoginDataQueuedResponse code=0
2025.10.14 07:51:17.196175200 >>> BnetRID::GameAccountLogon_OnInitialLoginDataQueuedResponse: service_id=1010695731 timeout_tick_interval=1800
2025.10.14 07:51:18.762785800 >>> BnetRID::OnInitialLoginData: Expected service_id=1010695731 message service_id=1010695731
2025.10.14 07:51:18.762965000 >>> BnetRID::OnInitialLoginData code=0
2025.10.14 07:51:18.763081600 MyContentFlags=2101663 ServerContentFlags=4294967295 ServerPool=Default
2025.10.14 07:51:18.763174500 >>> BnetRID::OnInitialLoginData: server reported time at logon is 813757877591197000
2025.10.14 07:51:18.764079100 >>> Boubou#1741 My Hero List:

Upgrade to Win 11 resolved it → so looks like it’S an incompatibility with a special win 10 version

1 Like

Suggested solution:
uninstall latest win updates (exact version when it’s working again will follow)
or update to Windows 11
If your system doesn’t meet the requirements for Win 11 go to your registry and add the following dword to: HKEY_LOCAL_MACHINE\SYSTEM\Setup
dword: AllowUpgradesWithUnsupportedTPMorCPU
and set value to 1
then download win 11 iso and install via there

1 Like

Thx for posting the solution here and on the topics in other languages… hopefully, that will work for everyone.

I suspect however that “updating to Win’11” will cause hardship for some…
and today’s the day that Micro$oft ends Win’10 support :frowning:

Best of luck in your games…