Remote Console (RCON) is the difference between hopping into your V Rising world every time you want to run an admin command and managing your server from anywhere with a lightweight client. On a V Rising dedicated server, RCON is built directly into the configuration — there is no plugin to install. You enable it inside a single JSON file, set a password, open one TCP port, and restart. This guide walks through the entire process for the current 1.1 “Invaders of Oakveil” build, including exactly which file to edit (and which copy of it the server actually reads), the precise fields and default port, how to connect with a standard RCON client, and the firewall and troubleshooting details that trip people up.
If you are still standing up the dedicated server itself, start with our walkthrough on setting up your V Rising dedicated server and then come back here to bolt RCON on top.
What RCON Is and Why You Want It on V Rising
RCON (Remote Console) is a long-standing protocol that lets an external client send administrative commands to a game server over the network. V Rising implements the standard Source-style RCON, which means it speaks the same protocol that tools like mcrcon and rcon-cli were built for. Once enabled, you connect to the server’s IP address on the RCON port, authenticate with a password, and send commands — without ever launching the game client or being physically present in the world.
The practical uses on a V Rising server include:
- Running admin and moderation commands remotely (kicking or managing players) without logging in.
- Automating routine tasks through scripts or scheduled jobs that issue RCON commands.
- Wiring the server up to a web control panel or a Discord bot that relays commands and status.
- Managing the server from a phone or a machine that does not have the game installed.
Because RCON grants administrative control, treat the password like a root credential — anyone who has it can run commands against your server.
Before You Begin: Generate the Config Files
V Rising’s dedicated server is installed anonymously through SteamCMD — no Steam login or game ownership is required. The dedicated server tool uses app ID 1829350 (distinct from the game client’s app ID, 1604030), and the server executable is VRisingServer.exe. Note that Stunlock currently ships a Windows-only server build; their instructions explicitly state there is only a Windows version available. Linux hosting exists only through community Wine/Proton wrappers, which is not an officially supported Stunlock target.
The SteamCMD install command set is:
login anonymous
app_update 1829350 validate
quitAfter installation, the folder includes start_server_example.bat. The official recommendation is to copy it to start_server.bat and edit it (at minimum, set a server name). Crucially, run the server once before customizing — the first boot generates the config files you are about to edit. If you skip this step, the active config files will not exist yet.
Which File Holds the RCON Settings
V Rising uses two JSON config files: ServerHostSettings.json handles network and identity settings, while ServerGameSettings.json handles gameplay rules. RCON lives in ServerHostSettings.json, alongside the ports, server name, and password fields.
Here is the part that catches almost everyone out: there are two copies of these config files on the system, and only one of them is the copy the running server actually reads.
- Default/template copies live in
VRisingServer_Data/StreamingAssets/Settings/inside the install folder. These are overwritten on every server update, and the running save does not read them. Do not edit these. - Active/save-specific copies live in the persistent data path. On a default Windows install this is
%USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRisingServer\Settings\. This path can be overridden with the-persistentDataPathlaunch parameter, which is what most host panels do — they point it at asave-data/folder.
Always edit the active copy under the persistent-data path. If you are on a managed host, that typically appears as save-data/Settings/ServerHostSettings.json in your file manager. Editing the StreamingAssets template version is the single most common reason people swear they enabled RCON and it still will not connect — the server never read their change. For the full breakdown of every field in both files, see our guide on how to configure your V Rising server.
Step-by-Step: Enabling RCON
Step 1 — Stop the server
V Rising loads its configuration at boot and does not hot-reload changes. Stop the server cleanly before you edit anything so that your edits are saved against a known state and applied on the next start.
Step 2 — Open the active ServerHostSettings.json
Navigate to the persistent-data Settings/ folder (the active copy, not StreamingAssets) and open ServerHostSettings.json in a plain-text editor. You will see fields such as Name, Port, QueryPort, Password, and an Rcon object.
Step 3 — Edit the Rcon object
Set the Rcon object to enabled, give it a strong password, and confirm the port. The verified structure is:
"Rcon": {
"Enabled": true,
"Password": "yourStrongPassword",
"Port": 25575
}The three fields do exactly what they say:
Enabled— must be set totrue. With itfalse(the default), the RCON listener never starts.Password— required. RCON refuses connections when no password is set, so an empty password effectively disables it. Use something long and random; this credential grants administrative control.Port— defaults to 25575 over TCP, which is the standard Source-style RCON port. You can change it, but 25575 is what most clients assume by default.
Save the file. Make sure the JSON stays valid — a trailing comma or a missing brace will cause the server to fall back to defaults or fail to read the file. If you are unsure, paste it into a JSON validator before saving.
Step 4 — Restart the server
Start the server back up. Because settings are loaded at boot, the RCON listener now binds to the configured port. On a managed control panel, a simple Restart from the dashboard accomplishes this.
Open and Forward the RCON Port
Enabling RCON in the config makes the server listen, but you still need the network path to reach it. RCON on V Rising uses TCP on port 25575 by default, which is separate from the game and query ports. The full V Rising port picture looks like this:
| Purpose | Default Port | Protocol | Config Field |
|---|---|---|---|
| Game traffic | 9876 | UDP/TCP | Port |
| Steam server-list query | 9877 | UDP | QueryPort |
| RCON remote admin | 25575 | TCP | Rcon.Port |
A quick correction worth flagging: some older guides cite 27015/27016 as V Rising’s defaults. Those are generic Steam values and are not V Rising’s defaults — the authoritative ServerHostSettings.json defaults are 9876 and 9877.
To reach RCON, you need to:
- Open TCP 25575 in the server’s firewall. On Windows, add an inbound rule for the port (and only the port you actually use).
- Forward TCP 25575 on the router if the server sits behind NAT on a home network.
- On a managed host, the port may need to be added in the control panel’s port/network settings; many panels expose RCON as a dedicated port allocation.
Because RCON is administrative, expose it as narrowly as possible. If your provider or firewall supports it, restrict the port to trusted IP addresses rather than the entire internet, and never reuse a password from another service. On XGamingServer plans, the network and port allocations are handled for you — see the V Rising server documentation for the panel-specific steps.
Connecting with an RCON Client
Because V Rising uses the standard Source RCON protocol, any compliant client works. Three common choices:
- mcrcon — a tiny, portable command-line client. Despite the “mc” name, it speaks generic Source RCON and works against V Rising.
- rcon-cli — another lightweight cross-platform CLI, convenient for scripting.
- Web RCON panels / control-panel RCON consoles — many hosts and standalone web tools provide a browser-based console so you do not need to install anything.
Every client needs the same three pieces of information: the server IP, the RCON port (25575 by default), and the RCON password you set. A typical mcrcon invocation looks like:
mcrcon -H your.server.ip -P 25575 -p yourStrongPasswordOnce authenticated, you have an interactive console (or, with a single command appended, a one-shot send) into the running server. If the client connects and authenticates, RCON is working end to end.
Troubleshooting RCON Connections
If a client cannot connect, work through these in order — they cover the overwhelming majority of failures:
- You edited the wrong file. Confirm you changed the active copy in the persistent-data
Settings/folder (or your host’ssave-data/Settings/), not theStreamingAssetstemplate. This is the number-one cause. - You did not restart. Settings load at boot only. A config change with no restart means RCON is still off.
- No password set. RCON refuses connections without a password — an empty
Passwordstring disables it even ifEnabledistrue. - Port not open/forwarded. TCP 25575 must be open in the firewall and forwarded through any NAT. Test reachability from outside the server.
- Invalid JSON. A stray comma or brace can cause the file to be ignored. Validate the JSON.
- Wrong port or protocol in the client. Confirm the client targets the RCON port over TCP, not the game port 9876.
A Note on the Two Config Files and Presets
While you are in ServerHostSettings.json for RCON, it is worth knowing the neighborhood. The file holds the identity and network values that define how your server appears and behaves on the network. Some of the verified defaults:
| Field | Default | Meaning |
|---|---|---|
Name | “V Rising Server” | Server name in the browser |
Port | 9876 | Game traffic port |
QueryPort | 9877 | Steam query port |
MaxConnectedUsers | 40 | Player slot cap |
MaxConnectedAdmins | 4 | Admin slot cap |
SaveName | “world1” | Active save name |
AutoSaveCount | 50 | Number of autosaves kept |
AutoSaveInterval | 600 | Seconds between autosaves |
Gameplay rules — GameModeType (PvP/PvE, plus a Duo PvP mode), ClanSize (default 4, configurable up to roughly 50 on private servers), CastleDamageMode (Always/Never/TimeRestricted), and the various rate multipliers — live in the separate ServerGameSettings.json file. ServerHostSettings.json also exposes a GameSettingsPreset field that loads a named difficulty template (standard PvP/PvE, Duo, and Hard templates exist). The exact preset string names vary, so check the live file rather than copying a string blindly.
Wiping the Server: Handle With Care
RCON administration and full server wipes are different operations, but admins often need both, so it is worth covering the destructive side here. A wipe removes world data, and it cannot be undone without a backup.
Save data lives under the persistent-data path at Saves\v4\. The current persistence-version folder for 1.1.x is v4 — older guides referencing v3 are outdated. On a default Windows install the full path is:
%USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRisingServer\Saves\v4\\ On host panels this typically appears as save-data/Saves/v4/. There are two ways to wipe:
- Delete the
Saves\v4\and restart, or - Change
SaveNameinServerHostSettings.jsonto a new value — the server generates a fresh world and leaves the old save on disk.
A wipe removes all castles and castle hearts, every player vampire character and their progression (gear, V Blood unlocks, research), and the world state for that save. Before wiping, copy the entire Saves\v4\ folder somewhere safe. Auto-saves accumulate according to AutoSaveCount and AutoSaveInterval, but they live inside the save folder — so deleting the save deletes the autosaves with it. The change-SaveName method is the safer route precisely because it preserves the old world. For the full procedure, see our dedicated guide on how to wipe your V Rising server.
Frequently Asked Questions
What port does V Rising RCON use?
The default RCON port is 25575 over TCP, the standard Source-style RCON port. It is independent of the game port (9876) and query port (9877). You can change it in the Rcon object, but most clients assume 25575.
Why won’t my RCON client connect even though I set Enabled to true?
The most common cause is editing the wrong file — the StreamingAssets template copy instead of the active copy in the persistent-data Settings/ folder. Other causes: no password set (RCON refuses passwordless connections), the server was not restarted after editing, or TCP 25575 is not open/forwarded.
Do I need a password for RCON?
Yes. The Password field is required — RCON refuses connections without one, so an empty password effectively disables it. Use a long, random password, since it grants administrative control over the server.
Which RCON client should I use for V Rising?
Any standard Source-RCON client works: mcrcon and rcon-cli are popular command-line options, and many hosts offer a web-based RCON panel so you do not have to install anything. All you need is the server IP, the RCON port, and the password.
Can I run a V Rising server with RCON on Linux?
Stunlock only ships a Windows dedicated server build; their instructions state there is currently only a Windows version. Linux hosting exists only through community Wine/Proton wrappers, which is not officially supported. RCON itself works the same once the server is running, regardless of the wrapper.
Will a server update reset my RCON settings?
Not if you edited the active copy. Updates overwrite the StreamingAssets/Settings/ template files, but the server reads the persistent-data copy, which is preserved across updates. This is another reason to always edit the active copy rather than the template.
Wrapping Up
Enabling RCON on V Rising comes down to four reliable steps: edit the Rcon object in the active ServerHostSettings.json (set Enabled: true, a strong Password, and confirm Port: 25575), open and forward TCP 25575, restart the server, and connect with a Source-RCON client using your IP, port, and password. The two pitfalls to remember are editing the template copy instead of the active one, and forgetting that settings only load on restart. Get those right and you have full remote administration of your world.
Want the whole stack handled for you — anonymous SteamCMD install, the correct ports pre-allocated, and a panel that points -persistentDataPath at the right save folder? Spin up a managed box with XGamingServer’s V Rising hosting and skip the firewall wrestling. From there, deepen your setup with our guides to the best base locations in V Rising and why blood types matter.
Ready to play?
Run your own V Rising server with XGamingServer
Spin up an always-on V Rising server your friends can join in minutes — no port-forwarding, no tech headaches.
