Skyrim Together Dedicated Server Setup Guide 2026

A great Skyrim co-op session should not crash before your friends even join. With a Skyrim Together dedicated server, your group gets one stable place to connect, play, and manage the session.

To host a Skyrim Together Reborn server, run SkyrimTogetherServer.exe on Windows or use the official tiltedphoques/st-reborn-server Docker image on Linux. Open port 10578, install Address Library, keep every player on the same supported Skyrim version, and connect only after escaping Helgen. Use a password and direct IP for private sessions.

This guide covers PlayTogether, local hosting, Hamachi, ZeroTier, VPS hosting, and dedicated servers. You will learn how to configure STServer.ini, open the right ports, fix connection issues, manage mods with loadorder.txt, and back up your server safely.

Skyrim Together Server Facts Before You Host

Before you set up a Skyrim Together dedicated server, get the basics right. Most setup problems come from outdated guides, wrong server files, blocked ports, wrong config paths, or mismatched game versions.

Skyrim Together Reborn works best when every player uses the same supported game version, same mod version, and same load order.

Each player should also install Address Library for SKSE Plugins before playing. Missing dependencies can break the client before the server becomes the real issue.

Do not connect to a Skyrim Together server during the Helgen intro sequence. Connect only after escaping Helgen. The intro uses heavy scripted events, and joining too early can cause bugs.

The server also needs a clean network path. Open port 10578 for both TCP and UDP. The official Tilted Phoques port-forwarding guide says to choose Both when the router allows it. If the router forces a choice, create one TCP rule and one UDP rule for port 10578.

If you want the least technical route, start with PlayTogether. If your group plays from the same house or LAN, use a local server instead. For more control, use a VPS, managed host, or dedicated server.

Skyrim Together Reborn vs Old Skyrim Together: Which One Should You Use?

Use Skyrim Together Reborn for a modern Skyrim co-op server.

Do not mix Reborn instructions with old Skyrim Together, Harbor, or Nightlies guides. Older tutorials may point you to outdated launchers, old Docker images, wrong folders, or server steps that no longer match the current Reborn setup.

Skyrim Together Reborn uses current files and terms such as:

• SkyrimTogetherServer.exe
• STServer.ini
• Docker image: tiltedphoques/st-reborn-server:latest
• Port 10578
• TCP + UDP firewall/router rules for Windows hosting

For the safest setup, follow Reborn-specific instructions only. Use the Reborn server executable on Windows, the current Docker image on Linux, and the correct STServer.ini path for your mod manager.

Skyrim Together Server Requirements: What You Need Before Setup

You need a supported PC copy of Skyrim Special Edition, Skyrim Together Reborn, Address Library for SKSE Plugins, a save past Helgen, and a host machine with stable CPU, RAM, and network access.

A Skyrim Together dedicated server can run correctly and still reject players. Most early failures come from the player side, not the server.

The common causes are simple:

• Wrong Skyrim version
• Missing Address Library
• Different Skyrim Together Reborn version
• Different mod load order
• Save stuck in the Helgen intro
• Blocked port 10578
• CGNAT or double NAT

Match the player setup first. Then test the server.

1. Use The Right Skyrim Version

Every player needs a supported PC copy of Skyrim Special Edition. The official FAQ specifically lists Steam version 1.6.117X, while the supported-games page also lists GOG’s latest version.

The paid Anniversary Upgrade DLC is not required. The Anniversary Upgrade adds Creation Club content, which the official FAQ treats as non-recommended for the most stable Skyrim Together Reborn experience.

Do not use Oldrim, Legendary Edition, VR, console versions, Xbox Game Pass, Epic Games, or cracked copies. These versions do not fit a stable Skyrim Together Reborn setup.

2. Install Skyrim Together Reborn And Address Library

Each player should install Skyrim Together Reborn and Address Library for SKSE Plugins.

The name causes confusion, but SKSE itself is not required for Skyrim Together Reborn. Install SKSE only when another mod in your list needs it.

3. Use The Same Mod Manager And Load Order

Players can use Vortex or Mod Organizer 2, but every player should stay on the same Skyrim Together Reborn version.

For modded servers, every player needs the same mod list and the same load order. One mismatch can cause crashes, missing NPCs, broken quests, desync, or failed connections.

4. Complete Helgen Before Connecting

