Satisfactory Dedicated Server Troubleshooting

Satisfactory Dedicated Server Troubleshooting

---

Players Can't Connect / Server Not Found

Wrong port argument order — most common cause:

Launch arguments for Satisfactory must come before -log -unattended. Arguments after these flags are silently ignored by the Unreal Engine launcher.

Incorrect (ports ignored):

./FactoryServer.sh -log -unattended -Port=7777 -BeaconPort=15000

Correct:

./FactoryServer.sh -Port=7777 -BeaconPort=15000 -ServerQueryPort=15777 -log -unattended

---

Server Not Appearing in Server Browser

The server browser uses the beacon and query ports (15000 and 15777). Check:

1. Both ports are open in your firewall:

   sudo ufw allow 15000/udp && sudo ufw allow 15777/udp
   sudo ufw status
   

2. The correct port arguments were passed before -log -unattended
3. Allow a few minutes after startup — the server browser can be slow to list new servers

Players can always use Direct Connect with your IP and port 7777 as a workaround.

---

"Version Mismatch" When Connecting

The client and server must be on the same version. Update the server:

~/steamcmd/steamcmd.sh \
  +force_install_dir /home/steam/satisfactory \
  +login anonymous \
  +app_update 1690800 validate \
  +quit

If using the experimental branch, ensure both client and server are on experimental.

---

Server Crashes or Hangs Frequently

Check tick rate in Engine.ini:

The tick rate must be 30 Hz. Ensure Engine.ini contains:

[/Script/Engine.GameNetworkManager]
TickInterval=0.03333

Increase RAM: Large factories require significant RAM. 8–16 GB is recommended for mid-to-late game.

Check for mod conflicts: If mods are installed, try running without them to isolate the crash.

---

High Latency / Factory Lag

Satisfactory server performance scales with factory complexity. Common fixes:

• Reduce Autosave frequency to avoid lag spikes: increase mAutosaveInterval in GameUserSettings.ini to 600+ seconds
• Disable or reduce particle effects in client video settings (doesn't affect server)
• Consolidate power infrastructure — large distributed power grids with many switches stress the server

---

Save File Won't Load

File in wrong directory: Save files must be in FactoryGame/Saved/SaveGames/server/. Files in other locations won't appear in Server Manager.

Corrupted save: Restore from backup. If no backup exists, try loading an older autosave file from the same directory.

Save from newer game version: Older server versions cannot load saves from newer game versions. Update the server to the same version as the save file.

---

Server Claiming Issues

"Claim" option not appearing: The server must be in an unclaimed state. If it was claimed previously and you want to reclaim:

• The current owner must transfer ownership in Server Manager
• Or delete GameUserSettings.ini and the save data to reset (destructive — back up saves first)

Lost admin password: There is no config file to read the admin password from directly. Options:

• Ask another server admin to reset it via Server Manager (if they have access)
• Use a Satisfactory save file editor (community tool — not officially supported)

---

Firewall Check Commands

# Check all open ports
sudo ufw status verbose

# Verify server is listening
ss -ulnp | grep -E "7777|15000|15777"

# Test from local machine (won't test external access but confirms process is running)
nc -zvu localhost 7777