Install a V Rising server

Step-by-step installation

1. 1

   Check the requirements (CPU, RAM, disk) and choose the host: Windows PC, VPS or dedicated server.

2. 2

   Install SteamCMD and download the server (Steam app 1829350).

3. 3

   On Linux create a non-root user and a dedicated folder; on Windows use a simple folder (e.g. C:\server).

4. 4

   Start the server once to generate its configuration files, then stop it cleanly.

5. 5

   Configure name, password and slot count (see our V Rising tools to generate the files).

6. 6

   Open ports 9876/UDP, 9877/UDP in the system and provider firewalls; forward them on your router if you host at home.

7. 7

   Test locally (127.0.0.1), then from a connection outside your network.

8. 8

   Create a systemd service (Linux) or a scheduled task (Windows) for automatic startup.

9. 9

   Schedule server backups and updates.

10. 10

    Add your server on game-rank.com/jeux/v-rising to get it known.

Requirements

• System: Windows (Linux possible through Wine, unofficial).
• Hardware: not officially documented in the sources consulted; starting point to adjust to your load: RAM 8 / 16 GB, disk 10 GB.
• Steam account: SteamCMD can download the server with an anonymous login; only players need to own the game.
• Network: a public IP (or port forwarding) with ports 9876/UDP, 9877/UDP open.
• Access: SSH (Linux) or Remote Desktop (Windows Server); an SSD is recommended.

Local installation (Windows)

Install SteamCMD (steamcmd.exe) in a dedicated folder, then run the commands below in a command prompt. Then start the server and join it from the game on 127.0.0.1.

steamcmd +force_install_dir C:\vrising-server +login anonymous +app_update 1829350 validate +quit
cd C:\vrising-server
VRisingServer.exe -persistentDataPath ".\save-data" -logFile ".\logs\VRisingServer.log"

Linux server through Wine (unofficial) or Windows Server

This server is built for Windows: the developer does not document a Linux version. On Linux, hosts and the community run it with Wine, with no guarantee or official support; Windows Server remains the most reliable option. Test before going live.

Create a dedicated user without root rights, install the 32-bit dependencies required by SteamCMD, then download the server. Adapt the user name and folders to your habits.

sudo dpkg --add-architecture i386
sudo apt update && sudo apt install -y curl tar lib32gcc-s1 wine wine64 xvfb
sudo adduser --disabled-password --gecos "" vrising
# then, as the vrising user (sudo -iu vrising):
mkdir -p ~/steamcmd ~/vrising-server && cd ~/steamcmd
curl -sqL "https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz" | tar zxvf -
./steamcmd.sh +@sSteamCmdForcePlatformType windows +force_install_dir ~/vrising-server +login anonymous +app_update 1829350 validate +quit
# first start (foreground test):
cd ~/vrising-server
/usr/bin/xvfb-run --auto-servernum /usr/bin/wine64 VRisingServer.exe -persistentDataPath ./save-data -logFile ./logs/VRisingServer.log

Ports to open

Default values; traffic direction is inbound (towards the server).

To change a port, edit it in the server configuration or launch line (ServerHostSettings.json: Port, QueryPort), then adapt the firewall.

• 9876/UDP — game traffic
• 9877/UDP — Steam queries / server list
• 25575/TCP — RCON (optional, do not expose without a strong password)

Linux firewall (ufw), provider and router

