How to Fix Failed to Connect to the Server API Error in Satisfactory

Satisfactory is finally out of early access after nearly five years in development. The 1.0 release is the biggest update yet and introduces tons of new content for players to try out. It has also introduced some technical headaches for players to resolve, especially those who are running dedicated servers. If you’re constantly running into the “Failed to Connect to the Server API” error in Satisfactory, here is how you can fix that.

Fixing the Satisfactory Failed to Connect to the Server API Error

If you’re running a dedicated server in Satisfactory, you’ll need to make a few changes to accommodate the 1.0 release, especially when it comes to port forwarding.

Forward All Ports to both TCP and UPD

The server API is running on TCP this time instead of UDP, so you need to forward ports 7777 (Game Port), 15000 (Beacon Port), and 15777 (Query Port) to both UDP + TCP instead of just UDP in your router. All three ports need to be forwarded to both UDP and TCP so that the dedicated servers can connect properly.

Remove -multihome Command

If you were using the -multihome=0.0.0.0 command to run your dedicated server, you don’t need it anymore, as the server runs in ipv6 and ipv4 by default.

Unraid Users: Change Network Type from Bridge to Host

If you are an Unraid user, switch the Network type from Bridge to Host.

The most important change is still to forward the ports to both TCP and UDP, as explained above, especially the 7777 game port. After you’re done, your dedicated servers will show up correctly in the Server Manager, which can be accessed from the Main Menu in-game.

The 1.0 release has largely been a smooth launch, but some users have reported Unreal Engine crashes in Satisfactory, that can be fixed with a simple tweak in the launch options.