7 Days to Die whitelist, remote admin and errors

Whitelist

A password keeps strangers out until someone shares it. A whitelist only lets in the Steam IDs you approve. You can use both.

Stop the server in the panel .
In Files, open serverconfig.xml and set:


<property name="WhitelistEnabled" value="true"/>

Start the server and add players from the Console:

Command	What it does
`whitelist add <name or steam id>`	Approves a player
`whitelist remove <name or steam id>`	Removes a player
`whitelist list`	Shows who is approved

The list is saved in serveradmin.xml in your save folder, next to the admin list. See Find your Steam ID and admins and commands.

Remote admin tools (telnet)

Tools such as server managers and bots connect to 7 Days to Die over telnet.

Stop the server and open serverconfig.xml.
Set a strong TelnetPassword first. A telnet port with no password lets anyone run commands.
Set TelnetEnabled to true and TelnetPort to an extra port your server owns (add one on the Network tab, see Adding Ports).
Start the server. The tool connects with your server IP, the telnet port and the password.

If a value is also on the Startup tab, change it there; Startup values are applied when the server starts.

Cannot join or kicked straight away

Wait for the server to finish booting. Watch the Console until it stops loading.
Use the IP and port from the panel. See Join your server.
Make sure the game and the server are on the same version. Restart the server to update it; players update through Steam.
With mods, every player needs exactly the same mods as the server.

“ZLIB: invalid stream” or similar right after connecting usually means the server turned the player away: mods differ between server and player, mods were removed but the old world kept, or the world named on the server is missing or damaged.

Only one player has the problem: close the game and Steam, delete %appdata%\7DaysToDie on their PC (local cache only), verify the game files in Steam, reinstall the server’s mods, and try again.

World will not load after removing mods

A world made with world-changing mods (new biomes, buildings, decay) often will not load without them. Put the mods back, or set a new GameName so the server starts a fresh save. The old save stays in the Saves folder in case you want it later. See worlds.

Kicked by Easy Anti-Cheat

Code-changing mods need EAC off, but console and crossplay need EAC on. See mods and crossplay.

Still stuck

Open a ticket with your panel link and a screenshot of the panel Console showing the red ERR or EXC lines from startup or from the moment the player joined. The panel console is more useful to us than the in-game F1 console.