DZPage Panel: install it on Linux with one command, connect it to dzpage.com and manage your DayZ servers

The DZPage Panel turns your own Linux server into a DayZ host that you manage entirely from dzpage.com: create servers, install the game files, start them, keep an eye on them and schedule restarts. It works the way you know from the big server management services, only it's free and runs on your own machine. The panel itself is just the helper on the machine; the managing happens in your browser.

This guide walks you through the whole thing: from an empty server to a running DayZ server, plus everything that matters day to day and when something goes wrong.

The short version

1. On dzpage.com, open RCon and click Get my command on the Connect a server card.
2. Paste the command into your server's terminal over SSH.
3. Confirm that the DZPage account shown is yours, and log in to Steam.
4. On dzpage.com, click New server under Your servers and submit the form.
5. Wait until the game files have downloaded, then click Manage and Start.

No port for the panel, no domain, no key to type in.

What you need

• A Linux server with x86_64 and systemd. Tested on Ubuntu 22.04, Ubuntu 24.04, Debian 12 and Debian 13, and the two Debian versions also as minimal installs. A rented server (VPS or root server) is enough. ARM machines such as a Raspberry Pi won't work, because the DayZ server only exists for x86_64.
• Memory and disk space: A running DayZ server needs 3 to 6 GB of RAM and about 6 GB of disk space, a lot more with mods. The panel itself hardly counts by comparison.
• A Steam account that owns DayZ. If you haven't bought the game, Steam refuses to download the server. No panel can get around that.
• A DZPage account. You sign in with Discord, and it's free.
• SSH access to your server, as a user with sudo or directly as root.

The installer fetches everything else by itself: git, the 32-bit libraries for SteamCMD and, if needed, Node.js in its own folder. SteamCMD itself is downloaded by the panel when you log in to Steam.

Step 1: Get the command

Sign in on dzpage.com and open RCon. On the Connect a server card, click Get my command. You get a command with a one-time pairing code inside:

curl -fsSL https://dzpage.com/panel/install.sh | sudo bash -s -- --pair dzp_pair_…

The code works once and for 30 minutes. If you need a new one later, reload the page and click again.

Above the command you can switch between With sudo and As root, without sudo. The second variant is for servers that have no sudo, for example a Debian system that got a root password during installation. There the sudo variant stops right away with "sudo: command not found".

As long as it's valid, the pairing code is as valuable as a password: whoever has it can connect a server to your account. Don't share it and don't show it on stream.

Step 2: Paste it into the terminal

Connect to your server over SSH, paste the command and press Enter. The installer then works for a few minutes:

• It checks the machine (architecture, system, memory, free space) and tells you if anything is tight.
• It creates a dedicated user called dzpage. The panel never runs as root.
• It installs the 32-bit libraries for SteamCMD and, if needed, Node.js.
• It sets up the service and starts it.

After that it redeems the code at dzpage.com. Before the panel takes over the connection, the terminal shows which DZPage account the server is about to be connected to and asks, in German, whether this is your account (J means yes, n means no):

Der Server wird mit dem DZPage-Konto »DeinName« verbunden. Ist das dein Konto? [J/n]

If your name is shown there, press Enter. Just like AirDrop asks before you accept something, this question makes sure your server doesn't end up on someone else's account by mistake. If you answer n (or press Ctrl+C), the server stays unconnected and the panel revokes the key that was just issued by itself, so it doesn't take up one of your ten places.

Logging in to Steam

Finally, if the connection worked, the installer asks for your Steam account name. Then SteamCMD starts right in your terminal and asks for your password and, if you have it turned on, your Steam Guard code.

You only ever type your Steam password into SteamCMD on your own machine. It only goes from SteamCMD to Steam, never through dzpage.com, and the panel doesn't store it. The only things saved are the login that SteamCMD keeps by itself and your Steam account name.

If you'd rather do this later, just leave the name empty and catch up with:

sudo dzpage-panel steam-login yourSteamAccount

That's it. On dzpage.com under RCon, your machine now shows up under Your servers as connected, together with the panel version.

Step 3: Create a server

Under Your servers, click New server for your machine. The form asks for:

• Server name: what the server will be called in the game and in your overview.
• Game port, Steam query port, RCon port: three different ports between 1024 and 65535. The suggested ports are ones that no other server of this panel uses. A second server on the same machine needs its own three.
• RCon password: 8 to 64 characters, no spaces. A random one is suggested, and you never have to type it anywhere.
• Player slots and Mission, for example dayzOffline.chernarusplus for Chernarus.
• Limits: the most memory (MB) and CPU (100 % = one core) the server may use.
• Download the game files right away: has the panel download about 4 GB of DayZ files straight after creating the server.

Create server sends the order to your panel. The panel checks the details again on its own, creates the server and adds it to your DZPage account. As soon as the server is running, you also get the console, player list, messages and bans for it through RCon.

Step 4: Install and start

While the game files download, the overview shows a progress bar with the current line from SteamCMD. Depending on your connection, the first download takes a few minutes.

Once it's finished, the server shows Stopped, with its DayZ build. Click Manage to open its page, then click Start. Shortly after, it shows Running, with uptime and memory. The first time, you start it yourself; after that it starts by itself every time the machine reboots.

Firewall and ports

Players and the DZPage RCon connect to your server from outside. That's why the server's three UDP ports (game, query, RCon) have to be open.

