Troubleshooting

The most common problems on a Satisfactory server, and how to fix them. In every case, the panel Console is your first tool: read the last lines shown before the stop or the error.

The server does not start

It stops after installing a mod

A mod that is not compatible with the game version, with dedicated servers or with Linux often blocks startup.

1. Stop the server
2. Remove the last mod you added (with SMM or from FactoryGame/Mods/)
3. Restart
4. If the server starts again, the mod is the cause: check its compatibility on ficsit.app

See Installing mods.

Error in a configuration file

A badly written section in Game.ini or Engine.ini can prevent the server from starting or be ignored. Go back to your last working version of the file (or remove your additions), with the server stopped. See Server settings.

It stops while loading the session

On a large factory, loading the save takes a lot of RAM. If the server stops during this phase with no other obvious error, memory is probably insufficient: see Not enough memory in late game.

Players who cannot connect

Symptom	Likely cause	Solution
The server shows as offline in the Server Manager	Server stopped or still loading	Check the panel Console and wait for loading to finish
Server not found after Add Server	Wrong IP or port	Use the IP and port shown in the panel, not 7777
The server is visible but connecting fails	Different version, or port changed by hand	Same version for everyone; do not change the ports (see Server ports)
Password rejected	Player password changed	Check the player password in the server settings
Disconnected right after loading	Different mods between the player and the server	Same mods, same version for everyone (see Installing mods)
Server full	Player limit reached (4 by default)	Raise MaxPlayers in Game.ini (see Server settings)
No access to the settings	Server claimed by someone else, or admin password lost	See Forgotten admin password

Ports

Opening the required ports is handled by YorkHost. Do not change the ports in the configuration files or the Startup tab. See Server ports and Unable to connect to the server.

Client version different from the server

The game and the server must be on the same version. Right after a Satisfactory update, your game may be updated before the server (or the other way around).

• Compare the version shown by the Server Manager with your game's version
• Restart the server from the panel Console, then check the version again
• If you play on the Experimental branch, the server must be on it too: Experimental and stable versions are not compatible with each other
• If the server version is still different, contact support and mention your game version

Mods and updates

A game update can make your mods temporarily incompatible. On a modded server, wait for your mods to be updated before updating, and take a backup.

Not enough memory in late game

Satisfactory's RAM usage grows with the size of your factory: buildings, belts, trains, drones, vehicles. A save that ran fine in the early game can max out memory in the late game. Typical symptoms: the server stops while loading or during play, or gets slower and slower.

1. Check RAM usage in the panel when the problem occurs. See also Performance debugging.
2. Enable Auto Pause so the server does not simulate the factory when nobody is playing (see Server settings).
3. Restart the server regularly, for example every night, with an automatic restart.
4. Lighten your mod list: large content packs noticeably increase memory usage.
5. Move up to a bigger plan if RAM stays maxed out: expect 12 to 16 GB, or more, for a large late-game factory. You can change plans from your client area.

Lag and slowdowns

• Slowdown on every autosave: normal on a large factory, saving takes a moment. Lengthen the autosave interval a little (see Server settings).
• Constant lag: the simulation mostly runs on one main core; the bigger the factory, the harder that core works. Regular restarts and a suitable plan help.
• Desync or stutter for players: check the Network Quality setting in the Server Manager, and the affected player's connection.

Still stuck?

Contact support 7 days a week on Discord or through your client area, including:

• your server name
• what you changed just before the problem
• your game version (Steam or Epic, stable or Experimental branch)
• the last lines of the console when the error occurred