Do not connect during the Helgen intro. Connect only after escaping Helgen, then join from a normal playable save.

The Helgen intro uses scripted events that can break when players connect too early.

5. Check Each Player Before Blaming The Server

Before joining, every player should confirm:

• Supported PC copy of Skyrim Special Edition
• Skyrim Together Reborn installed
• Address Library for SKSE Plugins installed
• SKSE is optional unless another mod needs it
• Paid Anniversary Upgrade/Creation Club content disabled for the most stable setup, especially on public servers
• Same Skyrim Together Reborn version as the group
• Same mod list and load order for modded servers
• Save file after escaping Helgen
• Stable internet connection
• Correct server IP, port, and password

When one player cannot join but others can, check that player’s setup first. The server may not be the problem.

6. Match Server Resources To Group Size

A Skyrim Together Reborn server does not need extreme hardware for a small friend group. It needs steady CPU performance, enough RAM, and a clean network path.

Treat Skyrim Together Reborn as a co-op server, not an MMO server. Start with 2–4 players, test the server, then raise the player count slowly.

For small groups, prioritize stable CPU performance, low latency, and enough RAM over oversized specs.

7. Prepare The Network Before Inviting Friends

Network quality matters as much as hardware. The server needs a stable internet connection, a reachable address, and open firewall rules for port 10578.

For home hosting, open TCP and UDP on port 10578 in both the firewall and router. Use a static LAN IP or DHCP reservation so the router rule keeps pointing to the correct machine.

Home hosting can fail even when the server runs fine. Common causes include:

• CGNAT
• Double NAT
• Weak upload speed
• Router firewall rules
• Windows Firewall
• Wrong public IP
• Router rule pointing to the wrong device

8. Use Hosted Infrastructure When Home Hosting Becomes A Limit

Use a VPS for small always-online groups, or use a dedicated/bare-metal server when your group needs:

• Always-online access
• Stable public IP
• No home router or CGNAT issues
• Docker or Pterodactyl control
• Multiple game servers
• More bandwidth control
• Safer backups and updates

For most groups, 2–8 players is the safest range. Test your mods, network, and server settings before you push beyond that.

How To Install Skyrim Together Reborn Before Hosting

Use this section as a client setup check before you invite players.

1. Install Skyrim Together Reborn With Vortex

Use Vortex if you want the simplest mod manager path.

First, install a supported PC copy of Skyrim Special Edition. The official FAQ specifically lists Steam version 1.6.117X, while the supported-games page also lists GOG’s latest version.

Launch Skyrim Special Edition once before you install Skyrim Together Reborn. The official Tilted Phoques setup guide says this first launch is required before setup.

Next, install the required files:

• Skyrim Together Reborn
• Address Library for SKSE Plugins
• Address Library All in one 1.6.X, not the older 1.5.X file

Address Library is required, but SKSE itself is not required for Skyrim Together Reborn. Install SKSE only if another mod in your list needs it.

After that, enable Skyrim Together Reborn in Vortex. Use the custom Skyrim Together launcher created through Vortex when you want to play.

The official Tilted Phoques Vortex guide says players must use the custom launcher every time they play Skyrim Together Reborn.

When the game opens, confirm that the Skyrim Together UI works. You should be able to open the connection menu before you test any server.

Do not connect yet if your character is still in Helgen. Connect only after escaping Helgen.

2. Install Skyrim Together Reborn With Mod Organizer 2

Use Mod Organizer 2 if your group wants tighter profile control, cleaner mod lists, or shared load order testing.

• Start by installing Skyrim Together Reborn and Address Library inside MO2. Keep every player on the same Skyrim Together Reborn version.
• Add Skyrim Together Reborn to the MO2 launch options. Then run it from inside MO2.
• On the first launch, Skyrim Together asks you to choose the game executable. Select: SkyrimSE.exe
• Do not select the Skyrim Together launcher as the target executable. The official Tilted Phoques MO2 guide says this step matters because the launcher needs to point to SkyrimSE.exe from the Skyrim root folder.
• If MO2 shows an Address Library warning, verify that the 1.6.X Address Library file is installed and follow the official Address Library troubleshooting steps before assuming it is harmless.
• For modded groups, keep profiles consistent across every player. Use the same mod list, same load order, and same Skyrim Together Reborn version.
• MO2 users can also run into Address Library path issues. The official troubleshooting guide tells MO2 users to copy the SKSE folder from the Address Library mod into the Skyrim Special Edition Data folder if Address Library fails to load.