• If ufw or firewalld is active on the machine, the panel opens these ports itself before every start and closes them again when the server is deleted.
• A firewall at your hosting provider (such as the Hetzner Cloud Firewall or a security profile in the customer menu) is invisible to the panel. You have to open the three UDP ports there yourself.
• You do not need to open any port for the panel itself. It connects out to dzpage.com from inside, so it also works behind a router. That only applies to the panel: players and RCon have to reach your server from outside, and that doesn't work behind CGNAT without a public address of your own.

Players can't get in, but the server is running? It's almost always the firewall at your hosting provider.

Day to day

Everything happens under RCon on dzpage.com:

• Your servers shows every server with its state (Running, Stopped, Crashed), uptime, memory and build.
• Manage opens a server's controls: Start, Stop, Restart and Update files.
• Restart schedule: times like 04:00,16:00, warnings like 15,5,1 minutes ahead, and a text of your own. The warning goes into the game over RCon, and the panel does the restart.
• Server log: fetches the last 200 lines of the server process log, handy when a server won't come up.
• The tabs at the top of the server page take you to the RCon features: Console, Players, Messages, Bans and Audit log.
• Delete removes the server along with its game files, saves and configuration. As a safety check, you have to type the server name. This cannot be undone.

If a server crashes, the machine restarts it by itself after ten seconds. Under Manage you can see that on the Restarts counter. If it still stays down, it shows Crashed, and you bring it back up with Start. That's exactly what RCon alone can't do: RCon talks to the game, the panel talks to the process.

Updates

The panel updates itself. Every six hours it checks for a new version and installs it. Your game servers keep running; only the panel restarts briefly. If a new version doesn't work, the panel brings back the previous one by itself.

The DayZ game files you update with Update files. A running server is stopped for this, updated and started again. Since that happens without any warning in the game, it's best to do it when nobody is online.

The panel only checks whether Steam has a newer DayZ version if you allow it to: in the local interface under Updates, which is off by default. Then the overview shows next to the build that an update is available.

Multiple machines and limits

• An account can have up to ten active panel keys, which means ten connected machines. Each machine gets its own key, which you can revoke individually under RCon → Panel keys.
• A machine runs as many servers as its memory and CPU can handle. From dzpage.com you can create servers until there are 20 on the machine.
• Every server runs under its own Linux user with its own limits, and can reach neither the other servers' files nor the panel's configuration.

Connecting without the command

If you installed the panel without a pairing code, for example with

curl -fsSL https://dzpage.com/panel/install.sh | sudo bash

the terminal shows a link like https://dzpage.com/link?code=K7QF-M2XP at the end. Open it, check that the name and address really belong to your server, and click Connect. After that the terminal asks, just like above, whether the DZPage account shown is yours; press Enter and the server is connected. The code in the link is valid for 15 minutes.

If the server isn't connected yet, you can catch up on that at any time with:

sudo dzpage-panel link

This also works after a key has been revoked: the panel notices that dzpage.com rejects it and connects again. You only need --force to move a server whose key still works to another account. When you do, the panel revokes the old key on dzpage.com, as long as no other machine uses it.

The dzpage-panel command

The installer puts a command on the machine for the things you can't do in the browser. If you're root, leave out sudo.

• sudo dzpage-panel status: service, version, address and the connection to dzpage.com (last contact, or a rejected key)
• sudo dzpage-panel link: connect to your DZPage account, also after a revoked key (--force only for another account)
• sudo dzpage-panel steam-login <account>: Steam login for the downloads
• sudo dzpage-panel logs: follow the panel log live
• sudo dzpage-panel setup-code: setup code for the local interface
• sudo dzpage-panel reset-password: new password for the local interface
• sudo dzpage-panel https enable <domain>: local interface over HTTPS
• sudo dzpage-panel uninstall: remove the panel (--purge also deletes the data and revokes the key)

The local interface (optional)

The panel also has its own small web interface as a fallback. You don't need it day to day. It only listens on the machine itself (127.0.0.1:8410) and is deliberately not reachable from outside.

Here's how to reach it anyway, through an SSH tunnel from your own computer:

ssh -L 8410:127.0.0.1:8410 you@your-server

Then open http://127.0.0.1:8410 in your browser. The first time, it asks for the Setup code, which you get with sudo dzpage-panel setup-code, and then for an administrator account.

Security in brief

• The panel never runs as root, and every game server runs under its own user.
• No port is opened for the panel. It connects out to dzpage.com from inside.
• Pairing shows your account before connecting, and the code works only once and only briefly.
• The panel only gets its own key. That key gives no access to your account, and you can revoke it at any time under Panel keys.
• Your Steam password only goes from SteamCMD to Steam, never to dzpage.com.
• The panel's source code is public for anyone to read: github.com/006mi4/dayz-linux-gameserverpanel

Removing it

sudo dzpage-panel uninstall

To be safe, this first asks you to type the word "entfernen" (German for "remove"; type it exactly like that). It then stops the panel and all game servers and removes the services, the game server users, the panel's firewall rules and the program. Game files, saves and configuration stay where they are. A new installation takes the servers over again; they are stopped at that point, and you turn autostart back on in the local interface. If you want to delete the data too (this can't be undone), add --purge; the panel then also revokes its key on dzpage.com first, as long as no other machine uses it. Without --purge the key stays valid, so that a new installation is connected again.

Common problems

Questions, bugs or feature requests? Just post here in this thread or in the Tech & problems forum.