[1.5.0] Web server does not auto-start on Linux dedicated server - Web_Autostart not recognized in FGUserSettings

[NoisyBoyFR]

Description

After updating to FRM 1.5.0 on Satisfactory 1.2.2.2, the web server does not start automatically on a Linux dedicated server. The Web_Autostart setting added to GameUserSettings.ini is silently removed at server startup and is never applied.

Environment

• Satisfactory version: 1.2.2.2 (CL 491125)
• SML version: 3.12.0
• FRM version: 1.5.0
• Server OS: Linux (Debian) via Docker (wolveix/satisfactory-server)

Steps to Reproduce

1. Install FRM 1.5.0 on a Linux dedicated server running Satisfactory 1.2.2.2
2. Add the following to GameUserSettings.ini under [/Script/FactoryGame.FGGameUserSettings]:

mBoolValues=(("FicsitRemoteMonitoring.Server.uWS.Web_Autostart", True))

3. Start the server
4. The entry is silently removed from GameUserSettings.ini and the web server does not start

Expected Behavior

The FRM web server should start automatically on port 8080 when Web_Autostart is set to True.

Actual Behavior

• The Web_Autostart entry is removed from GameUserSettings.ini at every startup
• No port is listening on 8080 (verified via /proc/net/tcp6)
• The AuthenticationToken IS correctly read and applied:
  LogFRMConfigManager: SetConfigFromInput: Applied setting 'FicsitRemoteMonitoring.Server.uWS.AuthenticationToken'
• No Applied setting 'Web_Autostart' message ever appears in logs
• The following warning appears at startup:

LogAssetManager: Warning: Invalid Primary Asset Type FGGameFeatureData:FicsitRemoteMonitoring: ChangeBundleStateForPrimaryAssets failed to find NameData

Relevant Logs

LogSatisfactoryModLoader: Display: FicsitRemoteMonitoring: 1.5.0
LogAssetManager: Warning: Invalid Primary Asset Type FGGameFeatureData:FicsitRemoteMonitoring: ChangeBundleStateForPrimaryAssets failed to find NameData
LogSubsystemManager: Registered subsystem class '/FicsitRemoteMonitoring/Subsystems/FicsitRemoteMonitoring_BP.FicsitRemoteMonitoring_BP_C'
LogSubsystemManager: Registered subsystem class '/FicsitRemoteMonitoring/Subsystems/FicsitRemoteMonitoringServer_BP.FicsitRemoteMonitoringServer_BP_C'
LogFRMConfigManager: SetConfigFromInput: Applied setting 'FicsitRemoteMonitoring.Server.uWS.AuthenticationToken'

Notes

• The web server CAN be started manually in-game via /frm http start — endpoints are all registered correctly (92 endpoints)
• The mStringValues entry for AuthenticationToken works correctly and persists between restarts
• On the previous version (1.4.x / Satisfactory 1.1), Web_Autostart: true in WebServer.cfg worked correctly
• This makes automated/headless dedicated server deployments unable to use FRM without manual intervention after each restart

[NoisyBoyFR]

The problem was resolved by simply checking the "Auto Start" option directly in the server's Ficsit Remote Monitoring settings.

[porisius]

Okay, glad that you got gotten the problem resolved, however, the issue here really is how Coffee Stain Studios did what they call FGUserSettings.

The prefix FG, if you were unaware, stands for FactoryGame, which is the Unreal Engine uProject Name for Satisfactory. Thus, FGUserSettings is a FactoryGame Data Type Asset for User Settings.

Remote Monitoring is now using the base game's system for configurations. Coffee Stain, in their infinite wisdom, decided that CheckBox values as defined in their Value Selector are to be stored as integers.

If you look at your GameUserSettings.ini file, you will notice a line like this.

mIntValues=(("FG.DSAutoPause", 0),("FicsitRemoteMonitoring.Server.Debug.JSONDebug", 1),("FicsitRemoteMonitoring.Server.uWS.Autostart", 1))

FG.DSAutoPause, obviously, is the Auto Pause when noone is logged into the server. It is also a checkbox.
I have the HTTP side set to AutoStart and the JSON Debug Mode, i.e. Pretty JSON, enabled. They also get the option value of "1".

The SML Mod Config System did use a boolean while CSS used int. Due to issues with the SML Config System and Remote Monitoring, I moved all of the options over to FGUserSettings which does have the benefit of options being easily configurable for Dedicated Servers in the Server Settings UI. The only downside is that I cannot use Arrays or Booleans (in their pure form). I am hoping to not have to do anymore shake-ups in the mod going forward.

So, please, enjoy Satisfactory, enjoy the mod, I really do appreciate you making mention as it makes me think that the Mod Documentation needs more work and polish. I apologize for the long comment, but honestly, I expect someone else to ask the exact same question in the near future. I can only hope they read this and learn.

I will see what I can do as I also have some tasks for the main modding community's documentation as well, regarding this exact feature.

[NoisyBoyFR]

Thank you so much for this detailed explanation! This is exactly the kind of context that was missing from the documentation.

To summarize for anyone who finds this issue later:

• Web_Autostart must be stored as an integer (1 = enabled) inside mIntValues, not as a boolean in mBoolValues.
• The correct key is FicsitRemoteMonitoring.Server.uWS.Autostart.
• The easiest way to configure this on a dedicated server is through the in-game Server Settings UI, which writes the value correctly to GameUserSettings.ini automatically.

The resulting line in GameUserSettings.ini should look like:

mIntValues=(...,("FicsitRemoteMonitoring.Server.uWS.Autostart", 1))

This works perfectly on our Linux Docker dedicated server (wolveix/satisfactory-server). Thank you again for taking the time to explain the FGUserSettings system — it makes total sense now that CSS chose integers for checkboxes. Looking forward to future documentation improvements!

[porisius]

Please note that FicsitRemoteMonitoring.Server.<option> is for Shipping Server builds only, i.e. Win64/Linux Dedi Servers.

FicsitRemoteMonitoring.<option> is for the clients. I had a lot of trouble figuring them all out, and at one point when I got it all working, I started to realized that there was a solid chance of just having one format.

However, I have 26 configuration options for this mod. It was working, working solid, and in some sense, made sense. Don't fix what ain't broken, right?

I see how I am going to write this one up, but in the mean time I hope this helps anyone reading.

[porisius]

I updated the docs. Please let me know if that helps.

b059ae1

https://docs.ficsit.app/ficsitremotemonitoring/latest/config/current/config.html