3. Keep The Group On One Mod Setup

Skyrim Together Reborn works best with a clean, shared setup.

For the first test, use only:

• Skyrim Special Edition on a supported PC storefront
• Skyrim Together Reborn
• Address Library for SKSE Plugins

After the server works, add mods slowly.

A safe testing order looks like this:

1. Test clean Skyrim Together Reborn.
2. Add visual mods first.
3. Add gameplay mods in small batches.
4. Test after each batch.
5. Lock the shared load order once stable.

Do not assume every mod will work. The official FAQ says other mods are not explicitly synced. Some mods may work by chance, but the team recommends using no extra mods for the most stable setup.

4. Check The Client Before Testing The Server

Before you host or join a server, every player should confirm:

• A supported PC copy of Skyrim Special Edition is installed.
• Skyrim Together Reborn is installed.
• Address Library All in one 1.6.X is installed.
• SKSE is not installed unless another mod needs it.
• The game launches through Vortex or MO2.
• The Skyrim Together UI opens.
• The character has escaped Helgen. If using an alternate-start mod, test it separately because extra mods are not guaranteed to sync.
• The group uses the same Reborn version.
• The group uses the same load order if mods are enabled.

This saves time. If a player fails this checklist, fix the client before changing server ports, firewall rules, or STServer.ini.

How to Set Up a Skyrim Together Dedicated Server on Windows

On Windows, start the server with SkyrimTogetherServer.exe, test it with 127.0.0.1, close the server, edit STServer.ini, then open TCP and UDP on port 10578 if friends need to join from outside your local network. The official guide uses SkyrimTogetherServer.exe for Windows server hosting and 127.0.0.1 for same-PC testing.

1. Find SkyrimTogetherServer.exe

SkyrimTogetherServer.exe is the Windows server file.

Do not confuse it with SkyrimTogether.exe.

• SkyrimTogetherServer.exe starts the server.
• SkyrimTogether.exe launches the client.
• Running the client does not start a dedicated server.

The server file location depends on your mod manager.

For Vortex, open:

C:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\SkyrimTogetherReborn

For Mod Organizer 2, open the Skyrim Together Reborn mod folder from MO2, then enter the inner Skyrim Together Reborn folder. The official Windows setup guide gives separate paths for Vortex and MO2 because the file location changes by install method.

2. Launch The Server Once

Run:

SkyrimTogetherServer.exe

Windows may show a firewall prompt. Allow access for private and public networks.

After the server window opens, test it before inviting friends.

Launch Skyrim Together Reborn on the same PC and connect to:

127.0.0.1

Use no password for the first local test unless STServer.ini already has sPassword set.

This test confirms that the server process works on your own machine. It does not prove that remote friends can join yet. Remote access still needs firewall rules, router forwarding, and a reachable public IP.

3. Stop The Server Before Editing Settings

Close SkyrimTogetherServer.exe before editing STServer.ini.

Do not edit the config while the server runs. The official configuration guide says STServer.ini changes need a server shutdown. If you edit the file while the server is running, changes may not apply and may be overwritten when the server closes.

Find STServer.ini based on your setup.

For Vortex, open:

C:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\SkyrimTogetherReborn\config\STServer.ini

For MO2, right-click the Skyrim Together Reborn mod in MO2, choose Open in Explorer, open the Skyrim Together Reborn folder, then open the config folder. The official guide lists both methods.

4. Configure Basic Server Access

Open STServer.ini in a text editor.

Start with the access settings first:

Use a password for private friend groups.

If you set a password, players should connect by direct IP instead of relying on the public server list. The official server configuration page says passworded servers do not show on the server list.

Keep the default port unless you have a clear reason to change it:

10578

A custom port adds more work because you must update the server config, Windows Firewall rule, router rule, and player connection address.

5. Open Windows Firewall And Router Port

For remote friends, open port 10578 for both TCP and UDP.

Use two rules if your router does not offer a “Both” option:

• TCP 10578
• UDP 10578

The official port forwarding guide says to select Both when available. If the router forces one protocol at a time, create one TCP rule and one UDP rule for port 10578.

