SM
Satisfactory Modding•3mo ago
Drauku

SMM managed selfhosted server not loading mods

I've found two other posts about this issue: https://discord.com/channels/555424930502541343/1384647971034894416 https://discord.com/channels/555424930502541343/1385568615054704640 I've double checked, and all the mods I want to use are present in the server's Mods folder, but the server does not load/install those mods when started. I've tried sending the mods when the server is off, when it's on, and restarting it. I've also tried creating a new game with the mods already in the folder. What am I doing wrong?
No description
Solution:
For anyone who stumbles on this in the future, I had to add this environment variable to my wolveix container: 
    environment:
      - ROOTLESS=false
    environment:
      - ROOTLESS=false
...
Jump to solution
6 Replies
Drauku
DraukuOP•3mo ago
FICSIT-Fred
FICSIT-Fred•3mo ago
SMM Version: 3.0.3
SML Version: 3.11.1
Installed Mods: 22
Game: WindowsClient CL 418783 from steam
Path: `g:\Games\Steam\steamapps\common\Satisfactory`
Command Line: cmd /C start  steam://rungameid/526870-NO_EOS_OVERLAY
SMM Version: 3.0.3
SML Version: 3.11.1
Installed Mods: 22
Game: WindowsClient CL 418783 from steam
Path: `g:\Games\Steam\steamapps\common\Satisfactory`
Command Line: cmd /C start  steam://rungameid/526870-NO_EOS_OVERLAY
-# Responding to Key Details for SMMDebug-2025-06-20-22-53-12.zip triggered by @Drauku
Drauku
DraukuOP•3mo ago
Server is running on Debian in a Docker container from wolveix.
sjhoward
sjhoward•3mo ago
Seems like mods are turned off in SMM Certainly you want to make changes only when the server is off Hmm the latest included server log in your debug zip is from 2 days ago
Drauku
DraukuOP•3mo ago
if it is, then I dated it incorrectly. I copied the server log that was dated today from my linuxserver and then manually typed the name. Uh... how? The SMM interface says they are on, and the mods are in the folders for my client and my server. Thanks for replying, by the way... I've been trying to get these working for days now, lol.
Solution
Drauku
Drauku•3mo ago
For anyone who stumbles on this in the future, I had to add this environment variable to my wolveix container: 
    environment:
      - ROOTLESS=false
    environment:
      - ROOTLESS=false
Which means it was a permissions issue... it's always a permissions issue /sigh.

Did you find this page helpful?