Unable to run dedicated server

[ItsMalevolent]

I don't know what changed but we're now unable to launch our dedicated server after the update. The command window opens, I can see task manager allocating memory, then it just drops and the cmd window closes. The log isn't much help either as it doesn't appear to be an actual crash.

Anyone have some basic things I can check? We've already completely uninstalled and reinstalled and tried launching a new server with default everything and still nothing.

This is a windows 2019 server.

[Friesi]

Same here, can't also find any logs which are helpful

[alan0n]

Had the same issue.

Was related to the fact that I had the IP set to an external ipv4 address while the actual network address of that machine was on a local subnet.

Basically I removed the IP: "xxx.xxx.xxx.xxx", line from the ServerHostSettings.json file and it came right back up.

[Ebon Lord]

Hello, here to post a solution to fellow V Rising servers hosts having this problem. We can rollback to the last version that is not broken this way :

Open the steam console : Windows+R then steam://open/console
Paste this in : download_depot 1829350 1829351 1920063827468227702
Download was slow for me compared to a classical download.

Now you just need to copy your map & settings to the newly downloaded folder and you should be good. Had to rollback one save, the server crashes if you give him a map with the last version.

There are other tutorials on how to rollback version of Steam apps on the Internet if this one does not work for you. Good luck !

[TheBlastMage]

Can this be done on hosted services like Nitrado? I don't see a way to run specific updates through there, though the server does update nearly every time I reboot it.

[HerZie]

Originally posted by chrsschb:

I don't know what changed but we're now unable to launch our dedicated server after the update. The command window opens, I can see task manager allocating memory, then it just drops and the cmd window closes. The log isn't much help either as it doesn't appear to be an actual crash.

Anyone have some basic things I can check? We've already completely uninstalled and reinstalled and tried launching a new server with default everything and still nothing.

This is a windows 2019 server.

Did you solve it? I have the same issue after the latest update. I even deleted everything and re-downloaded the server files through steamcmd. Before this I ran the server a full year since the game came out without issues.

[Durzo]

Solution is to delete VRisingServer_Data\Plugins\x86_64\lib_burst_generated.dll from your dedicated server, and turn off steam auto-update and/or verify files.

I just did this on mine and it started up fine (i'm running in a container via pterodactyl)

[HerZie]

Originally posted by Durzo:

Solution is to delete VRisingServer_Data\Plugins\x86_64\lib_burst_generated.dll from your dedicated server, and turn off steam auto-update and/or verify files.

I just did this on mine and it started up fine (i'm running in a container via pterodactyl)

Excellent! This indeed fixed the issue. Thanks.

[Odium]

I can get a server running but cant join at all,. even the old 127.0.0.1 doesnt work. besides that Fidium routers port forward via ip assignment and internal/external ports, I cant just forward ranges. Its silly