Crashes & startup failures
This guide covers crashes & startup failures for a Frags4u-managed Satisfactory dedicated server. It is written for the Frags4u managed environment, so the server identity, allocated resources and network values shown in the Panel take priority over defaults copied from a generic self-hosting guide.
Satisfactory operational notes • Failure evidence: If the server launches but cannot be claimed/joined, separate game networking, reliable messaging and persistent server-state issues using current logs. • Startup: The Linux dedicated server runs FactoryServer.sh with managed resources and Frags4u networking. • Mods / frameworks: Frags4u treats the Satisfactory Mod Manager/ficsit-cli ecosystem as compatibility-sensitive. Only deploy supported versions and re-check after game updates. • Updates: Managed server-file updates use SteamCMD app 1690800. Confirm save/config protection and mod compatibility before reopening the server.
Recommended checks
- Record when the crash/failure occurred and what changed immediately beforehand.
- Check whether the process exits, loops, or remains running but unhealthy.
- Review recent config/mod/framework changes before touching base-game assets.
- Use AI Support from the Technical ticket for approved evidence collection; any bounded repair still requires customer consent.
When to stop changing things If the failure persists after one controlled test, avoid repeated restarts, broad file deletion or unrelated configuration changes. Preserve the newest evidence. A clean process start, a listening game endpoint and a successful client connection are separate signals; record which one is failing.
What to send Support Include the affected server, approximate failure time, exact error text, the last change made and whether the problem affects startup, connectivity, performance, updates or mods. Technical tickets remain bound to the selected game server so staff and AI Support can inspect the correct managed context rather than guessing.
Backups and recovery Before destructive maintenance, keep a verified recovery point. For Satisfactory, the persistent save/world and configuration areas described above should be treated separately from replaceable base-game assets. Do not use a wipe, reinstall or deletion of runtime files as a first troubleshooting step.
Frags4u AI Support safety boundary AI Support can only use approved typed support actions inside the customer's server boundary. It has no root, sudo, general shell, SSH or node-administration access. Any bounded repair requires customer consent, creates a protected snapshot first, remains limited by the existing remediation policy, and is followed by restart/post-repair verification where a restart is required.