Barotrauma Troubleshooting Guide
This guide covers common issues you may encounter when running a Barotrauma dedicated server on Legion Hosting, along with step-by-step solutions. For initial server setup, see the Barotrauma Dedicated Server Setup Guide.
Before troubleshooting: Check your server console in GPanel for error messages. Lines containing
[ERROR] or Exception will point you to the cause in most cases.
Table of Contents
- Submarine Not Loading / Server Stuck on Startup
- Mod Conflicts and Crashes
- Server Not Appearing in Browser
- Connection Timeout / Cannot Direct Connect
- Campaign Save Not Found After Restart
- Server Lag and Performance Issues
Submarine Not Loading / Server Stuck on Startup
Symptom: The server starts but players cannot join, or the server log shows an error about the submarine not being found.
Solutions
- Check the name exactly: The
Submarineattribute inserversettings.xmlmust match the filename (without the.subextension) exactly, including capitalisation. For example,Humpbackis correct buthumpbackis not. - Verify the file exists: Connect to your server via SFTP or the GPanel file manager and confirm the
.subfile is present in theSubmarines/directory. - Workshop submarine? If the submarine came from a Workshop mod, it must be installed in
LocalMods/and registered in the server settings before it can be used. See the Mod Installation Guide. - Test with a default submarine: Switch to a built-in submarine (e.g.
Humpback) to confirm the server starts correctly. If it does, the issue is with the custom submarine file.
Mod Conflicts and Crashes
Symptom: Server crashes on startup, disconnects players on join, or the console shows errors referencing specific content IDs.
Solutions
- Isolate the problem mod: Disable all recently added mods and restart the server. If it runs stable, re-enable mods one at a time, restarting each time, to find the conflict.
- Version mismatch: Ensure all mod files on the server match the versions installed on client machines. Re-download and re-upload mods if uncertain. See the Mod Installation Guide for the update process.
- Client-only mods: Some Workshop mods are client-side only and should not be installed on the server. Check the mod's Workshop description page for this information.
- Check the server log: Open the console in GPanel and look for
[ERROR]orExceptionlines. These usually reference the specific mod or content file causing the crash.
Tip: If you are running many mods and cannot identify the conflict, try a binary search approach: disable half the mods at a time rather than one by one. This narrows down the problem much faster.
Server Not Appearing in Browser
Symptom: Your server is running but does not appear in the in-game server browser.
Solutions
- Wait a few minutes: The Steam server browser can take several minutes to list a newly started server. Try a direct connect first to confirm the server is reachable.
- Verify the server is fully started: Open GPanel and confirm the server shows as running with no errors in the console.
- Check your query port: The
QueryPortvalue inserversettings.xmlmust match the query port assigned to your service. Check the Network tab in GPanel for the correct port assignment. - Confirm with direct connect: Try connecting directly using your server IP and main port (check GPanel Network tab for your assigned port) to rule out a browser-specific issue.
Connection Timeout / Cannot Direct Connect
Symptom: Attempting to join via direct connect results in a timeout or "connection failed" error.
Solutions
- Verify your IP and port: Check the Network tab in GPanel for your server's IP address and port. See How to Find Your Server IP and Port.
- Use the correct port: Connect to the main game port, not the query port. The main port is the one listed as the primary port in GPanel.
- Confirm the server is running: Check GPanel to ensure the server has not crashed or stopped.
- Check your serversettings.xml: Ensure the
Portvalue inserversettings.xmlmatches the port assigned in GPanel. If they differ, the server will bind to the wrong port. - Firewall on your end: On rare occasions, your local network or ISP may block outbound UDP traffic on non-standard ports. Try connecting from a different network or using a VPN to test.
Campaign Save Not Found After Restart
Symptom: After restarting the server, the campaign is gone and players must start a new one.
Solutions
- Verify the save files exist: Connect via SFTP and check that the campaign folder still exists in
Saves/Multiplayer/. - Check for migration issues: If you recently migrated your server or restored from a backup, ensure the save folder was uploaded to the correct path inside the Barotrauma server directory.
- Unclean shutdown: If the server was force-killed (rather than stopped cleanly via GPanel), the final save state may not have been written. Always use the Stop button in GPanel rather than force-killing the process.
- Restore from backup: If you previously backed up the campaign, stop the server, upload the backup folder to
Saves/Multiplayer/via SFTP, and start the server. See the main setup guide for detailed backup/restore instructions.
Server Lag and Performance Issues
Symptom: Players experience rubber-banding, delayed inputs, or the server becomes unresponsive during gameplay.
Solutions
- Reduce player count: Lower the
MaxPlayersvalue inserversettings.xmlif your server plan does not have enough resources for the current player count. - Reduce mod count: Some mods, especially those adding many new creatures or complex systems, significantly increase server resource usage. Remove non-essential mods.
- Check server resources: In GPanel, monitor CPU and memory usage. If you are consistently near the limit, consider upgrading your server plan.
- Restart the server: Long-running sessions can accumulate memory usage. A scheduled restart between play sessions can help maintain performance.
Related Articles
- Barotrauma Dedicated Server Setup Guide
- Barotrauma Mod Installation Guide
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
Still having trouble? Open a support ticket at legionhosting.net/submitticket.php and include your server name, the error messages from the GPanel console, and the steps you have already tried.