Menu
  Log out
 

V Rising Server Troubleshooting Guide - V Rising Wiki

V Rising Guide • Updated Jan 9, 2026

V Rising Server Troubleshooting Guide

Comprehensive guide to diagnosing and fixing common V Rising dedicated server issues. From connection problems to performance bottlenecks, save corruption, admin access, and voice chat issues, this guide provides step-by-step solutions for server administrators.

Quick Tip: Most V Rising server issues can be resolved by checking port forwarding, verifying server configuration files, ensuring all players have the same game version, and managing save file compatibility.

Common Connection Issues

1. "Failed to Connect" or "Connection Timed Out" Error

Symptoms:

  • Players cannot connect to server
  • "Failed to connect" or "Connection timed out" message appears
  • Server shows in browser but connection fails
  • Players can connect locally but not remotely

Solutions:

  1. Check Port Forwarding: Ensure port 9876 (default UDP) and 9877 (optional query port) are properly forwarded on your router.
  2. Verify Firewall Settings: Add exceptions for V Rising server executable in Windows Firewall or configure iptables on Linux.
  3. Test Local Connection: Try connecting from a device on the same network to rule out internet issues.
  4. Check Server Status: Verify the server process is running with netstat -tulpn | grep 9876 (Linux) or Resource Monitor (Windows).
  5. Update Server Files: Ensure server is updated to latest stable version using SteamCMD.

2. Server Not Showing in Server Browser

Symptoms:

  • Server doesn't appear in V Rising server browser
  • Direct IP connection works but browser doesn't show server
  • Server visibility set to "Public" but not listed
  • Intermittent visibility in browser

Solutions:

  1. Enable Steam Query: Ensure QueryPort=9877 is set in ServerGameSettings.json or server arguments.
  2. Check Query Port: Verify port 9877 is open and accessible (used for Steam queries).
  3. Wait for Registration: Steam server browser can take 5-15 minutes to register new servers.
  4. Server Name Format: Avoid special characters in server name that might break browser listing.
  5. Use Server Browser Commands: Try refreshing browser or restarting game client.

Performance Problems

3. Server Lag and High Ping

Symptoms:

  • Delayed player actions and vampire movements
  • High ping for all connected players
  • World saving causes temporary freezes
  • Castle rendering lag during sieges

Solutions:

  1. Optimize Server Settings: Reduce MaxConnectedUsers or adjust performance settings in ServerGameSettings.json.
  2. Increase Memory Allocation: Ensure server has adequate RAM (minimum 8GB for 40 players).
  3. Reduce Castle Limits: Lower CastleLimitPerPlayer and CastleLimitPerClan if experiencing lag.
  4. Schedule Regular Restarts: Daily server restarts clear memory leaks and improve performance.
  5. Use Performance Optimizations: Consider dedicated hosting with SSD storage and high-clock CPUs.

4. High CPU/Memory Usage

Symptoms:

  • Server process using excessive CPU (90%+)
  • Memory usage constantly increasing over time
  • Server becomes unresponsive after extended uptime
  • Performance degradation with many active castles

Solutions:

  1. Limit Player Count: Reduce MaxConnectedUsers setting to match server capabilities.
  2. Optimize Castle Settings: Adjust castle decay rates and limits to reduce server load.
  3. Regular Restarts: Schedule daily server restarts to clear memory leaks.
  4. Monitor with Tools: Use htop (Linux) or Process Explorer (Windows) to identify resource hogs.
  5. Upgrade Hardware: Consider moving to dedicated hosting with better CPU/RAM resources.

Save and World Issues

5. World Corruption or Save Data Loss

Symptoms:

  • World fails to load on server startup
  • Characters or castles missing after server restart
  • "Failed to load world" error message
  • Map data corruption or missing chunks

Solutions:

  1. Restore from Backup: Use Supercraft's automated backups or manual backup files in SaveGames/ directory.
  2. Verify File Permissions: Ensure server has write access to save directory.
  3. Check Disk Space: Ensure adequate free space for world saves (minimum 5GB).
  4. Use Save Repair Tools: Consider using community tools for V Rising save file repair.
  5. Prevent Corruption: Always use proper shutdown procedure rather than killing process.

6. Character and Castle Data Issues

Symptoms:

  • Character items or progression missing after server transfer
  • Castles disappeared or reset to lower level
  • Clan data corruption or loss
  • Duplicate characters appearing

Solutions:

  1. Backup Save Files: Regularly backup entire SaveGames/ directory.
  2. Check Save Compatibility: Ensure save files match server version (major updates may break saves).
  3. Avoid Cross-Server Transfers: Character and castle data may not be compatible between different server configurations.
  4. Manual Restoration: Replace corrupted save files with backups from known good state.
  5. Preventive Measures: Enable automatic backups and test restore procedures regularly.

Admin and Permission Issues

7. Lost Admin Access

Symptoms:

  • Admin commands not working
  • Cannot access admin panel or use admin features
  • Admin permissions reset after server update
  • Admin list file not being recognized

