NinjaJabari
3 months agoSeasoned Adventurer
Unknown Errror
I was able to play the game fine for a few hours until I kept getting this error. Now it's making the game unplayable and I don't know what to do
I was able to play the game fine for a few hours until I kept getting this error. Now it's making the game unplayable and I don't know what to do
Yeah I get the same error. Tried reinstalling Javelin, rebooting, checking game files etc.
Nothing seems to fix it...
I am able to play a few minutes before being kicked out by this error.
I hope it gets fixed soon man
any solutions? is it this our internet problem or theirs?
I got it working on my end by changing my DNS. I was using the Mullvad one, but BF6 doesn't seem to like that one. Using the default DNS now and I am able to play.
I think it's theirs I have no issue with any other game besides this one
Interesting I've been using the default DNS. I'm going to see if Cloudflare works
Please post back with your findings so we know if it works or not.
I've been aggressively trying to tackle this issue for the past few days spending close to 10-hours in various streams of EA tech support channels, and I think I'm getting close to finding the cause.
As you may read in other posts relating to this 'unknown issue', there is suspicion that the issue sits somewhere around account authentication.
My current theory is that after logging into Battlefield 6 on launch day (which would have used my account credentials to generate an authentication token), I changed my account details. Which was fine while my authentication token was valid.
Once that token expired however (potentially 24 hours later), Battlefield 6 was no longer able to create a valid authentication token which is leading to the error you're seeing.
You might ask "But why is it not using my current account credentials to generate the auth-token?"
I dug deeper, and found that multiple iterations of my EA ID were able to log into my account using my current password.
I suspect this is a back-end bug that could be causing all kinds of authentication troubles internally.
Unfortunately, EA doesn't seem to want to take this legitimate cyber-security risk seriously... So here we are. Public forums.
Check out the forum post below:
https://forums.ea.com/discussions/ea-app-technical-issues-en/security-vulnerability---multiple-ea-ids/12763070