Jump to content

Question

i have got a problem connecting with the bercon.exe to our new epoch 1.0.3.1 server.
we do have another epoch 1.0.3 server running on the same machine(strato server) and the bercon is working with it.
both use battleye extendended controls (bec), they have different ports and one is able join them.

until now i couldnt find anything in the forums about a similar problem.

 

 

the new epoch 1.0.3.1(vanilla) server seems to be working, except for the bercon issue.

bec is connecting and the beserver.cfg and config files are in place.

the schedular.xml is running too.
battleye is up to date.

bercon.exe:
couldn`t connect to server

 

bec error log:
Error with encoding in queued data list!

 

 

bec, config.cfg:

# This config file is only provided as an example file.


# Edit it to sute your needs.
# For more info on how to edit this file. use the Readme.txt file or visit http://www.ibattle.org/install-and-configure


#--------------------------------------------------------------------------------------------------------
[bec]
#--------------------------------------------------------------------------------------------------------

# Set the ip to your server. normaly 127.0.0.1 will be fine.
Ip = 127.0.0.1


# Set the port to the server. default port is 2302
Port = 2330


# Set the path to the BattlEye directory that is currently in use by the server.
BePath = E:\EPOCH_SERVER\instance_11_Chernarus\BattlEye\


# Set the path to your Admins.xml file containing your admins.
Admins = Admins.xml


# Set the path to your Commands.xml file.
Commands = Commands.xml



#--------------------------------------------------------------------------------------------------------
[Misc]
#--------------------------------------------------------------------------------------------------------
ConsoleHeight = 45
ConsoleWidth = 165

# Only allow english chars to be typed on the chat. Note, Warnings must be enabled. 0 or more.
# Only allow english chars.
AsciiNickOnly = False

AsciiChatOnly = True

# If AsciiChatOnly is set True. you can define none english chars that will be accepted.
# you seperate each char with a , "note you need to define lower and upper case of the chars."
IgnoreChatChars = £,æ,Æ,ø,Ø,å,Å,ö,ä,ü,ß


# Set the amount of warnings a player will get before kicked. -1 is disabled. 0 instant kick
# 1 == one warning on a bad word. next bad word results in kick
Warnings = 3


# Kick players who has listed chars in their name
# DisallowPlayerNameChars = []{}()0123456789


# Max length a player name. kicks players who has to long name.
MaxPlayerNameLength = 16


# Set the name of your armaserver.exe if it has been renamed from armaoaserver.exe to something else!
# if the exe has its originale name. comment it out.
# DO NOT SET FULL PATH TO THE EXE FILE
ServerExeName = epochserver.exe


# Set path to the file containing a list of bad words. Note, Warnings must be enabled. 0 or more.
WordFilterFile = BadWords.txt


# Set the path to the file containing whitelisted guids.
WhiteListFile = WhiteList.txt

# Set custom whitelist kick message. Text must be in ascii letters. MAX 58 CHARS. BE only does ascii on messages
# WhileListKickMsg = you are not whitelisted on this server.


# Kick people with offensive names
NickFilterFile = BadNames.txt

# Set the path to the Scheduer.xml file.
Scheduler = Scheduler.xml


# Kick people who are idleing in the lobby, kick will happen after given time, Min time is 90 sec. use 0 to disable this function.
KickLobbyIdlers = 300


# If enabled. Bec will create seperate chat files for each channel along with the main file.
#ChatChannelFiles = false

# Set the amount of Normal players who can connect. Set it to -1 to disable it.
# If set to 0 it means only players who are listed in the Admins.xml, (or whatever you call it) will be able to connect to the server.
# Quick Example 1: server can holed 50 players. and you want to reserve 5 slots for admins. then set SlotLimit to 45.
# Quick Example 2: server can holed 50 players. and you want to reserve 5 slots for admins and 5 slots for friends. then set SlotLimit to 40,
# AND edit your admins.xml. ADD in all your frineds guid and remaining data, put them in group example 100. or whatever you feel likt.
# by using this method you can give some of your friends some access to some commands if you like or none.
# in general this is works like .Whitelisting X player slots for admins and friends, while leaving the remaining Y slots for public.
SlotLimit = -1

# Set the messahe people will get when they try to connect and is not whitelisted. Text must be in ascii letters. MAX 58 CHARS.
SlotLimitKickMsg = The Server has reached its player limit.

Timeout = 60

#--------------------------------------------------------------------------------------------------------
[Reporter]
#--------------------------------------------------------------------------------------------------------
# Reporter account. Fill in the username and password for your reporter account.
# Gamehack,Hacks will be reported to a database. all players who connect will also be checked against this database.

# Set the Username for your account
#User = alfred

# Set the Password for your account
#Password = 123456



#--------------------------------------------------------------------------------------------------------
[ChatRestriction]
#--------------------------------------------------------------------------------------------------------
# Set max amount of chat lines a player is allowed to send for each channel.
# Going passed the number will result in kick. -1 is disabled, 0 isntant kick.
# If the number is higher than 0 players will be sendt warnings.

Lobby = 30
Global = 5
Side = -1
Group = 10
Vehicle = -1
Command = 13
Commander = 15
Direct = -1



#--------------------------------------------------------------------------------------------------------
[ChatSpam]
#--------------------------------------------------------------------------------------------------------

# Set max amount of chat lines per channel allowed within given time frame.
# Set the values to 0 to disable this function(s)

# Quick Example:
# Lobby = 5
# Lobby_Time_Lower = 10
# Lobby_Time_Upper = 15

# If the time between each new chatlines from a player is less than CHANNEL_Time_Lower the spam counter increases by + 1.
# Consider the CHANNEL (Lobby) as the spam counter.
# When a player has (CHANNEL - 1) in spam counting. a warning will be sent to whom it may consern.
# If the time between each new chatline from the player is Greater than CHANNEL_Time_Lower and Less than CHANNEL_Time_Upper the spam counter stay as it is.
# If the time since the last chatline is greater then CHANNEL_Time_Upper the spamcounter is reset to 1.
# To get optimal result play around a bit with the values on your server.

Lobby = 0
Lobby_Time_Lower = 0
Lobby_Time_Upper = 0

Global = 0
Global_Time_Lower = 0
Global_Time_Upper = 0

Side = 0
Side_Time_Lower = 0
Side_Time_Upper = 0

Group = 2
Group_Time_Lower = 1
Group_Time_Upper = 3

Vehicle = 0
Vehicle_Time_Lower = 0
Vehicle_Time_Upper = 0

Command = 0
Command_Time_Lower = 0
Command_Time_Upper = 0

Commander = 0
Commander_Time_Lower = 0
Commander_Time_Upper = 0

Direct = 0
Direct_Time_Lower = 0
Direct_Time_Upper = 0

 

 

schedular.xml:





000100
000000
1,2,3,4,5,6,7
1
loadbans
0



002000
000000
1,2,3,4,5,6,7
1
say -1 ~ Do not ask for Admins in game - jump on TS3 if you have any issues or need informations! Не разговаривать на русском в Общем канале, либо вы будете забнены! ~
0



020000
000000
1,2,3,4,5,6,7
0
say -1 SERVER WILL AUTO RESTART IN 60 MINUTES!
0



025000
000000
1,2,3,4,5,6,7
0
say -1 SERVER WILL AUTO RESTART IN 10 MINUTES!
0



025500
000000
1,2,3,4,5,6,7
0
say -1 SERVER WILL AUTO RESTART IN 5 MINUTES!
0



025600
000000
1,2,3,4,5,6,7
1
#lock
0



025900
000000
1,2,3,4,5,6,7
0
say -1 ~~SERVER WILL AUTO RESTART IN 1 MINUTE! LOG OUT NOW!~~
0



025950
000000
1,2,3,4,5,6,7
0
say -1 ~~ SERVER RESTART INCOMING! GO THE HELL OFF NOW!!! ~~
0



030000
000000
1,2,3,4,5,6,7
0
E:\CR_METH_test_backup_BASE\bec\_restartperso.bat
1



 

 

start.bat:

@echo off


start "arma2" /min "Expansion\beta\epochserver.exe" -port=2330 "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;" "-BEpath=E:\EPOCH_SERVER\instance_11_Chernarus\BattlEye"
exit

 

 

bec guide: http://www.ibattle.org/install-and-configure
i followed their instruction and double checked everything i could.


did anyone experience issues like this and how would you try to solve these?
 

Link to comment
Share on other sites

9 answers to this question

Recommended Posts

  • 0

 

copy/paste the bec.exe and rename it bec2.exe (or whatever you want) then launch it.

 

ok, i did as you told me to. everything starts up (bec and server console).

bec messege: RCon admin #0 logged in (as usual)

but i still wont be able to connect with the bercon.exe from my machine.

bercon messege: cant connect with server

 

epoch 1.0.3 server(port 2302): accessable with bercon

new epoch 1.0.3.1 server(port 2330): not accessable with bercon

 

Link to comment
Share on other sites

  • 0

yes, it should be the right pw.
E:\EPOCH_SERVER\instance_11_Chernarus\BattlEye\beserver.cfg
bec seems to be using it, cause it can connect.
its the same pw for our other server. (the servers exist in different directories with separate bec`s)
the content of the beserver.cfg has been copied.

i just tried to connect with bercon.exe from the host location, i used the exact same data.

host/ip > port > pw: admin rcon 1# logged in. so it does work.
but it wont work from my machine.

it appears as if something is wrong with the ports, either on my or at the host side.

Link to comment
Share on other sites

  • 0

i have tried all three of them. they are connecting to the old server but not to the new one.

it comes up with the same messege: couldn`t connect to server.
 

i did set up a new beserver.cfg with a different pw, but it doesn`t make a difference.
 

Link to comment
Share on other sites

  • 0

thx for the efforts.

i have just managed to connect.
its been an firewall issue. i had to give the server and bec certain permissions.
my antecessor had done this for the previous server. and since i did all set up according to the tutorials without any experience,
i didn`t know i had to do so.

server firewall:
create new rules
bec.exe, tcp/udp
server.exe, tcp/udp

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Discord

×
×
  • Create New...