Solutions:

  1. Check Admin Files: Verify SteamID64 in adminlist.txt (located in SaveGames/ folder).
  2. Use Correct SteamID: Ensure you're using 64-bit SteamID, not username or other ID formats.
  3. File Location: Admin list must be in correct save game folder (matching your server's save slot).
  4. File Permissions: Server must have write access to admin list file.
  5. Verify Syntax: Admin list should contain one SteamID64 per line, no extra characters.

Detailed Guide: See our complete Admin Management guide for step-by-step solutions.

8. Voice Chat (Vivox) Problems

Symptoms:

  • Voice chat not working for players
  • Microphone detection issues
  • Voice chat cutting out or distorted
  • Players cannot hear each other

Solutions:

  1. Verify Vivox Enabled: Ensure "IsVoiceChatEnabled": true in ServerGameSettings.json.
  2. Check Port Configuration: Voice chat uses UDP ports 9876-9880; ensure they're open.
  3. Client-Side Settings: Players must enable voice chat in game settings and configure microphone.
  4. Test Locally: Have two players on same network test voice chat to isolate network issues.
  5. Update Vivox: Ensure server has latest Vivox integration files.

Detailed Guide: See our Vivox Voice Chat guide for complete setup instructions.

Configuration and Settings Issues

9. Server Settings Not Applying

Symptoms:

  • Changes to ServerGameSettings.json not taking effect
  • Server reverting to default settings after restart
  • Configuration file being overwritten
  • Settings inconsistent between server and clients

Solutions:

  1. Verify File Location: Ensure editing correct ServerGameSettings.json in active save folder.
  2. Check JSON Syntax: Use JSON validator to ensure no syntax errors in configuration file.
  3. File Permissions: Server needs write access to configuration files.
  4. Restart Server: Most settings require server restart to take effect.
  5. Backup Original: Always backup configuration before making changes.

10. Difficulty and Game Mode Problems

Symptoms:

  • Difficulty settings not working as expected
  • Game mode (PvP/PvE) not applying correctly
  • Custom preset not loading
  • Balance issues with server settings

Solutions:

  1. Use Preset Files: Start with official preset files (StandardPvP, StandardPvE, Hardcore) and modify.
  2. Validate Settings: Ensure all difficulty-related settings are consistent in JSON file.
  3. Check Version Compatibility: Some settings may change between game versions.
  4. Test Incrementally: Change one setting at a time and test to identify problematic values.
  5. Community Resources: Check V Rising community for recommended settings for your desired gameplay.

Network and Firewall Configuration

# Required Ports for V Rising Server Port 9876 (UDP) - Game traffic (default, configurable) Port 9877 (UDP) - Steam query (optional, recommended) # Additional ports for voice chat (Vivox) Port 9878-9880 (UDP) - Voice chat traffic # Linux iptables rules sudo iptables -A INPUT -p udp --dport 9876 -j ACCEPT sudo iptables -A INPUT -p udp --dport 9877 -j ACCEPT sudo iptables -A INPUT -p udp --dport 9878:9880 -j ACCEPT # Windows Firewall PowerShell New-NetFirewallRule -DisplayName "V Rising 9876-9877" -Direction Inbound -Protocol UDP -LocalPort 9876-9877 -Action Allow New-NetFirewallRule -DisplayName "V Rising Voice 9878-9880" -Direction Inbound -Protocol UDP -LocalPort 9878-9880 -Action Allow # Common ServerGameSettings.json network settings "MaxConnectedUsers": 40, "QueryPort": 9877, "ServerFPS": 60

Diagnostic Commands and Tools

Server Console Commands

# Check server status netstat -tulpn | grep 9876 # Monitor server process (Linux) top -p $(pgrep VRising) # View server logs (typical locations) tail -f ~/.config/unity3d/Stunlock\ Studios/VRisingServer/Logs/*.log tail -f "C:\Users\[User]\AppData\LocalLow\Stunlock Studios\VRisingServer\Logs\*.log" # Test network connectivity nc -zvu your_server_ip 9876 nc -zvu your_server_ip 9877 # Check disk space df -h /path/to/server

Client-Side Diagnostics

  • Steam Network Diagnostics: Steam → Settings → Downloads → Clear Download Cache
  • Verify Game Files: Steam Library → V Rising → Properties → Local Files → Verify Integrity
  • Check Firewall: Ensure V Rising client is allowed through Windows Defender Firewall
  • Update Network Drivers: Ensure network adapter drivers are up to date
  • Client Logs: Check %UserProfile%\AppData\LocalLow\Stunlock Studios\VRising\Logs\ for connection errors

Preventative Measures

Best Practices to Avoid Issues:

  1. Regular Backups: Schedule automated daily backups of save games, configuration files, and admin lists.
  2. Update Management: Test game updates on a staging server before deploying to production.
  3. Monitor Resources: Use monitoring tools to track CPU, memory, and disk usage trends.
  4. Document Configuration: Keep records of server settings, custom changes, and version history.
  5. Community Communication: Inform players of scheduled maintenance, updates, and expected downtime.
  6. Moderation Team: Establish multiple admins to handle issues and prevent single points of failure.

When to Seek Help

If you've tried all troubleshooting steps and still experience issues:

  • Check Official Channels: V Rising Discord server, Stunlock Studios support, official forums
  • Community Resources: Reddit r/vrising, V Rising community wiki, Steam community guides
  • Hosting Provider: Contact Supercraft support for dedicated server assistance and diagnostics
  • Log Collection: Gather server logs, client logs, console outputs, and error messages before seeking help
  • Bug Reporting: Report persistent bugs to Stunlock Studios with detailed reproduction steps

Final Tip: V Rising servers require careful configuration and maintenance. Most issues are solvable with systematic troubleshooting: start with basic connectivity, then configuration, then save files, then hardware/resources.

Need professional V Rising server hosting with automated troubleshooting? Launch your V Rising server with Supercraft for optimized performance and 24/7 support.

← Back to V Rising Guides
Top