Page MenuHomeFeedback Tracker

BattlEye kick everybody with "Client not responding" since 1.78
Closed, ResolvedPublic


I run 2 Servers on one Maschine, the Server with Port 2302 is running quiet good but the second one with Port 2502 is kicking everybody after 20 seconds.
Maybe its a Issue with this changed Battleye Port.

Log says "Connected to BE Master" but when somebody is connecting to the Server it keep spaming
BEServer: cannot find channel #205241591, users.card=0 until you get kicked after 20 Seconds.

I already tryed to change the RConPort in the BE_Server.cfg


Operating System
Windows 10 x64
Dedicated Server
Steps To Reproduce

Run a Arma Server on Port 2302 and a seconds one on a other Port

Additional Information

Windows 2012 R2 Server

Event Timeline

BrezZZz created this task.Nov 30 2017, 7:06 PM
Wulf added a subscriber: Wulf.Dec 1 2017, 9:51 AM


We apologise for the inconvenience. Thank you for the report, we will have a look at it.

Wulf closed this task as Resolved.Dec 1 2017, 9:51 AM
Wulf claimed this task.
Wulf reopened this task as Reviewed.Dec 1 2017, 11:44 AM

So i tryed this out on a diffrent maschine with other Missions on it.
Same thing, Battleye will only work on one of them. Turn off Battleye will fix it,
but thats not a Option for me, so please give me a Fix for it.

This issue is realted to new BE Traffic port separation and its behaviour. Server is mapping BE Port as hardcoded incremental from server game port. Client is currently only listening to 2306 and have no respect to other ports -> server is not responsible if game port isn't 2302.

Hotfix is out and everything is working again :)

Wulf closed this task as Resolved.Dec 8 2017, 2:09 PM

That is great to hear.

Connectivity issues are not fixed

The server still works without BatlEye

which ports to open or firewall?

now the server uses ports 2312 - 2313

Wulf added a comment.Dec 14 2017, 9:53 AM

@aleksandr.noskov.26261 Please, create a separate ticket for your issue.

FIXED BATLLEYE PROBLEM! battleye: client not responding.... 1.80 hotfix fucks us!