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
I'm having the same exact issue. I can join 2 of 3 of their servers. I am not banned on any of them. This started a few days ago.
We need "therealroksteady" from Dice to please address the issue.
I can comfirm this issue.
3 of my 5 servers are affected by this issue since last week...
It turned out that resetting the server GUID... And by this losing your whole player base would fix this issue. At the same time kill your server forever...
Anyways, it also turned out that new server GUIDs are affected by this after a few days.
However, the issue dissapears sometimes for a few hours/days and comes then back
I also would like to adress an additional issue:
1. It is known that servers use fake player counts to populate.
2. Together with this issue the following is happening since last week: The fake players do not show up for the affected servers anymore (in the in game menu). This is extremely unfair because at the moment most servers still have fake player counts and all other servers are basically done and dead now... This is not a fair competition..
3. This is extremly unfair.
The BF4 server market is extremely unfair atm... Please help us...
@H3diusTbh. This issue seems like smth at the Blaze is going on. Not sure tbh.
It does not affect all players. The majority is not able to join from Battlelog and gets this error. Looking at the communication between Origin and Battlelog reveals only an unknown error.
Joining over the in game menu still works though. I did several tests and it turned out that the issue is linked to the server GUID. Moving to other machines/hosts with a GUID will not make the error dissapear. However, resetting a GUID does... So smth with the Blaze or any backend system is screwed up.
----
Same for the fake player counts. All servers should be able to use them or none... Excluding a small portion is unfair....
We need a level playing field...I can confirm the issues discussed in here are actually happening. While it thankfully hasn't happened to me yet, I know of friends and other players who are having this issue and cant seem to fix it since it appears to be some weird error in the Blaze Backend.
And yes, fake player / seeding issue h3dius talks about needs to be addressed and fixed properly! It's absurd and preposterous to fix these fake numbers in battlelog the browser based menu and not in the ingame (.exe) menu. Seeding existed for a long time, used by server owners to help populate their servers. Now with the current bugs going on, seeding doesn't work with our servers anymore. Again, same issues h3dius described; Accounts can't join our servers, getting the error message mentioned in the title of this thread. Seeding doesn't show up in the battlelog menu anymore, for everyone. That's fine, I guess. But for some reason just like h3dius said, seeding is also not showing up in the ingame menu for our servers. Pretty weird considering other servers still visibly have seeding, you can spot that in the ingame menu easily. So we demand that seeding stops working in both menus (ingame and battlelog) altogether or to fix it so its working for everyone again. Its unfair for us server owners who are putting real money into this. Unfair...
.JPG){kind=link}