Point the router rule to the server PC’s local IPv4 address.

Use a static LAN IP or DHCP reservation. If your server PC gets a new local IP, the router rule may point to the wrong device.

Remote players should connect with:

public-ip:10578

If friends still cannot connect after port forwarding, check CGNAT, double NAT, Windows Firewall, and the router’s internal IP target before changing server files.

How To Set Up a Skyrim Together Reborn Local Server

Use 127.0.0.1 for same-PC testing, the host PC’s local IPv4 for LAN play, the public IPv4 for internet play, and a Hamachi or ZeroTier IP when port forwarding fails. A local server can work on your PC and still fail for remote friends.

A Skyrim Together Reborn local server means you run SkyrimTogetherServer.exe on your own machine or home network.

Local success only proves that the server can run. It does not prove that your router, ISP, or firewall allows outside players.

1. Use 127.0.0.1 For Same-PC Testing

Use this when the client and server run on the same PC:

127.0.0.1

This checks the local server process.

It does not test router forwarding.

2. Use The Local IPv4 For LAN Players

Players on the same home network should use the host PC’s local IPv4 address.

A local IPv4 often looks like:

192.168.1.25:10578

This works only inside the same network.

Do not give this local IP to remote friends. It will not work over the internet.

3. Use Public IP For Remote Friends

Remote players need your public IPv4 address and port.

Use this format:

public-ip:10578

The official connection guide tells players to enter the server address in the Skyrim Together Reborn UI. For local hosting, it uses 127.0.0.1; for remote hosting, it uses the host’s public IPv4.

4. Use Hamachi Or ZeroTier When Port Forwarding Fails

A VPN mesh gives players a private network path.

Use this when:

• Your router setup is hard.
• Your ISP uses CGNAT.
• Port forwarding does not work.
• You only host for a small friend group.

The official server overview lists ZeroTier as the Windows path for hosting without port forwarding. It also explains that ZeroTier works like Hamachi or Radmin by connecting players without router forwarding.

5. Use A VPS Or Dedicated Server For Always-Online Hosting

Use hosted infrastructure when you want:

• Public IP access
• No home router issues
• No CGNAT problems
• Better uptime
• Docker control
• Pterodactyl control
• Multiple game servers

A home server works for testing. A VPS or dedicated server fits long-running groups better.

How To Set Up a Skyrim Together Server on Linux With Docker

Linux users should use Docker with the current Skyrim Together Reborn server image. Create persistent folders for config, Data, and logs, then run the container with UDP port 10578 exposed.

1. Install Docker

Update the server first:

• sudo apt update
• Install Docker and the Docker Compose plugin based on your Linux distribution.
• On Ubuntu-based systems, you can use Docker’s official install method or your server provider’s supported Docker package source.
• After Docker is installed, add your user to the Docker group if needed:
  • sudo usermod -aG docker $USER
• Log out and log back in before running Docker without sudo.

2. Create Persistent Server Folders

Create folders for the server files:

• sudo mkdir -p /opt/docker/skyrimserver/{config,Data,logs}

Give your user ownership:

• sudo chown -R ${USER}:${USER} /opt/docker/skyrimserver

These folders keep your server files outside the container.

Do not skip volume mounts. If you recreate the container without persistent folders, you can lose settings and server data.

3. Run The Official Docker Container

Run the current Skyrim Together Reborn server image:

docker run -d -it --name skyrimserver \

-p 10578:10578/udp \

-v /opt/docker/skyrimserver/config:/st-server/config \

-v /opt/docker/skyrimserver/Data:/st-server/Data \

-v /opt/docker/skyrimserver/logs:/st-server/logs \

tiltedphoques/st-reborn-server:latest

This command does four key things:

• Creates a container named skyrimserver
• Opens UDP port 10578
• Mounts the config, Data, and logs folders
• Uses the current Reborn Docker image

The official Docker setup maps UDP only on port 10578. Follow that for the main command unless you have a specific, tested reason to expose TCP too.

4. View Server Logs

Check live logs with:

• docker logs -tf skyrimserver

Use logs when the server fails to start, players cannot connect, or config changes do not behave as expected.

5. Attach To The Server Console

Attach to the running server:

• docker attach skyrimserver

Use the console for supported live commands.

To leave the attached console without stopping the container, press:

