Menu
  Log out
 

VEIN Dedicated Server Setup: App 2131400, Ports & First Join

VEIN Guide • Updated Sep 24, 2026

VEIN Dedicated Server Setup

This guide follows the public VEIN dedicated-server reference. VEIN is in Early Access, so compare the installed package with the reference whenever a binary, flag, or config path changes.

Reference facts

  • Steam app: 2131400
  • Platforms: 64-bit Windows or 64-bit Linux. The reference is written and tested for Windows; the same Steam app also ships a native Linux server, started by VeinServer.sh (checked on build 25035268, 24 September 2026).
  • Ports: UDP 7777 game, UDP 7778 query; TCP 7777 is optional if the current setup uses RCON.
  • Starting memory guidance: the reference says to start with at least 8 GB; measure your own world before scaling up.

Install the server app

Use the Steam tool or SteamCMD with the current app ID. Keep the install path and build/branch in your notes. If a provider exposes a one-click template, confirm which app and branch it actually deploys.

force_install_dir C:\VEINServer
login anonymous
app_update 2131400 validate
quit

On Linux, run the same SteamCMD commands with a Linux path such as /home/vein/server. SteamCMD downloads the native Linux build of app 2131400 automatically.

These commands are a starting pattern; use the current SteamCMD syntax and the package's actual files if the reference changes.

Launch the server on Windows or Linux

On Windows, the reference launches the 64-bit binary directly:

VeinServer-Win64-Test.exe -log -port=7777 -MaxPlayers=64

On Linux, start the native build from the install folder with the same flags. VeinServer.sh runs Vein/Binaries/Linux/VeinServer-Linux-Test and passes every flag through:

./VeinServer.sh -log -port=7777 -MaxPlayers=64

The Windows line is the example shown in the community-maintained dedicated-server reference. Neither line is a permanent promise that every branch keeps the same executable or player limit, so verify the current binary and choose a player limit your world and host can sustain.

Open the documented ports

PortTransportPurpose
7777UDPGame traffic
7778UDPQuery/listing traffic
7777TCPOptional RCON path when enabled by the current setup

Keep provider mapping, firewall rules, launch flags, and the address given to players consistent. Query success does not prove game traffic is reachable.

First-join test

  1. Start with one trusted player.
  2. Confirm the server appears or connect using the current host's documented endpoint.
  3. Test a harmless world change and a reconnect.
  4. Stop cleanly and verify that the save is still present.
  5. Only then invite the rest of the group.

When setup fails

  • Process exits: compare the binary, branch, working directory, and log.
  • Not listed: check the query port and listing state.
  • Listed but cannot join: check UDP game traffic, firewall, provider mapping, and client/server build.
  • Linux server runs but never appears in the browser: it must register under VEIN's game app ID, 1857950, and the package ships no steam_appid.txt. Put one containing 1857950 in the install folder, or export SteamAppId=1857950 before launching.
  • Linux log says steamclient.so cannot be opened: copy steamclient.so from your SteamCMD install's linux64 folder into ~/.steam/sdk64/ for the user that runs the server.
  • Wrong world: stop changing ports and follow the save workflow.

Related guides

Launch managed VEIN hosting with the current plan details shown on the product page.

Tired of fighting this issue every patch?

Run a managed VEIN server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See VEIN hosting plans →
← Back to VEIN Guides
Top