Fix common Satisfactory server errors

Most Satisfactory server problems come down to four things: the wrong port, a version mismatch, the certificate prompt, or joining some other way than the Server Manager. Start with the error you see. The most common ones are first.

Before anything else, open Overview and check the server says Running or Sleeping. If it says Stopped, press Start. If it crashed, the Console shows a crash helper card with a hint and a fix button when it recognises the problem.

Joining and connecting

The Server Manager shows your server as offline

The game can’t reach the server at the address and port you saved.

1. Check the port. Edit the server in your Server Manager and compare it with the address card on Overview. It must be your server’s port, like 30412, not 7777.
2. Check the address. Type it without https://, without spaces, and without the port: assembly.play.wilderack.com.
3. Give a sleeping server a few seconds. Opening it in the Server Manager wakes it. If it still looks offline, open the wake link play.wilderack.com/w/assembly, wake it, and try again.
4. Restart the server from Overview.
5. Still offline? Remove the server from your Server Manager and add it again.

“Failed to connect to the Server API”

The Server Manager talks to your server through a small web service on the game port, called the Server API. This message means that talk failed.

1. Check the address and port, as above. A wrong port is the most common cause.
2. Make sure your game is on the same version as the server. See You can’t join after a game update.
3. Restart the server from Overview, wait until it says Running, then try again.
4. If you typed an IPv6 address by hand, put it in square brackets. Using your address name avoids this.
5. Remove the server from your Server Manager, add it again, and accept the certificate prompt.

A certificate warning when you connect

The first time you add a server, the game warns about its certificate. Every Satisfactory server makes its own certificate, so the game can’t check it against a known list. That’s normal. Accept it and carry on.

You may see the warning again after the server’s settings are reset, for example after a forgotten-password reset. That’s also expected.

If you see “certificate is not yet valid”, a clock is wrong. Our servers keep the right time, so check your PC:

1. In Windows, open Settings > Time & language > Date & time.
2. Turn on setting the time and time zone automatically.
3. Restart the game and try again.

“Encryption token missing”

You tried to join some other way than the Server Manager, such as a friend’s invite.

1. Open Server Manager from the main menu.
2. Add your server with its address and port, if it isn’t there yet.
3. Sign in, then select Join Game on the Status tab.

You can’t join after a game update

Your game and the server are on different versions. This usually happens for a short time after a Satisfactory update.

1. In the panel, check the game version in Settings. If it’s pinned to an older version, unpin it, or ask everyone to play that version.
2. Restart the server from Overview. With auto-update on, a fresh start moves it to the newest version.
3. Make sure nobody is on the Experimental branch. In Steam, right-click Satisfactory, open Properties > Betas and pick none.
4. If you use mods, see the server won’t start after adding mods. Updates often break mods for a while.

The game asks you to claim the server

We claim your server on its first start. If the game offers to claim it anyway, the server’s settings were reset. Claim it right away, before anyone else does. The steps are in Claim your Satisfactory server.

If claiming fails:

1. Restart the server from Overview and try once more.
2. Make sure your game version matches the server.
3. Write to support@wilderack.com if it still fails. We can reset it for you.

You forgot the admin password

Set a new one in Settings in the panel. Your factory and saves stay as they are. The manual way, with its side effects, is in Claim your Satisfactory server.

Playing and running the server

Players get stuck loading or time out

A big save takes a while to send to a joining player.

1. Have players join one at a time.
2. Raise InitialConnectTimeout and ConnectionTimeout in Engine.ini, with the server stopped. See the config reference.
3. Make sure everyone has the latest game version. Recent patches include fixes for joining big saves.
4. If every join gets stuck, the server’s second port (for game data) may not be reachable. Restart the server from Overview, and write to support@wilderack.com if it keeps happening.

Friends can’t join because the server is full

Satisfactory allows 4 players by default. Raise the player limit in Settings, or change MaxPlayers in Game.ini. More players need more RAM, so check performance tips first.

The server won’t start after adding mods

A mod is broken, out of date, or missing something it needs.

1. Open the Console and look for the crash helper card. It often names the mod.
2. Remove the mod you added or updated last from Mods, then start again.
3. After a game update, pin the old game version in Settings until your mods catch up.
4. If nothing works, restore the backup we made before the mod change, from Backups.

Make sure each mod supports dedicated servers. On ficsit.app, look for the check mark under Server. See How to add mods to a Satisfactory server.

Still stuck?

Write to support@wilderack.com with your server’s address and what you see. A real person reads every message. Our status page shows if anything is wrong on our side.