• CTRL + P, then CTRL + Q

Run this inside the console to view supported commands:

• /help

Do not invent server commands. Use only commands shown by the server.

6. Stop, Start, And Restart The Container

Stop the server:

• docker stop skyrimserver -t 1

Start the server:

• docker start skyrimserver

Restart the server:

• docker restart skyrimserver -t 1

Stop the server before editing STServer.ini. If you edit the config while the server runs, your changes may not apply or may be overwritten when the server stops.

7. Keep Docker Networking Separate From Router Forwarding

Use this rule in the article:

• Windows/router forwarding: TCP + UDP on port 10578
• Official Docker command: UDP only with -p 10578:10578/udp

Docker Compose Setup for a Skyrim Together Server

Docker Compose is optional. Use it when you want cleaner long-term management on a Linux server, VPS, or dedicated server.

The official Docker command uses UDP port 10578, persistent folders, and the image tiltedphoques/st-reborn-server:latest. This Compose file adapts the official Docker setup into a long-term management format.

1. Create A compose.yaml File

Create a server folder:

mkdir -p /opt/docker/skyrimserver/{config,Data,logs}

cd /opt/docker/skyrimserver

Create the Compose file:

nano compose.yaml

Add this:

services:

skyrimserver:

image: tiltedphoques/st-reborn-server:latest

container_name: skyrimserver

restart: unless-stopped

ports:

- "10578:10578/udp"

volumes:

- /opt/docker/skyrimserver/config:/st-server/config

- /opt/docker/skyrimserver/Data:/st-server/Data

- /opt/docker/skyrimserver/logs:/st-server/logs

stdin_open: true

tty: true

This setup keeps your config, server data, and logs outside the container. You can recreate the container without losing the main files.

2. Start The Server

Run:

• docker compose up -d

Check logs:

• docker compose logs -f

Stop the server:

• docker compose down

Restart the server:

• docker compose restart

Use Compose when you plan to keep the server online for more than a quick test. It makes restarts, updates, and folder mounts easier to manage.

3. Update The Docker Server Safely

Back up your folders first:

• cp -a /opt/docker/skyrimserver /opt/docker/skyrimserver-backup

Then update:

• docker compose pull
• docker compose up -d

Do not update the server while players are active. Stop the session, back up the files, pull the latest image, then restart.

Skyrim Together Server Download: Where Do The Server Files Come From?

Windows users get the server executable from the Skyrim Together Reborn mod files. Linux users should use the Docker image tiltedphoques/st-reborn-server:latest. Avoid random downloads because old files can break your server.

1. Windows Server Files

On Windows, the main server file is:

• SkyrimTogetherServer.exe

Do not confuse it with:

• SkyrimTogether.exe

SkyrimTogether.exe launches the client. SkyrimTogetherServer.exe starts the dedicated server.

The file path depends on your mod manager. With Vortex, the server files sit inside the Skyrim Special Edition Data\SkyrimTogetherReborn folder. With MO2, open the Skyrim Together Reborn mod folder through MO2.

2. Linux Server Files

Linux users should use Docker instead of downloading random server files.

Use this image:

• tiltedphoques/st-reborn-server:latest

This keeps the Linux setup cleaner and avoids outdated server packages.

3. Match Server And Client Versions

Every player should use the same Skyrim Together Reborn version as the server.

Version mismatch can cause:

• Failed connections
• Crashes
• Desync
• Missing UI behavior
• Server list issues

Do not use cracked copies, old Skyrim Together builds, Harbor-era guides, or random third-party server downloads.

Skyrim Together Server Ports, Firewall Rules, And Port Forwarding

Use port 10578. For Windows firewall and router forwarding, open both TCP and UDP on port 10578 because the official port-forwarding guide says to use “Both” when your router supports it. If your router forces one protocol at a time, create one TCP rule and one UDP rule.

1. Use The Default Port

The default port is:

10578

You can change it in STServer.ini, but beginners should leave it alone.

Changing the port means you must update:

• STServer.ini
• Windows Firewall
• Router forwarding rules
• Player connection address

2. Open The Port In Windows Firewall

Allow inbound traffic for:

• TCP 10578
• UDP 10578

If Windows shows a firewall prompt when you start the server, allow it.

3. Forward The Port In Your Router

