You decide which services we may enable for analytics, personalization, and external content.
We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.
Necessary cookies
These entries support essential functions such as security, stability, and form processing.
Optional sections
Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
You can reopen and change your selection at any time. · 1.0.2
The most common issues with your Skyrim Together server on a VPS and how to fix them quickly, from version errors to lag → Learn more
Running your own Skyrim Together server on a VPS is a lot of fun, but it also means taking responsibility when something goes wrong. Crashes, lag, and configuration issues are typical challenges that every server owner encounters eventually.
To help you spend less time troubleshooting, we’ll cover the most common issues and how to fix them quickly on your VPS.
FAQ
C:\ZapX-GameServers\skyrim-together-reborn\logs\server.log. Restarts after crashes are recorded in logs\supervisor.log.Skyrim Together Reborn (skyrim-together-reborn) - Start.Skyrim Together Reborn (skyrim-together-reborn) - Backup shortcut on your VPS. Your entire VPS is also backed up daily. With an active ZapX Pass, you can restore these backups yourself.Feedback
Was this article helpful?
Your feedback helps us prioritize and improve content.
0 of 0 Users found this article helpful.
Personal support
Need more help than the guide provides?
Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.
Zappy knows this guide and answers you right in the chat.
Navigation
The causes of server issues aren’t always immediately obvious. The best place to start is the server output: if you set up Skyrim Together Reborn using the Game Server Installer, you’ll find it at C:\ZapX-GameServers\skyrim-together-reborn\logs\server.log. The installer logs restarts after crashes in logs\supervisor.log.
Your server isn’t publicly listed by default. Players connect directly using its IP address and port. If they can’t connect, first check server.log to see if the server is running. Then check that the ports are open in the Windows Firewall and your VPS’s network firewall. See Skyrim Together Reborn: Set up a server on your VPS for the ports required by Skyrim Together Reborn. Also make sure all players are using the same mod version as the server (1.8.3).
Start the server via Remote Desktop using the shortcut Skyrim Together Reborn (skyrim-together-reborn) - Start and monitor server.log. Common causes include a typo in server\config\STServer.ini, a port that’s already in use by another program, or an error in a script resource in the server\resources\ folder. If you’ve made any changes, try reverting them to see if that resolves the issue.
Nothing ends a great session faster than an unexpected crash. Possible causes include an outdated server version, incompatible mods on players’ PCs, an overloaded VPS, or a misconfiguration. The installer automatically restarts your server after a crash. If it crashes several times in quick succession, the installer gives up. You’ll then need to fix the cause and restart the server yourself.
The server and players must use the same version of Skyrim Together Reborn. The installer is set to mod version 1.8.3. Updates aren’t installed automatically. Open the Game Server Installer again and select Skyrim Together Reborn. It will then show Update. Alternatively, use the shortcut Skyrim Together Reborn (skyrim-together-reborn) - Update on your VPS.
Many issues originate on players’ PCs, for example, other mods that aren’t compatible with Skyrim Together Reborn or different mod lists. Test the game with as few mods as possible, then add more mods one at a time. To require everyone to use the same mods, create a loadorder.txt file in the server\Data\ folder to enable the server’s mod check.
Issues like lag and delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or additional content overloads the system.
The mod’s developers don’t recommend having more than 8 players. Check the player slots (uMaxPlayerCount in server\config\STServer.ini) and set them using the installer. Stop the server before editing the file.
Skyrim Together Reborn requires at least 2 GB of RAM. The server uses very little when idle, but its resource requirements increase with more players. The operating system and other programs on the VPS also need resources. You can see how heavily your VPS is being used in the ZapX dashboard under Monitoring. If RAM or CPU usage is consistently maxed out, upgrading your VPS may help. Learn more in Upgrade, downgrade, renewal, and cancellation.
Ping spikes and lag are usually caused by limited VPS resources, a large number of players, or a server location far from your players. First, check resource usage under Monitoring. If you suspect routing issues, see Diagnose network issues with WinMTR/MTR. If you still need help, contact our support team.
Game servers are occasionally targeted by DDoS attacks, which flood the server with traffic. Your VPS is protected by our DDoS protection. You can view past attacks in the DDoS Manager for your VPS in the ZapX dashboard, if it’s available at your location. If you suspect an attack is causing issues, contact our support team.
Regular backups can save you a lot of stress. Use the shortcut Skyrim Together Reborn (skyrim-together-reborn) - Backup to back up STServer.ini, the mod list in the Data folder, and the script resources as a ZIP file at any time. Use Skyrim Together Reborn (skyrim-together-reborn) - Restore to restore them. Your entire VPS is also backed up automatically every day. With an active ZapX Pass, you can restore these backups yourself and create your own. Learn more in Daily backups, restoration, and restricted actions.
These steps should help you resolve the issue. If they don’t, feel free to contact our support team: simply start a support chat in your ZapX customer account. We’re here every day and happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
