Your V Rising server is up. The panel light is green, the console has stopped scrolling, and your clan is staring at a server browser that flatly refuses to admit the thing exists. Or worse: one person can see it and nobody else can.
Almost every guide written about this assumes you are hosting on your own PC behind a home router, so it opens with twenty minutes of port forwarding advice. If you rent your server, that advice is noise and the real cause is somewhere else entirely. Here is the actual list, ordered by how often each one turns out to be the answer.
Give the Server Its Registration Window
A V Rising server does not appear in the browser the moment the process starts. It has to load the save, finish booting, then announce itself to the master server and to Epic Online Services. Only once that announcement has been indexed does anyone see your server name in a list.
On a cold start with a fresh world that takes a couple of minutes. On an established world with a large save and a full clan roster, five to ten minutes is normal. A restart after a settings change goes through exactly the same cycle, which is why "I changed one setting and now it's gone" is such a common complaint. It is not gone, it is re-registering.
So the first rule is boring, and it resolves a large share of these tickets anyway. Wait ten minutes from the moment the process started before you change anything. Editing settings mid-registration just restarts the clock.
Check Both Listing Flags, in the Right File
V Rising has more than one visibility switch and they do not do the same job. In ServerHostSettings.json:
{
"Name": "Doom Clan Nightfall",
"Port": 9876,
"QueryPort": 9877,
"ListOnMasterServer": true,
"ListOnEOS": true,
"Secure": true
}
ListOnMasterServer handles the Steam side of the listing. ListOnEOS handles the Epic Online Services listing that the in-game browser leans on. Set one true and the other false and you get the classic split symptom: half your group finds the server, half cannot, and everyone assumes the ones who cannot are doing something wrong. For a normal public or password-protected server, both belong on true.
Then there is the trap that eats an entire evening. Two copies of the settings files exist. The templates ship in VRisingServer_Data/StreamingAssets/Settings/, and the live copies the server actually reads sit in the save-data Settings/ folder. Editing the template does nothing at all: no error, no warning, the server simply keeps running the values it already had. Confirm you are editing the file under save-data, not the one under StreamingAssets.
Settings are read once at boot, too. There is no hot reload. If you edited the right file and did not restart, the server is still on the old values.
Fix Your Filters Before You Blame the Server
The in-game browser hides more than people expect, and it hides it silently.
- Password-protected servers are filtered out by default. If you set a
Password, that filter has to be switched on or your server is invisible to everyone who has not already done it. - The PvP and PvE toggles do exactly what they say. A PvE server will not show while the list is filtered to PvP.
- Region and ping filters quietly drop a server hosted on another continent from your group's list even though it is perfectly healthy.
- Search matches the
Namevalue inServerHostSettings.jsoncharacter for character. Not the name you gave the service in billing, and not what you meant to type.
One more that catches modded clans: a heavily modded server often will not appear in the vanilla browser at all. Direct Connect is the expected way in there, not a workaround.
Direct Connect Wants the Game Port
V Rising uses two UDP ports. 9876 carries game traffic and 9877 answers queries. The browser listing depends on the query port. Actually joining depends on the game port.
Direct Connect takes IP:9876. Pasting the query port there fails every time, and it is an easy mistake to make because plenty of panels print both numbers next to each other. Watch for a stray space on the end of a pasted address as well, since the client treats it as part of the address and the connection just fails.
That split gives you a genuinely useful diagnostic. If Direct Connect works but the browser never shows the server, the game port is fine and your problem is the query port or the listing flags. If Direct Connect fails too, the server is not reachable at all and you should be looking at the process, not the listing.
Self-hosting at home, both ports need forwarding on UDP plus a Windows Firewall rule. On a rented server they are allocated and open for you, so copy the connect address straight out of the panel rather than typing one from memory.
When It Is the Patch or the Mods
Two causes produce a server that looks perfectly healthy and that nobody can reach.
Version mismatch. Stunlock ships a client patch, your clan updates automatically through Steam, and the server is still running last week's build. A mismatched server drops out of the browser for updated clients. Restart it so it pulls the new build, and do that before you start reading logs.
A mod killing the server at boot. V Rising modding runs on BepInEx, and a mod built against an older game version can throw during load. The process stays up long enough to look alive but never reaches the point of registering. Open the console and read from the top rather than the bottom, because the first stack trace names the assembly at fault. Remove whatever you installed most recently, restart, and confirm the server registers clean before you add it back. Client-side mod mismatches cause the same "cannot join" symptom from the other direction, so check that the whole clan is running the same mod list.
The 60-Second Triage
Next time it happens, work it in this order:
- Has the process been up for ten full minutes? If not, wait.
- Does Direct Connect on
IP:9876work? If it does, this is a listing problem, not a connectivity one. - Are
ListOnMasterServerandListOnEOSbothtrue, in the save-data copy ofServerHostSettings.json? - Did you restart after editing?
- Are the browser's password, PvP/PvE and region filters actually letting your server through?
- Is the server running the current game build?
- Does the console show a mod failing during load?
Nearly every invisible V Rising server is one of those seven, and the first three account for most of them. If you want to go deeper on what each setting does, our guide to V Rising server settings walks the whole file, and the mods roundup covers which BepInEx mods tend to survive a patch cycle. Renting instead of self-hosting removes the port and firewall half of this list entirely: see V Rising server hosting.