Forward port 10578 to the server PC’s local IPv4 address.

Use:

Use a static LAN IP or DHCP reservation. If your server PC gets a new local IP, the router rule may point to the wrong device.

4. Test With A Remote Player

Do not rely only on browser port checkers.

Many port checkers test TCP more reliably than UDP. Some will show a failed result even when the game server works, so confirm with a real remote player.

The best test is simple:

• Start the server.
• Ask a remote friend to connect.
• Use your public IPv4 and port 10578.
• Check the server console and logs.

If LAN works but internet fails, check router forwarding, Windows Firewall, CGNAT, and double NAT.

Why Port Forwarding Still Fails: CGNAT, Double NAT, And ISP Blocks

Port forwarding only works when your router has a reachable public IPv4 address. If your ISP uses CGNAT, your server can run perfectly and still stay unreachable from the internet.

1. Check For CGNAT

CGNAT means your ISP does not give your router a real public IPv4 address.

Check this:

• Find the WAN IP in your router.
• Search “what is my IP” in a browser.
• Compare both addresses.

If the router WAN IP does not match the public IP shown online, port forwarding may fail.

Common CGNAT ranges include:

A WAN IP in the range 100.64.0.0 to 100.127.255.255 is a strong sign of CGNAT. This range belongs to the 100.64.0.0/10 shared address space reserved for carrier-grade NAT deployments.

If your router WAN IP falls in a private range such as 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, your router is behind another private network. That may indicate double NAT or ISP-side NAT, but those are private address ranges, not CGNAT ranges.

2. Check For Double NAT

Double NAT means two devices route traffic before it reaches your server.

This often happens when:

• The ISP modem acts as a router.
• Your personal router also acts as a router.
• Both devices use NAT.

Fix it by placing the ISP modem in bridge mode or forwarding the port on both devices.

3. Check ISP Blocks

Some ISPs block inbound traffic on home plans.

If your settings look correct but friends still cannot connect, ask your ISP for:

• A public IPv4 address
• No CGNAT
• Inbound traffic support
• Bridge mode support

4. Use A Workaround When Home Hosting Fails

If port forwarding still fails, use one of these paths:

A Skyrim Together dedicated server not working issue often comes down to the home network, not the game server.

Use Hamachi or ZeroTier with Skyrim Together for small private groups when port forwarding blocks you. Use a VPS or dedicated server when you want a cleaner public IP and long-term uptime.

Full STServer.ini Settings Guide: What To Configure First

STServer.ini controls server name, password, player count, port, public listing, gameplay rules, sync settings, and mod policy. Stop the server before editing this file. If you edit it while the server runs, changes may not apply and can get overwritten.

1. Find STServer.ini

The path depends on your install method.

For Vortex, use:

C:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\SkyrimTogetherReborn\config\STServer.ini

For MO2:

• Open MO2.
• Right-click Skyrim Together Reborn.
• Select Open in Explorer.
• Open the inner Skyrim Together Reborn folder.
• Open the config folder.
• Open STServer.ini.

2. Server Identity And Access Settings

Use a password for private friend groups.

Password-protected servers do not appear on the public server list. Players should join manually with direct IP and port.

3. Gameplay Rule Settings

Set gameplay rules before the first full session.

Do not change too many settings at once. Change one group of settings, restart the server, then test with one or two players.

4. Sync Settings

Treat sync settings with care.

Skyrim was built as a single-player game. Some sync options can help co-op play, but not every setting stays stable for every group, save, or mod list.

For a safer first run, keep the setup simple. Test the server with the default sync settings before changing them.

5. Mod Policy Settings

Use mod checking when your private group needs the same mod list.

This helps prevent:

• Crash loops
• Missing NPCs
• Quest desync
• Different items
• Failed connections

For the safest modded server, test this order:

1. Start with clean Skyrim Together Reborn.
2. Confirm the server works.
3. Add visual mods first.
4. Add gameplay mods slowly.
5. Test after each batch.
6. Lock the shared load order.

Skyrim Together Server Commands: What Admins Should Know

Use the server console for live commands. Use STServer.ini for permanent settings. Run /help in the console to see supported commands, and do not invent unsupported commands. The official docs list commands such as /players, /mods, /quit, /admins, /AddAdmin, and /RemoveAdmin.

1. Access The Console On Windows

