What DayZ RCon Is

RCon means remote console. On DayZ it is a UDP service that BattlEye exposes so an admin tool can say "kick," "ban," "message," or "say" without a player sitting in the mission with a keyboard on the host. It is how you run the server when you are not in the server. CFTools Cloud is the management product that speaks this protocol so you do not have to keep a BattlEye window open on a desktop that falls asleep.

It is not the password in serverDZ.cfg. That password, if you set one, is what players type to join. RCon has its own password in the BattlEye config, BEServer_x64.cfg on Windows or beserver_x64.cfg on Linux. Mixing them up is the first hour of every new admin. The ports guide is the second hour: RCon lives on its own UDP port, conventionally the game port plus three, and RestrictRCon has to be 0 or the interesting commands never arrive.

Anyone who can open that port and guess the password can run your server. Treat the password like a production secret. Short, no spaces, not the same word as the join password, not pasted into a Discord screenshot. Rotate it when a moderator leaves. Cloud stores the connection so your moderators do not each need the raw password in a text file called rcon.txt on a laptop. That file is how communities get hijacked.

RCon does not install mods, edit types.xml, or wipe persistence. Those are file jobs on the host. CFTools Architect is the host for that side if you do not want to be the file job. Cloud is the live side. Using RCon to "restart" is a command to the process, which is useful, and it is not a backup. Read the restart schedule so a remote restart is announced, not a jump scare.

The public server page cannot show your RCon port on purpose. DayZ Manager lists the game address players use to connect. Publishing the RCon port next to a weak password would be a favor to strangers. If you came here to find someone's RCon, you are in the wrong guide. If you came here to run your own, start with BattlEye RCon for DayZ and then the command list.

A server with no RCon can still be a good place to play. It cannot be a place you moderate from a phone. Communities that grow past a handful of friends hit a night when nobody with the host login is awake and a cheater is online. That night is the sales pitch, and it is also just true. Connect Cloud before you need it, while the port is a setting and not an emergency.

After the port answers

Open the community roster and pick a busy server you do not run. You cannot see its RCon, and that absence is the correct design. Your own server, once it is on the stable list, should look the same from the outside: a game address, a map, a player count, and no admin secret. The open list is the same public contract with the password flag cleared. RCon is the private contract. Mixing the two in a hostname ("RCON OPEN", "ADMIN PORT 2305") is how a bored scanner finds you. The classified stamps on this site say "RCON / OPEN" because they are advertisements for CFTools Cloud, not because your UDP port should be a slogan.

A practical first night looks like this. The process is up on the game port. BattlEye has a password and a port. You connect Cloud from a network that is not the host. You send one say. You kick a second client you joined yourself. You ban that test identity for five minutes and confirm the reconnect fails. You unban it. You restart once, with a message, and you watch the process return. If any of those steps only works while you are RDP'd into the box, you do not have remote management yet. You have a window. Write down which step failed before you change the password, the port, and the mod list in one breath.

Staff grow faster than the cfg file. The first extra moderator should get a Cloud user, not the BattlEye string in a private message. When the third moderator arrives, you already want a permission that can kick and cannot wipe. RCon itself is a single password. It cannot express "this person may message and may not ban." That is the product gap Cloud fills on top of the protocol. Keep the protocol working so the product has something to talk to.

Players on a Chernarus server you moderate will not thank you for the port. They will notice whether the person ruining the coast is gone before the next restart. That is the only public proof that RCon exists. If you cannot produce that proof on a Saturday, the cfg is still a hobby. Fix it on a weekday, against the experimental box if you need a place to break things, and leave the live hive alone.