favicon192Gamer Hosting: Useful Software Kiwami

Server Setup Guide for [Deep Rock Galactic (private lobbies)] Gamers

Game Server Requirements

Setting up a dedicated server for Deep Rock Galactic, especially for private lobbies, offers a more stable and customizable experience than relying solely on in-game hosting. Understanding the underlying hardware and software requirements is crucial for a smooth operation. While Deep Rock Galactic itself is not overly demanding, a dedicated server needs sufficient resources to handle game logic, player connections, and potential modding.

For the server operating system, Linux distributions (Ubuntu Server LTS, Debian) are generally preferred due to their efficiency and lower resource overhead compared to Windows Server, though Windows Server is also a viable option if you're more comfortable with it. The game server application itself is designed to run on both.

Regarding CPU, a modern dual-core processor (e.g., Intel Core i3 or AMD Ryzen 3 equivalent or better) is typically sufficient for a small to medium-sized private lobby (2-8 players). For larger groups or if you anticipate running multiple game instances or other services on the same machine, a quad-core or higher CPU would be beneficial. Clock speed is often more important than core count for game servers, so aim for a CPU with a high single-thread performance.

Memory (RAM) is another critical component. A minimum of 4GB of RAM is recommended for the server operating system and the Deep Rock Galactic server application. However, to ensure smooth performance, especially with multiple players, background processes, or if you plan to use mods, 8GB or even 16GB of RAM is highly advisable. This provides ample headroom and prevents the server from swapping to disk, which can introduce significant latency.

Storage requirements are relatively modest for the game files themselves. A solid-state drive (SSD) is strongly recommended over a traditional hard disk drive (HDD) for the operating system and game server files. SSDs offer significantly faster read/write speeds, which translates to quicker server startup times and reduced loading screens for players. A 120GB SSD should be more than enough for the OS and the Deep Rock Galactic server files, with plenty of room for logs and future updates.

Network connectivity is paramount for a good multiplayer experience. A stable internet connection with at least 100 Mbps symmetrical bandwidth (upload and download) is recommended for a dedicated server. While Deep Rock Galactic doesn't consume an enormous amount of bandwidth per player, consistent low latency is crucial. A wired Ethernet connection is always preferred over Wi-Fi for the server machine to minimize packet loss and latency fluctuations. Ensure your router is capable of port forwarding, as you'll need to open specific ports for players to connect to your server. The default port for Deep Rock Galactic is UDP port 7777, but this can be configured.

Beginner's Guide

Setting up a private Deep Rock Galactic server might seem daunting at first, but by following these steps, you'll have your mining operation ready for your friends in no time. This guide assumes you have access to a dedicated machine or a virtual private server (VPS) that meets the aforementioned requirements.

Step 1: Prepare Your Server Environment If you're using a Linux distribution, ensure it's updated:

sudo apt update

sudo apt upgrade -y

For Windows Server, ensure all system updates are installed. You'll also need to install SteamCMD, which is a command-line version of Steam used to install and update game servers. On Linux, you might need to install some dependencies first:

sudo apt install lib32gcc-s1 steamcmd -y

On Windows, download SteamCMD from the official Valve Developer Community website and extract it to a dedicated folder, e.g., C:\steamcmd.

Step 2: Install Deep Rock Galactic Dedicated Server Files Open SteamCMD. On Linux, you can usually just type steamcmd in the terminal. On Windows, navigate to your steamcmd folder and run steamcmd.exe.

Once in the SteamCMD prompt, log in anonymously:

login anonymous

Set the installation directory for the Deep Rock Galactic server files. Choose a location with ample space, e.g., C:\DRGServer on Windows or /home/drgserver on Linux.

force_install_dir C:\DRGServer

(Replace C:\DRGServer with your desired path)

Now, download the Deep Rock Galactic dedicated server application. The App ID for Deep Rock Galactic is 548430.

app_update 548430 validate

This process will download all necessary server files. It might take some time depending on your internet speed. Once complete, type quit to exit SteamCMD.

Step 3: Configure Your Server Navigate to the installed server directory. Inside, you'll find a folder structure similar to the game client. The primary configuration file you'll be interested in is ServerSettings.ini. This file is usually located in DRGServer\FSD\Saved\Config\WindowsServer (on Windows) or DRGServer/FSD/Saved/Config/LinuxServer (on Linux). If it doesn't exist, you might need to run the server once to generate it, or create it manually.

Key settings to consider in ServerSettings.ini:

