Contents show Potential fixes to “Failed to connect to server API” error in Satisfactory Fix port forwarding Remove the -multihome Steam launch string Change network type (for Unraid users)
Satisfactory is a fun game by yourself, but even better on a server with friends. You can build up the factory together, but connection issues can stall your progress. Setting up a dedicated server can be complicated sometimes, and with the game’s structure changing during the development, some settings don’t work as they used to. This can cause errors, such as getting the “Failed to connect to server API” message. We have a few suggestions to try to fix it.
Potential fixes to “Failed to connect to server API” error in Satisfactory
While there is no official fix for this issue yet, dedicated players have banded together on various forums to discuss potential solutions. We’ve compiled some of the ones that have been reported to work after the Satisfactory 1.0 update.
Ultimately, an official fix from the Satisfactory devs will supercede most player solutions. However, until such time, it is worth trying these fixes for the “Failed to connect to server API” error.
Fix port forwarding
Due to the recent changes in how API functions, you can try fixing the port forwarding. By default, they would be set to UDP instead of TCP. We’re going to change that. Here’s what to do:
- Access the port settings on your router
- Change forwarding on port 7777 (game port) to UDP + TCP
- Change forwarding on port 15000 (beacon port) to UDP + TCP
- Change forwarding on port 15777 (query port) to UDP + TCP
Remove the -multihome Steam launch string
Previously, you had to use Steam commands to run a dedicated server. This is no longer the case, because the server now runs in IPv6 and IPv4 by default. If you have the “-multihome=0.0.0.0” string added to your Steam launch options for Satisfactory, simply remove it and try again.
Change network type (for Unraid users)
If you’re playing the game through the Unraid OS, you could be getting the error message due to a network type issue. Go to your Network settings and under Network Type, switch from Bridge to Host.
After that, make sure that your ports are being forwarded, as we explained above. Then, run Satisfactory and check the Server Manager in the main menu. You should now be able to see your dedicated server as normal.
