Set up Project Zomboid RCONControl the server remotely without being in the game

Published on August 9, 2026 · last updated on October 21, 2026

Configuration in servertest.ini

Two values in servertest.ini control access:

RCONPort=27015
RCONPassword=yourSecurePassword

• Without a password, RCON is deactivated - that is the default setting, and deliberately so.
• The RCON port is a port of its own, separate from the game port. Every server with us is assigned its own ports - only enter one here that belongs to your server according to the web interface. The 27015 above is an example, not a default value.
• Only change the file while the server is stopped - otherwise it overwrites it when shutting down.

Choose a long password of its own. Whoever has RCON controls the server completely - that does not belong in players' hands. How ports work for game servers in general is explained in Ports & firewall.

Connecting

Project Zomboid uses the widespread Source RCON protocol. So you do not need a game-specific client - any common RCON tool works.

1. Start an RCON tool of your choice.
2. Enter your server's IP and the RCON port - not the game port.
3. Enter the RCON password and connect.
4. As a test, send players - the response lists the connected players.

If no connection is established, one of these three causes is almost always to blame: the password is not set (so RCON is off), a port was entered that is not assigned to your server, or the file was edited while the server was running and was overwritten.

The kind of failure tells you which of the three it is. If the connection is not accepted at all, nothing is listening on the port - either RCON is switched off for lack of a password, or you are addressing the wrong port. If the connection is established and only the login fails, the password is wrong: then the server either read the file differently from how you wrote it, or your change was overwritten at the last shutdown. This distinction saves aimless trial and error, because it cleanly separates the two problem areas. If, on the other hand, the problem concerns the game port and not RCON, Fix connection problems gets you there faster.

The commands that count in everyday use

The roles and the complete list of commands are in Admin & server commands. save and quit are particularly valuable: with them, you shut the server down cleanly instead of risking a hard abort.

What RCON is really worth it for

• Announcements before a restart - a servermsg ten minutes beforehand saves trouble.
• Saving cleanly before backups - first save, then back up, see Create backups.
• Intervening without starting the game - starting Project Zomboid just to kick someone takes unnecessarily long.
• Automation - many tools can send commands on a schedule, for example saving and announcing every day.

For a server among friends, RCON is dispensable - the commands in the game are enough there. For a community with fixed restart times and several moderators, it is the difference between management and improvisation.

What RCON is - and what it is not

RCON is a way of access, not permission management. Whoever connects works at console level and therefore has everything the server offers. There are no levels, no intermediate stage and no record of who sent which command. The graded roles described in Admin & server commands apply to player accounts in the game - they have no effect on RCON access. Three consequences of this count in everyday use:

• The console has no character in the world. Commands that refer to your own position or your own inventory make no sense via RCON. You always have to name targets here.
• The password travels over the line unencrypted. That is how Source RCON works. So use a password that does not appear anywhere else, and do not pass it on to moderators for whom a role in the game is enough.
• The responses are terse. Some commands only confirm acceptance, not the effect. If in doubt, check in the game or in the server logs whether a change has actually taken effect.

That gives a useful dividing line: via RCON, you handle everything that concerns the server as a whole - saving, announcing, shutting down, scheduled restarts. Everything that relates to individual players in the running game world is usually faster in the game, because you can see what you are deciding about.

A restart routine that surprises nobody

The most common productive use of RCON is the scheduled restart. In Project Zomboid, being thrown out without warning is particularly annoying, because players can be in the middle of an action that costs them their life. The procedure takes less than a minute:

1. servermsg "Restart in 10 minutes" - enough time to get out of a building.
2. The same announcement after five minutes and once more shortly before.
3. save - writes the current state away while everything is still running.
4. quit - shuts the server down cleanly and saves again in the process.

Why not simply restart in the panel? Because quit gives the server the opportunity to write everything away completely. In Project Zomboid, that is more than a formality: the world is stored in a great many small files, and an abort in the middle of writing always only catches part of them. The panel restart remains the right move when the server no longer responds - in normal operation, it is the worse choice.

The same procedure is worth it before every change to the configuration. You may only edit servertest.ini while the server is stopped anyway, otherwise it overwrites your changes when shutting down. And changes to the mod list call for a backup first - save first, then shut down, then fetch the files, as described under Create backups. Once you have internalized this order, a failed mod update costs you one game session at most instead of an entire round.

Frequently asked questions