Allow SSH first so you do not lock yourself out, then the game ports. Ports are only reachable if they are also open in the provider firewall (OVH, Hetzner, Scaleway…: "security group" or the panel's network rules).

Hosting at home: create a port forward (NAT) on your router to the server's fixed local IP, for the same ports and protocols. If your ISP uses CGNAT (no public IPv4), forwarding is impossible: ask for a public IP or rent a VPS.

Testing: UDP cannot be tested with a simple web port checker; verify by joining from the game on an outside network (a mobile hotspot, for example) and check the server logs.

sudo ufw allow 22/tcp
sudo ufw allow 9876/udp
sudo ufw allow 9877/udp
sudo ufw enable
sudo ufw status verbose

Windows firewall (netsh)

Run these commands in a command prompt started as administrator. When hosting at home, also add the port forward on your router.

netsh advfirewall firewall add rule name="V Rising 9876 UDP" dir=in action=allow protocol=UDP localport=9876
netsh advfirewall firewall add rule name="V Rising 9877 UDP" dir=in action=allow protocol=UDP localport=9877

Automatic start on Linux (systemd)

The service restarts the server after a crash and when the machine boots. Enable it with the commands shown in the block.

[Unit]
Description=V Rising dedicated server (Wine, unofficial)
After=network-online.target
Wants=network-online.target

[Service]
User=vrising
WorkingDirectory=/home/vrising/vrising-server
Environment=WINEDEBUG=-all
ExecStart=/usr/bin/xvfb-run --auto-servernum /usr/bin/wine64 VRisingServer.exe -persistentDataPath ./save-data -logFile ./logs/VRisingServer.log
Restart=on-failure
RestartSec=10
KillSignal=SIGINT
TimeoutStopSec=90

[Install]
WantedBy=multi-user.target

# sudo nano /etc/systemd/system/vrising.service
# sudo systemctl daemon-reload && sudo systemctl enable --now vrising
# journalctl -u vrising -f

Automatic start on Windows (scheduled task)

Create a task that runs the start script when Windows boots, under a dedicated account if possible. Adapt the script path.

schtasks /Create /TN "V Rising Server" /TR "C:\vrising-server\start.bat" /SC ONSTART /RU SYSTEM /RL HIGHEST
schtasks /Run /TN "V Rising Server"
schtasks /End /TN "V Rising Server"

Updates, backups and restarts

Stop the server before any update, back up the data, then restart. Schedule backups with cron (Linux) or Task Scheduler (Windows), and a daily restart if the game leaks memory.

sudo systemctl stop vrising
/home/vrising/steamcmd/steamcmd.sh +@sSteamCmdForcePlatformType windows +force_install_dir /home/vrising/vrising-server +login anonymous +app_update 1829350 validate +quit
sudo systemctl start vrising
# Windows: steamcmd +force_install_dir C:\vrising-server +login anonymous +app_update 1829350 validate +quit

mkdir -p ~/backups
tar czf ~/backups/vrising-$(date +%F).tar.gz -C ~/vrising-server save-data
find ~/backups -name 'vrising-*.tar.gz' -mtime +14 -delete
# crontab -e   ->   30 4 * * * <the two lines above, as a script>

Listing and finding your server

Once the server is stable, add it on game-rank.com/jeux/v-rising (the website of the owner of these tools) with its connection address, slots, language and version. Direct connection address to share: <IP>:9876 (depending on the game version). Never publish an admin password.

Troubleshooting

• The server does not appear in the list — cause: query ports closed or server not listed. Fix: open 9876/UDP, 9877/UDP, check name/password and wait a few minutes; join directly by IP to test.
• Cannot connect from the Internet but fine locally — cause: system/provider firewall, missing port forward or CGNAT. Fix: check all three levels (ufw/Windows, provider, router) and the protocol (UDP/TCP).
• The server exits at startup or runs out of memory — cause: not enough RAM, missing libraries or wrong working directory. Fix: run it in the foreground, read the logs, add RAM or swap.
• Players see an incompatible version after a game update — cause: server not updated. Fix: stop it, update it (see the Updates section), then restart.
• Configuration changes are ignored or overwritten — cause: file edited while the server runs, wrong folder or syntax error. Fix: stop the server, edit the right file, validate the syntax (JSON/XML) and restart.

Frequently asked questions

What machine do I need for a V Rising server?

Hardware: not officially documented in the sources consulted; starting point to adjust to your load: RAM 8 / 16 GB, disk 10 GB.

Which ports should I open?

Open 9876/UDP, 9877/UDP inbound, in the system firewall, at the provider and on your router if needed. These are the default values and can be changed in the server configuration.

Do I need to own the game to host?

The dedicated server is downloaded for free with SteamCMD (anonymous login); only players need to own the game.

How do I update the server?

Stop the server, re-run the SteamCMD command +app_update 1829350 validate (see the Updates section), then restart. For a beta branch, add -beta <name>.

Can I host at home?

Yes, if your connection has a public IP and you can forward ports on your router. With CGNAT or a weak upload, prefer a VPS or dedicated server.