Error "Could not join server (1)"
So when joining this one server noted below many people are getting "Could Not join Server ⚽" including 2 of 4 of my accounts. But the error is only generated when joining this one server link below....
Forum Discussion
Interesting observations @H3dius ,
As we can confirm that on consoles this is definitely the same error message players gets, when they are in fact banned on the servers.
It is not always the player gets the message on screen that they cannot join the server because they are banned.
They simply just gets this less helpful error message "Error - Could not join server ( 1 )".
From consoles and analyzing the network data packages, its caused by what appears to be a botched list of active gaming players and the ban list cache (memory or written onto HDD) on the specific server.
Hope that @jsimpson32
Would come back to me in PM, as would be interesting to see if certain work-around also would work on the PC platform.
In console world, it is a deteriorating condition, that slowly but surely brings a server to its knees.
Would be good to confirm if same for PC world, as then we are clear the issue is in EA backbone infrastructure and not actually due to game server end itself.
EA keeps sending us to go to the server hosting entities for them to fix it, while we have so far not seen anything not working there in that end as intended...
@CyberDyme What also speaks against this theory is that joining from battlelog is not possible. However, joining from the newer in game menu is still possible and does not result in the error.
@H3dius wrote:
@CyberDymeWhat also speaks against this theory is that joining from battlelog is not possible. However, joining from the newer in game menu is still possible and does not result in the error.Yeah, this last point here @H3dius is a good point for the PC world problem.
I would still like to hear from @jsimpson32 though, to try and see if the console workaround also can work in the PC world, for specific accounts/server situations resulting in this peculiar error situation. I still have some insights not able to share here, but testing it in practice would enable me to make a stronger case with EA, if shown to work. It is related to the EA user domain controllers. And how they interact with the game servers. But EA have not been willing to open up and share the real data so far on this. Hence, we are stuck, as they both point towards each other as root cause for the problem.
All while we the server renters/payers/players are shouting and screaming in vain, as obviously nothing is truly done about fixing it...
.JPG){kind=link}