ServerName=MyAwesomeDRGServer (Choose a unique name for your server)

ServerPassword=YourSecurePassword (Optional, but highly recommended for private lobbies)

MaxPlayers=4 (Deep Rock Galactic is designed for 4 players, but you can technically increase this, though it's not officially supported and may lead to issues.)

bIsPublic=False (Set to False for a private server that won't appear in the public server browser. Players will connect via IP.)

Port=7777 (The default UDP port. Ensure this port is open on your firewall and router.)

Step 4: Configure Firewall and Port Forwarding This is a critical step for allowing players to connect to your server.

Server Firewall: You need to open UDP port 7777 (or whatever port you configured) on your server's operating system firewall.

Linux (UFW example): sudo ufw allow 7777/udp

Windows Server: Go to Windows Defender Firewall with Advanced Security, create a new inbound rule for UDP port 7777.

Router Port Forwarding: If your server is behind a router, you must configure port forwarding on your router. This tells your router to direct incoming traffic on UDP port 7777 to the internal IP address of your server machine. The exact steps vary by router model, so consult your router's manual or search online for "port forwarding [your router model]".

Step 5: Start Your Server To start the Deep Rock Galactic server, navigate to the DRGServer\FSD\Binaries\Win64 (Windows) or DRGServer/FSD/Binaries/Linux (Linux) directory. The executable is typically named FSDServer.exe (Windows) or FSDServer-Linux-Shipping (Linux).

You can run it directly, but it's often better to use a script or a process manager (like screen or tmux on Linux) to keep it running in the background. Example command (Windows):

start FSDServer.exe -log

Example command (Linux with screen):

screen -S drgserver ./FSDServer-Linux-Shipping -log

The -log argument is useful for seeing server output and troubleshooting.

Step 6: Connect to Your Server Your friends can connect to your private server by opening Deep Rock Galactic, going to the "Join Game" menu, and selecting "Direct Connect." They will need to enter your server's public IP address and the port (e.g., your.public.ip.address:7777). If you set a password, they will be prompted for it. You can find your public IP address by searching "what is my IP" on Google from your server machine.

Hosting Service Comparison and Recommendations

Choosing the right hosting service for your Deep Rock Galactic private server can significantly impact performance, reliability, and your overall experience. This section compares various types of hosting and recommends providers based on different needs and budgets.

Types of Hosting:

Shared Hosting: Generally not suitable for game servers. While inexpensive, shared hosting environments allocate minimal resources and often have strict usage policies that prohibit running game servers. Performance will be poor, and your server might be terminated.

Virtual Private Server (VPS): An excellent balance of cost, performance, and flexibility. A VPS gives you dedicated resources (CPU, RAM, storage) within a virtualized environment. You get root access, allowing full control over the operating system and server software. This is the most common and recommended option for private game servers.

Dedicated Server: Offers the highest performance and control, but at a higher cost. You get an entire physical server to yourself. This is overkill for a small Deep Rock Galactic private lobby but might be considered for very large communities, multiple game servers, or if you have specific hardware requirements.

Game Server Hosting Providers: These specialized providers offer pre-configured Deep Rock Galactic servers. They handle the setup, updates, and often provide a user-friendly control panel. Convenient for beginners but typically more expensive per resource unit than a self-managed VPS.

Key Factors for Comparison:

CPU Performance: Look for providers offering modern CPUs with good single-thread performance.

RAM: Ensure sufficient RAM (8GB+ recommended).

Storage: SSD storage is a must for game servers.

Network Latency & Bandwidth: Choose a data center geographically close to your players for lower ping. High, unmetered bandwidth is ideal.

Operating System Choice: Flexibility to install Linux or Windows Server.

Pricing: Compare monthly costs, setup fees, and any hidden charges.

Support: 24/7 technical support is invaluable, especially for self-managed VPS.

Recommended Hosting Providers (as of 2025-11-30):

For Self-Managed VPS (Best Value & Control):

OVHcloud: Known for competitive pricing and a wide range of VPS and dedicated server options globally. Their "VPS Game" series is specifically optimized for gaming workloads.

Hetzner: Offers powerful VPS (Cloud Servers) and dedicated servers in Europe and the US at very attractive price points. Excellent performance for the cost.

DigitalOcean: User-friendly interface, good documentation, and reliable "Droplets" (VPS). While slightly pricier than OVH or Hetzner, their ease of use is a big plus for those new to VPS management.

Vultr: Similar to DigitalOcean, offering high-performance cloud instances across many data centers. Good for global reach.

For Game Server Hosting (Ease of Use):

GPORTAL: A popular game server host that often supports Deep Rock Galactic. They provide a web-based control panel for easy management and automatic updates.

Nitrado: Another well-established game server provider with a global presence. Offers Deep Rock Galactic servers with a user-friendly interface and good support.

Survival Servers: Specializes in survival and co-op games, including Deep Rock Galactic. Offers instant setup and a custom control panel.

Recommendation Summary:

For most Deep Rock Galactic private lobbies, a VPS from providers like Hetzner or OVHcloud offering at least 2 vCPUs, 8GB RAM, and 120GB SSD storage provides the best balance of performance, cost, and control. If you prefer a hands-off approach and are willing to pay a bit more for convenience, a specialized game server host like GPORTAL or Nitrado is a solid choice. Always check the latest pricing and available configurations directly on the providers' websites.

Troubleshooting

Even with careful setup, you might encounter issues when running your Deep Rock Galactic private server. Here's a systematic approach to common problems and their solutions.

1. Players Cannot Connect to the Server:

"Server Not Responding" or "Connection Timed Out" errors:

Check Server Status: Ensure the FSDServer.exe (or Linux equivalent) process is actually running on your server machine. Check the server's console output for any error messages.

Firewall: Verify that UDP port 7777 (or your configured port) is open on your server's operating system firewall. Temporarily disabling the firewall (for testing purposes only, re-enable immediately after) can help isolate if this is the issue.

Port Forwarding: If your server is behind a router, confirm that port forwarding is correctly configured to direct UDP traffic on port 7777 to your server's internal IP address. Use an online port checker tool (e.g., canyouseeme.org) to verify if the port is open from the internet.

Public IP Address: Ensure players are using the correct public IP address of your server. If your server's public IP changes (dynamic IP), you might need to update players or consider a Dynamic DNS service.

Incorrect Port: Double-check that players are entering the correct port number (e.g., your.ip.address:7777).

Server Password: If you set a password, ensure players are entering it correctly.

"Failed to Join Game" or "Invalid Server" errors:

Game Version Mismatch: The most common cause. Ensure your server and all players are running the exact same version of Deep Rock Galactic. Game updates frequently break server compatibility. You'll need to update your server files via SteamCMD (app_update 548430 validate) after a game update.

Server Configuration: Review your ServerSettings.ini file for any typos or incorrect values. Ensure bIsPublic=False if you intend for it to be private.

Mod Conflicts: If you're using mods, ensure both the server and clients have compatible versions of the mods, or temporarily disable them for testing.

2. Server Lag or Poor Performance:

High Ping:

Geographic Distance: If players are far from the server's data center, high ping is inevitable. Consider a server location closer to the majority of your players.

Network Congestion: Check your server's internet connection for bandwidth saturation or packet loss. Run a speed test on the server.

Server Resources: High CPU or RAM usage on the server can lead to lag. Monitor these metrics using tools like htop (Linux) or Task Manager (Windows).

Low FPS (on server, if applicable) or Stuttering:

Insufficient CPU/RAM: Your server might be under-resourced. Upgrade your VPS plan or consider a dedicated server.

Disk I/O: If your server is using an HDD instead of an SSD, or if the SSD is heavily utilized by other processes, it can cause performance bottlenecks.

Background Processes: Ensure no other resource-intensive applications are running on your server.

Game Updates: Sometimes, game updates can introduce performance regressions. Check official Deep Rock Galactic forums or communities for similar reports.

3. Server Crashing or Unexpected Shutdowns:

Out of Memory (OOM) Errors: Check server logs for "out of memory" messages. This indicates your server doesn't have enough RAM. Increase RAM or optimize server usage.

Corrupted Game Files: Run app_update 548430 validate again in SteamCMD to verify and repair any corrupted server files.

Operating System Issues: Ensure your server OS is stable and up-to-date. Check system logs for any critical errors.

Hardware Failure (Dedicated Servers): If you're on a dedicated server, hardware issues (e.g., failing RAM, overheating CPU) can cause crashes. Monitor hardware health.

Mod Instability: If using mods, try running the server without them to see if they are causing the crashes.

4. Server Not Appearing in Public List (if bIsPublic=True):

Firewall/Port Forwarding: Even for public servers, UDP port 7777 must be open.

Steam Master Server Issues: Occasionally, there can be delays or issues with the Steam master server listing. Give it some time.

Server Name/Tags: Ensure your ServerName is unique and doesn't contain any disallowed characters.

General Troubleshooting Tips:

Check Server Logs: The server logs are your best friend. They are usually located in DRGServer\FSD\Saved\Logs. Look for error messages, warnings, or anything unusual.

Restart the Server: A simple restart can often resolve temporary glitches.

Consult Community Forums: The Deep Rock Galactic community (e.g., official Discord, Reddit r/DeepRockGalactic) is a great resource for specific issues. Search for similar problems or ask for help.

Isolate the Problem: Change one variable at a time (e.g., disable firewall, remove mods, change port) to pinpoint the root cause.

Performance Optimization Tips

Optimizing your Deep Rock Galactic private server ensures a smooth, lag-free experience for all players. While the game isn't extremely resource-intensive, these tips can help maximize performance and stability.

1. Server Hardware and Configuration:

Prioritize SSD Storage: As mentioned, always use an SSD for your server's operating system and game files. This drastically reduces load times and improves overall responsiveness.

Sufficient RAM: Ensure your server has at least 8GB of RAM, preferably 16GB, especially if you plan to run other services or use mods. This prevents the server from relying on slower swap space.

CPU Clock Speed: For game servers, higher single-core clock speed often benefits performance more than a large number of cores. Choose a CPU with good per-core performance.

Dedicated Resources: If using a VPS, ensure your provider guarantees dedicated CPU cores and RAM, rather than oversubscribed resources that can lead to performance fluctuations.

2. Network Optimization:

Low Latency Connection: Host your server in a data center geographically close to the majority of your players. This minimizes ping and improves responsiveness.

Wired Connection: Always use a wired Ethernet connection for your server machine. Avoid Wi-Fi for server hosting.

Sufficient Bandwidth: Ensure your server has at least 100 Mbps symmetrical bandwidth to handle player traffic without congestion.

QoS (Quality of Service): If you have control over your network equipment (e.g., router), you can configure QoS to prioritize game server traffic, ensuring it gets preferential treatment over other network activities.

3. Operating System Optimization:

Minimal OS Installation: Install a minimal version of your chosen operating system (e.g., Ubuntu Server without a GUI). This reduces resource consumption by eliminating unnecessary services and processes.

Keep OS Updated: Regularly update your operating system to benefit from performance improvements and security patches.

Disable Unnecessary Services: Review and disable any services or applications running on your server that are not essential for the Deep Rock Galactic server.

Linux Specifics:

screen or tmux: Use these tools to run your server in the background, allowing you to disconnect from the SSH session without stopping the server.

ulimit: Increase the open file limit for the user running the server if you encounter "too many open files" errors, though this is less common for DRG.

Kernel Tuning: For advanced users, minor kernel tuning (e.g., TCP buffer sizes) can sometimes offer marginal improvements, but this is usually not necessary for DRG.

4. Deep Rock Galactic Server Configuration:

ServerSettings.ini Tweaks:

MaxPlayers: While you can technically increase this, Deep Rock Galactic is optimized for 4 players. Running with more than 4 players can introduce instability and performance issues, as the game's netcode is designed for smaller groups. Keep it at 4 for optimal performance.

TickRate (if available): Some game servers allow adjusting the tick rate (how many times per second the server updates game state). A higher tick rate generally means smoother gameplay but consumes more CPU. Deep Rock Galactic's server application might not expose this directly, but if it does, experiment cautiously.

Mod Management:

Be Selective: Only install mods that are well-optimized and from trusted sources. Poorly coded mods can significantly impact server performance.

Test Thoroughly: Always test new mods on a separate instance or during off-peak hours to assess their performance impact before deploying them to your main server.

Keep Mods Updated: Ensure all server-side mods are updated to their latest versions, as developers often release performance improvements.

5. Monitoring and Maintenance:

Resource Monitoring: Regularly monitor your server's CPU, RAM, and network usage. Tools like htop (Linux), top (Linux), or Task Manager (Windows) are invaluable. Set up alerts if resources exceed certain thresholds.

Log Analysis: Periodically review server logs for errors, warnings, or performance bottlenecks.

Regular Restarts: While not a solution for underlying issues, a daily or weekly automated server restart can help clear memory leaks and ensure a fresh state.

Backup: Implement a regular backup strategy for your server files and configuration.

By implementing these optimization tips, you can ensure your Deep Rock Galactic private server provides a stable, low-latency, and enjoyable experience for you and your fellow miners.

Technical Q&A

This section addresses common technical questions related to setting up and managing a Deep Rock Galactic private server.

Q1: Can I run a Deep Rock Galactic server on my home PC? A1: Yes, you can, but it's generally not recommended for long-term or reliable hosting. While technically feasible, home internet connections often have limited upload bandwidth and dynamic IP addresses, which can make it difficult for players to connect consistently. Furthermore, running a server on your gaming PC can consume resources, potentially impacting your own game performance. A dedicated machine or a VPS is a more robust solution.

Q2: What is the difference between a "private" and "public" Deep Rock Galactic server? A2: A private server is typically configured with bIsPublic=False in ServerSettings.ini and often has a password. It won't appear in the in-game server browser, and players must connect directly using the server's IP address and port. A public server (with bIsPublic=True) will appear in the in-game server browser, allowing anyone to join, though you can still set a password. For private lobbies with friends, setting bIsPublic=False is recommended for better control and privacy.

Q3: How do I update my Deep Rock Galactic dedicated server? A3: To update your server, you'll use SteamCMD.

Stop your running Deep Rock Galactic server process.

Open SteamCMD.

Log in anonymously: login anonymous

Set the installation directory (if you haven't already): force_install_dir C:\DRGServer (or your server path)

Run the update command: app_update 548430 validate

Once the update is complete, type quit and restart your server. It's crucial to update your server whenever the game client receives an update to avoid version mismatch issues.

Q4: Can I run multiple Deep Rock Galactic servers on a single machine? A4: Yes, it's technically possible, but requires careful resource management and configuration. Each server instance will require its own set of game files, its own unique port number (e.g., 7777, 7778, 7779), and its own ServerSettings.ini file. You'll need to ensure your server machine has sufficient CPU, RAM, and bandwidth to handle all instances concurrently without performance degradation. Each instance will consume resources as if it were a separate server.

Q5: How do I backup my Deep Rock Galactic server data? A5: The most important data to back up are your ServerSettings.ini file and any save game data. Save game data for Deep Rock Galactic dedicated servers is typically located in DRGServer\FSD\Saved\SaveGames (Windows) or DRGServer/FSD/Saved/SaveGames (Linux). You can simply copy these directories to a safe location. For a full server backup, you might want to back up the entire DRGServer directory. Automated backup solutions (e.g., rsync for Linux, backup software for Windows) are highly recommended.

Q6: What if my server's public IP address changes? A6: If your server has a dynamic public IP address (common with home internet connections), it will change periodically. This means players will need to be updated with the new IP. To avoid this, you can use a Dynamic DNS (DDNS) service. A DDNS service maps a static hostname (e.g., my-drg-server.ddns.net) to your dynamic IP address. Your server or router periodically updates the DDNS service with your current IP, so players can always connect using the hostname. For VPS or dedicated servers, you typically get a static IP address, so this isn't an issue.

Q7: Can I use mods on my Deep Rock Galactic dedicated server? A7: Yes, Deep Rock Galactic supports modding, and many mods can be used on dedicated servers. The process for installing mods varies depending on the modding framework (e.g., Mod.io integration). Generally, server-side mods need to be installed on the server, and client-side mods on the players' machines. Always ensure compatibility between server and client mod versions. Be aware that some mods might impact server performance or stability. Consult the mod's documentation for server installation instructions.

Q8: My server console is showing errors about "SteamAuth" or "Steamworks." What does this mean? A8: These errors often indicate issues with the server's ability to communicate with Steam's authentication services.

Firewall: Ensure outbound connections from your server to Steam's servers are not blocked by your firewall.

Internet Connectivity: Verify your server has a stable internet connection.

SteamCMD Login: Ensure you logged in anonymously when updating the server via SteamCMD.

Game Version: A version mismatch between your server and the current game client can sometimes manifest with authentication errors. Update your server.

Steam Server Issues: Occasionally, Steam's authentication servers might experience temporary outages. Check Steam Status for any reported issues.

Q9: How do I make my server automatically restart after a crash or update? A9:

Linux: You can use systemd services or cron jobs combined with a script that checks if the server process is running and restarts it if not. Tools like supervisord are also excellent for process management.

Windows: You can create a batch script that starts the server in a loop, or use Windows Task Scheduler to run a script that checks and restarts the server. For more robust solutions, consider third-party process monitoring tools. Implementing automatic restarts significantly improves server uptime and reduces manual intervention.

Return to index - Sitemap for users