Start:

• SkyrimTogetherServer.exe

Use the server window as the console.

Run:

• /help

This shows supported commands for your server version.

2. Access The Console In Docker

Attach to the container:

• docker attach skyrimserver

Run:

• /help

Leave the attached console without stopping the server:

• CTRL + P, then CTRL + Q

3. Use Commands For Live Control

Use console commands when you need live control, such as checking players or stopping the server.

Examples from the official command page include:

4. Keep Permanent Settings In STServer.ini

Use STServer.ini for stable server rules.

Use the console for temporary control.

Stop the server before editing STServer.ini. Restart after saving changes.

Enforce a Shared Mod List With loadorder.txt

Use bEnableModCheck=true when every player must run the same mod list. The server checks each player’s loadorder.txt. If the player’s load order does not match the server’s loadorder.txt, the player cannot join.

Skyrim Together Reborn works best when every player uses the same:

• Skyrim version
• Skyrim Together Reborn version
• Mod list
• Load order
• Server connection details

Mod mismatch can cause crashes, desync, missing NPCs, broken quests, missing items, and failed joins.

1. Turn On Mod Checking

Open STServer.ini.

Find:

• bEnableModCheck=false

Change it to:

• bEnableModCheck=true

Stop the server before editing STServer.ini. Save the file, then restart the server.

2. Add loadorder.txt For Vortex Servers

For Vortex, copy the source loadorder.txt from the game application data folder.

Open it through Vortex:

• Vortex → Mods → Open Game Application Data Folder → loadorder.txt

Copy loadorder.txt.

Then paste it into the Skyrim Together Reborn server Data folder:

C:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\SkyrimTogetherReborn\Data\loadorder.txt

Create the inner Data folder if it does not exist.

The folder should look like this:

Skyrim Special Edition

└── Data

└── SkyrimTogetherReborn

└── Data

└── loadorder.txt

3. Add loadorder.txt For MO2 Servers

For Mod Organizer 2, copy the source loadorder.txt from your MO2 profile folder.

The source path looks like this:

C:\Modding\MO2\profiles\[profile name]\loadorder.txt

Replace [profile name] with the active profile your group uses for Skyrim Together Reborn.

Then paste the file into the Skyrim Together Reborn server Data folder inside the MO2 mods directory:

C:\Modding\MO2\mods\Skyrim Together Reborn\SkyrimTogetherReborn\Data\loadorder.txt

Create the inner Data folder if it does not exist.

The destination should look like this:

MO2

└── mods

└── Skyrim Together Reborn

└── SkyrimTogetherReborn

└── Data

└── loadorder.txt

Do not copy the source file from the MO2 mods folder. The source loadorder.txt lives in the MO2 profiles folder.

4. Add loadorder.txt For Docker Servers

For Docker, place the approved loadorder.txt in the mounted Data folder:

/opt/docker/skyrimserver/Data/loadorder.txt

This maps into the container as:

/st-server/Data/loadorder.txt

Use the same file that your approved client profile uses.

5. Keep The Load Order Identical

Every player should use the same loadorder.txt.

If one player changes mod order, adds a plugin, removes a plugin, or updates a mod alone, that player may fail the server check.

Use one approved mod profile for the full group.

After enabling mod checking, restart the server and check logs/console for mod-policy or loadorder-related errors.

6. Set SKSE And MO2 Rules On Purpose

Use these settings with care:

Do not allow SKSE just because the Address Library name includes “SKSE Plugins.” Skyrim Together Reborn does not need SKSE by itself.

Only allow SKSE when your chosen mod list needs it.

7. Build The Modded Server Slowly

Use this testing flow:

1. Start with clean Skyrim Special Edition plus only Skyrim Together Reborn and Address Library.
2. Test the server connection.
3. Add visual mods first.
4. Add gameplay mods in small batches.
5. Test after each batch.
6. Lock the shared load order once stable.

Skyrim Together Server List: Why Your Server Does Or Does Not Appear

Your server may not appear in the public server list if it has a password, bAnnounceServer is disabled, port 10578 is blocked, the server sits behind CGNAT, or the client and server versions do not match. The official config page says passworded servers do not show on the server list.

1. The Server Has A Password

Password-protected servers do not appear on the public server list.

This is expected behavior.

Players should connect manually with:

public-ip:10578

