How much machine does a Pavlov server need?
Less memory than you might expect, and more clock speed. The Pavlov wiki's setup guide gives these figures from providers' experience, not a benchmark:
| Your server | Memory | Processor clock |
|---|---|---|
| About 10 players, stock maps | 2 GB | About 2.5 GHz |
| 24 or more players, content mods or large maps | 4 GB, more for big maps | About 4 GHz |
| Each extra server on the same machine | Its own share, sized as above | One more core, with one core kept spare overall |
The PC version takes up to 50 players, though the guide advises staying at 24; Shack, the Quest version, stops at 24. Running short of memory is a common cause of crashes, so treat those figures as floors.
Extra cores do nothing for a single lobby, because the server is functionally single-threaded. They matter once you run several: the rule is one core per server plus one spare, so an eight-core processor carries seven servers at most.
Why a whole machine suits a Pavlov lobby
Because the thread that runs every match cannot share. On a dedicated server the processor is yours alone: nobody else's job lands on your core mid-round, and the speed you measure on night one is the speed you keep.
The port is unmetered and not shared with another customer at the access switch, so a full lobby never becomes a traffic bill. Players notice latency first, and latency is mostly distance. The machines sit in New York, Miami, San Francisco, Amsterdam and Bucharest, and our locations page times each city from your own browser.
You also get root on a clean system, which this install needs for its 32-bit libraries, steam user and systemd service.
The machines that fit
Choose by clock speed first. Our game server machines are ranked by single-thread score, with the cities, memory ceilings and drives of each line beside them.
- Friends, around ten players: the Intel Xeon E3-1585L v5 class, four cores at 3.0 GHz rising to 3.7 GHz, 32 GB of memory and NVMe, sold in all five cities.
- 24-player lobbies or heavy mods: the guide points at about 4 GHz. The AMD EPYC 72F3 runs at 3.7 GHz rising to 4.1 GHz in New York and Bucharest; the Intel Xeon E-2286M rises from 2.4 GHz to 5.0 GHz in Bucharest.
- A community with many servers: one of the many-core EPYC or Xeon Gold machines lower in the table.
A racked machine is handed over about 30 minutes after the order is approved; the payment check comes first and is the part that varies.
Up and running in an evening
Pick Ubuntu 24.04 at checkout: it is on the Pavlov guide's list of known-good systems. These steps follow that guide, typed over SSH.
Step 1. As your admin user, install the dependencies and create the steam user that will own the server, then switch to it:
sudo apt update && sudo apt install -y gdb curl lib32gcc-s1 libc++-dev unzip
sudo useradd -m steam
sudo chsh -s /bin/bash steam
sudo su -l steam
Step 2. As steam, fetch SteamCMD, install the PC server and copy a fresh steamclient.so to where the server looks for it. Swap default for beta_server for the PC beta, or shack or shack_beta for the Quest builds:
mkdir ~/Steam && cd ~/Steam && curl -sqL "https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz" | tar zxvf -
~/Steam/steamcmd.sh +force_install_dir /home/steam/pavlovserver +login anonymous +app_update 622970 -beta default +exit
~/Steam/steamcmd.sh +login anonymous +app_update 1007 +quit
mkdir -p ~/.steam/sdk64
cp ~/Steam/steamapps/common/Steamworks\ SDK\ Redist/linux64/steamclient.so ~/.steam/sdk64/steamclient.so
cp ~/Steam/steamapps/common/Steamworks\ SDK\ Redist/linux64/steamclient.so ~/pavlovserver/Pavlov/Binaries/Linux/steamclient.so
chmod +x ~/pavlovserver/PavlovServer.sh
Step 3. Type exit to get back to your admin user. The guide points the system's libc++.so at libc++.so.1; it deletes the original, but moving it aside keeps a copy you can restore: sudo mv /usr/lib/x86_64-linux-gnu/libc++.so /usr/lib/x86_64-linux-gnu/libc++.so.orig && sudo ln -s /usr/lib/x86_64-linux-gnu/libc++.so.1 /usr/lib/x86_64-linux-gnu/libc++.so
Step 4. Get your server key. In the game, open Settings, then General, then Server Key Generator for a six-digit PIN, and enter your Steam ID and that PIN on Vankrupt's key page (api-key.vankrupt.net). The key goes into Game.ini in the next section.
Step 5. Save the guide's unit below as /etc/systemd/system/pavlovserver.service.
[Unit]
Description=Pavlov VR dedicated server
[Service]
Type=simple
WorkingDirectory=/home/steam/pavlovserver
ExecStart=/home/steam/pavlovserver/PavlovServer.sh
RestartSec=1
Restart=always
User=steam
Group=steam
[Install]
WantedBy = multi-user.target
Step 6. Allow SSH before anything else so you cannot lock yourself out, open the two game ports, then start the server and have it start on boot: sudo ufw allow OpenSSH && sudo ufw allow 7777 && sudo ufw allow 8177 && sudo ufw enable && sudo systemctl enable --now pavlovserver
Step 7. The first start writes the config folders. Stop it with sudo systemctl stop pavlovserver, edit Game.ini as steam, then start it again and follow the log with sudo journalctl -u pavlovserver -f.
On Ubuntu, ufw writes each rule for IPv4 and IPv6 alike. Pavlov itself does not support IPv6, so players reach you on the machine's IPv4 address. A rule without a protocol opens TCP too, which Quest players need to download maps from you.
Game.ini: the lines worth changing
The file is /home/steam/pavlovserver/Pavlov/Saved/Config/LinuxServer/Game.ini, under the heading [/Script/Pavlov.DedicatedServer]. Edit it as steam and restart the service afterwards.
| Setting | What it controls | Example |
|---|---|---|
| ServerName | The name in the browser, about 35 characters at most | ServerName="Friday Night SND" |
| MaxPlayers | Slots; 24 recommended on PC, 24 is the Shack limit | MaxPlayers=10 |
| ServerKey | Registers the server with the master list | ServerKey= and your key |
| bSecured | Valve Anti-Cheat | bSecured=true |
| bCustomServer | Extra tools; needed for bans in blacklist.txt | bCustomServer=true |
| bWhitelist | Only players in whitelist.txt may join | bWhitelist=false |
| Password | A join PIN; leave the line out for a public server | Password= and a number |
| TickRate | Default 90; changing it breaks some modes | TickRate=90 |
| MapRotation | One line per map, played in order | MapRotation=(MapId="datacenter", GameMode="SND") |
| AdditionalMods | One line per mod.io content mod | AdditionalMods=UGC and the mod's ID |
A profanity filter can hide a server over a harmless name, so keep it plain. While you configure, a PIN keeps strangers out: a whole number from 1 to 9999 without leading zeros. Remove it when you open the doors.
Maps, moderators and RCON
Maps and content mods come from mod.io. Take the resource ID from a mod's mod.io page and put UGC in front of it, so resource 2773760 becomes UGC2773760, then use that as a MapId in a rotation line or in an AdditionalMods line.
Three text files sit in Pavlov/Saved/Config: blacklist.txt for bans, whitelist.txt for the allowed list, and mods.txt. Despite its name, mods.txt lists moderators, the players who get the admin menu, not content mods. The server re-reads all three every RefreshListTime seconds.
RCON lets you kick, ban and switch maps without a headset. Turn it on with RconSettings.txt in that same Config folder: one line Password= followed by a long password of your own, and one line Port=9100. Every server on the machine needs a different RCON port.
RCON is a plain-text TCP stream that sends the password as a bare MD5 hash. Keep port 9100 closed in the firewall and reach it through an SSH tunnel from your own computer. The wiki warns that hosted RCON websites could keep your password; prefer an open-source tool you run yourself.
Keeping it healthy
- Updates: run the
app_update 622970line again whenever Pavlov updates, and repeat thesteamclient.socopies after it. The guide also offers a nightly update script for root's crontab; schedule it for when your lobby is empty. - Backups: the setup is a few text files, so copy the Config folder off the server after every change.
- Security: the guide says the server code has had no security review. Run it as the unprivileged
steamuser, never root, and keep nothing on the machine you would mind losing. - More servers: copy the install folder with
cp -r pavlovserver pavlovserver1, start each copy with its own-PORT=, and open both that port and the one 400 above it.
When this is the wrong place to run it
- You want a panel and one-click installs. You get the bare machine with root; we do not install, mod or update games for you.
- You expect attacks. No machine of ours comes with a defence against denial-of-service floods, and none is sold as an extra. A public server that draws trouble needs its own plan before launch.
- You play twice a month with three friends. A whole machine is far more than that needs.
Stuck on a step? Our chat AI answers in seconds and can check your server for you, and a person takes over whenever you ask.
Questions people ask
- Will the Pavlov server run on Windows Server?
- No. The Pavlov setup guide says there are no Windows binaries, so the server runs only on Linux. Its known-good systems are Ubuntu 18.04 to 24.04 and Rocky Linux 8. Choose Ubuntu 24.04 when you order.
- My server is running, so why is it missing from the in-game list?
- Usually one of three things. Game.ini needs a
ServerKeyfrom Vankrupt, UDP 7777 and 8177 must be open, and the name has to pass the profanity filter. Allowing ping also helps the list show your real latency. - How many players can a single Pavlov server take?
- Up to 50 on PC, where the guide recommends 24, and 24 on Shack for Quest. For 24 it points at a processor near 4 GHz and 4 GB of memory.
- Can I host the Quest version too?
- Yes. The same SteamCMD app takes
-beta shackfor the live Shack build or-beta shack_betafor its release candidate. Quest players download maps from your server, so createPavlov/Saved/mapsand open your game ports over TCP as well as UDP.