This guide covers common issues you may encounter with your V Rising dedicated server and how to resolve them. For initial server configuration and connecting, see V Rising Dedicated Server Setup Guide.

Server Not Appearing in the Server Browser

If your server is running but does not show up in the Steam or in-game server browser:

• Open the Network tab in GPanel and confirm the assigned query port. Then verify that the QueryPort value in ServerHostSettings.json matches exactly.
• Ensure "ListOnSteam" is set to true in ServerHostSettings.json. If it is set to false, the server will not be listed.
• After starting or restarting the server, it can take 5 to 15 minutes for the server to appear in the browser. Use direct connect to verify the server is reachable in the meantime.
• Confirm the server status shows as Online in GPanel. If the server crashed or failed to start, it will not register with the Steam master server.

Config Changes Not Taking Effect After Restart

If you edited ServerHostSettings.json or ServerGameSettings.json but your changes are not reflected on the server:

• Stop the server before editing. V Rising writes configuration files on shutdown. If the server is still running when you edit a file, it may overwrite your changes when it shuts down. Always stop the server from GPanel first, then edit, then start.
• Check for JSON syntax errors. JSON format is strict -- a single misplaced comma, missing quote, or trailing comma will cause the file to fail silently. The server may revert to default settings without displaying an obvious error.
• Verify the file was saved. After editing in the GPanel file editor, click the Save button before navigating away.
• Check the console output. After starting the server, look at the console in GPanel for any warnings or errors related to configuration loading.

Players Cannot Connect (Correct IP and Port)

If players have the right IP address and port but still cannot connect:

• Confirm the Port value in ServerHostSettings.json matches the game port shown in GPanel's Network tab. Do not assume default port values -- check GPanel Network tab for the actual assigned ports.
• Ensure the server is fully started and shows as Online in GPanel. A server that is still loading will reject connections.
• If the server has a password set in ServerHostSettings.json, players must enter it when prompted. An empty password value ("") means no password is required.
• Ask the connecting player to verify they are entering the address in the format IP:PORT with no spaces, and that they are using the game port, not the query port.
• Check if the player is banned. An admin can run banlist in the server console, or check the banlist.txt file in VRisingServer_Data/StreamingAssets/Settings/.

World Not Generating on First Start

If the server appears to be stuck after the first startup and no world is created:

• Wait at least 3 to 5 minutes. World generation on the first launch takes significantly longer than subsequent startups. The server may appear unresponsive during this time.
• Check the console output in GPanel for any error messages. If the server encounters a fatal error during generation, it will display an error and stop.
• Ensure the SaveName in ServerHostSettings.json does not contain special characters or spaces. Use only letters, numbers, and underscores (e.g. "world1").
• If the server shuts down immediately after starting, there may be a configuration error. Review both ServerHostSettings.json and ServerGameSettings.json for syntax issues.

Server Crashes or Stops Unexpectedly

If your server shuts down or crashes without warning:

• Check the console output in GPanel for any error messages that appeared before the crash. Copy these messages -- they are essential for diagnosing the issue.
• Ensure your server has not exceeded its allocated memory. V Rising dedicated servers typically require at least 4 GB of RAM. If your plan is undersized, the server may be killed by the system when it runs out of memory.
• If crashes happen after a game update, check the V Rising community forums or patch notes for known server issues. Sometimes a fresh config regeneration is needed after major updates.
• Try removing any recently changed settings from ServerGameSettings.json by reverting to defaults. Invalid setting combinations can cause crashes that do not produce clear error messages.

Castle Decay Happening Too Fast (or Not at All)

Castle decay rates are controlled by the CastleDecayRateModifier setting in ServerGameSettings.json:

Remember to stop the server before editing this value, and restart the server for the change to take effect.

Admin Commands Not Working

If you have added your SteamID to the admin list but commands are not working:

• Verify the console is enabled in your game options (Options > General > Console Enabled).
• Make sure you run adminauth in the console after connecting. Admin privileges are not granted automatically -- you must authenticate each session.
• Double-check that your SteamID64 in adminlist.txt is correct. It must be the 17-digit SteamID64, not a vanity URL or SteamID3 format.
• Ensure adminlist.txt is in the correct directory: VRisingServer_Data/StreamingAssets/Settings/.
• The server must be restarted after changes to adminlist.txt. The file is only read on startup.

For a full list of admin commands and setup instructions, see V Rising Admin Commands and Setup.

Related Articles

• V Rising Dedicated Server Setup Guide
• V Rising Admin Commands and Setup