Use this setup for private friend groups.

2. bAnnounceServer Is Disabled

bAnnounceServer controls public listing.

Use this setting:

bAnnounceServer=true

Set it to false when you want a private direct-connect server.

A public listing also needs a reachable server. The setting alone cannot fix blocked ports or CGNAT.

3. Port 10578 Is Blocked

Your server needs open network access on port 10578.

Check:

• Windows Firewall
• Router forwarding
• Correct local IPv4
• Correct public IPv4
• TCP and UDP router rules for Windows home hosting
• UDP mapping for the official Docker container

If the router rule points to the wrong PC, friends will not reach the server.

4. The Server Is Behind CGNAT

A server can run correctly and still stay unreachable from the internet.

CGNAT means your ISP does not give your router a true public IPv4 address. Port forwarding may fail even when your router settings look right.

Check your router WAN IP against your public IP. If both do not match, ask your ISP for a public IPv4 or use ZeroTier, Hamachi, PlayTogether, VPS, or a dedicated server.

5. Version Or Mod Mismatch Blocks Players

Server list issues and join failures can also come from client mismatch.

Check:

• Same Skyrim Together Reborn version
• Same Skyrim version
• Same mod list
• Same load order
• Same loadorder.txt when mod check is enabled

Fix client mismatch before changing router settings again.

Skyrim Together Dedicated Server Not Working: Complete Troubleshooting Guide

Start with the exact symptom. A working server can still fail because of firewall rules, CGNAT, wrong IP, passworded server list behavior, mod mismatch, Docker volume issues, or edited config files.

1. Fix Connection Problems First

If friends cannot join, check the network path before changing game files.

Check:

• Is the server running?
• Did you share the public IP, not the local IP?
• Did you include port 10578?
• Does Windows Firewall allow the server?
• Does the router rule point to the server PC?
• Does your router have a real public IPv4?

The official guide tells remote players to use the host’s public IPv4, while local testing uses 127.0.0.1.

2. Fix Config Problems Next

If STServer.ini changes do not apply, stop the server first.

The official config page says STServer.ini changes need a server shutdown. If you edit the file while the server runs, the server can overwrite the changes on shutdown.

3. Fix Mod Problems Last

If players crash after joining, check the mod setup.

Check:

• Same Reborn version
• Same Address Library file
• Same mod list
• Same load order
• Same loadorder.txt
• bEnableModCheck=true only when the server has the correct loadorder.txt

If only one player fails while others connect, check that player’s Skyrim version, Address Library file, Reborn version, mod list, and load order before changing server settings.

Update And Back Up A Skyrim Together Server

Back up config, Data, STServer.ini, loadorder.txt, and logs before updates. Stop the server before you update.

Update rule: never update only the server or only the clients before a group session. Keep the server and every player on the same Skyrim Together Reborn version.

Most guides stop at setup. Long-running servers need backup and update discipline.

1. What To Back Up

Back up these files and folders:

For Docker, back up:

/opt/docker/skyrimserver/config

/opt/docker/skyrimserver/Data

/opt/docker/skyrimserver/logs

2. Windows Update Workflow

Use this flow for Windows servers:

1. Tell players the server is going offline.
2. Stop SkyrimTogetherServer.exe.
3. Back up the Skyrim Together Reborn config folder.
4. Back up the Data folder if you use mod check.
5. Update Skyrim Together Reborn files.
6. Confirm the server version.
7. Start SkyrimTogetherServer.exe.
8. Ask every player to update the client.
9. Test with one player before inviting the full group.

Do not update the host while players stay connected.

3. Docker Update Workflow

Use this flow for Linux Docker servers:

1. Stop the session.
2. Back up mounted folders.
3. Pull the latest image.
4. Recreate or restart the container.
5. Check logs.
6. Confirm clients match the server version.

Run:

• cp -a /opt/docker/skyrimserver /opt/docker/skyrimserver-backup

Then update:

• docker compose pull
• docker compose up -d

Check logs:

• docker compose logs -f

If you do not use Compose, update with Docker commands:

• docker pull tiltedphoques/st-reborn-server:latest
• docker stop skyrimserver -t 1docker rm skyrimserver

Then recreate the container with the same volume mounts.

Do not delete the mounted folders. Those folders keep your config, mod policy, and logs safe.