How to Install Mods on Your Satisfactory Server with SMM

What You Need

To run mods on your DoomHosting Satisfactory server you need:

• Satisfactory Mod Manager (SMM) installed on your PC
• SFTP credentials from your DoomHosting panel
• The server in a stopped state during the install
• Every player who joins must install the same mods locally

Mods are distributed through ficsit.app, the official Satisfactory mod portal. SMM is the supported tool for installing them on both clients and dedicated servers.

Step 1: Download and Install SMM

1. Go to the Satisfactory Mod Manager GitHub releases page.
2. Download the installer for your OS (Windows, macOS, or Linux).
3. Run the installer and launch SMM.

The first time you start SMM it will detect your local Satisfactory install and pick up your single-player mod profile automatically.

Step 2: Get Your SFTP Credentials

1. Log in to the DoomHosting Panel and open your Satisfactory server.
2. At the bottom of the sidebar, find the SFTP Details section. You'll see:
   • SFTP Server: the host and port (e.g. sftp://node.doomhosting.com:2022)
   • Username: usually youremail.identifier
   • Password: the same password you use to log into the panel

Copy these. You'll paste them into SMM next.

Step 3: Stop the Server

In the panel, click Stop and wait until the status changes to Offline. Installing mods on a running server can corrupt files.

Step 4: Add Your Server in SMM

1. In SMM, click the Server Management icon (the cloud/server icon in the top bar).
2. Click Add New Server.
3. Fill in:
   • Protocol: SFTP
   • Host: the host from your panel (without the sftp:// and without the port)
   • Port: 2022
   • Username: from the panel
   • Password: from the panel
   • Install path: /FactoryGame (path relative to the server root; SMM resolves it correctly)
4. Click Connect.

If the connection fails, double-check that the host and port are split correctly and that the server is fully Offline.

Step 5: Install Mods

With SMM connected to your server:

1. Open the Mods tab.
2. Use the filter dropdown and set it to Compatible to hide client-only mods. Server-side mods are flagged as compatible.
3. Tick the mods you want.
4. Click Apply Changes in the top right.

SMM downloads each mod from ficsit.app and uploads it to your server's /home/container/FactoryGame/Mods/ folder automatically.

Step 6: Start the Server

Back in the DoomHosting Panel, click Start. Watch the console. Mods are loaded during startup and any with errors will be flagged in the log.

Step 7: Every Player Installs the Same Mods

Mods only work if all clients and the server run the same versions of the same mods.

The easiest way to keep everyone in sync is to share a mod profile:

1. In SMM, open Profiles → Export Profile and send the file to your friends.
2. They open SMM → Profiles → Import Profile and select the file.
3. SMM installs the matching mods to their local Satisfactory.
4. They restart Satisfactory.

Compatibility Notes

• Stable vs Experimental: mods are tagged with the game version they support. If your server is on the Experimental branch, filter mods by that version in SMM or some will fail to load. See our guide on switching branches.
• Mod updates can break saves: when a mod updates, the new version may not load an old save. Always back up your save before changing mods.
• Client-only mods don't need to be on the server. SMM marks them clearly. They won't appear when you filter by Compatible.

Troubleshooting

• SMM "Connection refused": server isn't fully stopped, or port 2022 is wrong. The panel shows the correct port at the bottom of the sidebar.
• Mods don't load on startup: open the panel console and search for the mod name. The most common cause is a mod compiled for a different game version than your server.
• "Mod mismatch" when joining: a player has different mod versions than the server. Re-export your SMM profile and have them re-import.
• Mods folder doesn't exist: open the panel File Manager and navigate to /FactoryGame. If there's no Mods folder, SMM hasn't uploaded successfully yet. Try the install again with the server fully stopped.