Satisfactory 1.0 - Can't connect to server

[Entryx89]

Hello,

maybe someone can help? :)

I've installed Satisfactory Dedicated Server on Windows Server 2019.
Once I will connect with the Server Manager, the game shows following message:

Can't connect to server. Failed to connect to the Server API.

Yesterday everything was fine with latest Update 8 Build.

It seems there was some changes in the dedicated server application.
The log from the server show something special to me:

[2024.09.10-19.28.55:287][ 0]LogServer: Warning: Server API is running using a Self-Signed Certificate.
[2024.09.10-19.28.55:288][ 0]LogServer: Warning: To verify the certificate integrity on the Client, make sure the following Fingerprint matches with the Client one:

In the wikis for Satisfactory Dedicated Server is no hint how can I solve that.
Maybe someone here has an idea? ^^

[Xelo]

port 7777 used to be udp only. Now you should have it forward BOTH UDP and TCP. That's what fixed it for me.

[Rush Sykes]

same issue, cannot find a proper fix, I also enabled both tcp and udp on 7777, still to no avail

[omega552003]

Firstly, open up ports 7777UDP/TCP. Also there is a known issue with the TCP port not binding correctly so until a fix is pushed its going to dynamically select a random wrong port. Also the Wiki is not up to date.

[PRObert]

Originally posted by Xelo:

port 7777 used to be udp only. Now you should have it forward BOTH UDP and TCP. That's what fixed it for me.

I can confirm that the server now uses both TCP and UDP port 7777.

And if you used the -multihome=0.0.0.0 option in the past, try running without this option. That's what fixed it for me (Linux server).

[Bannukutuku]

Make sure 7777 is open both UDP/TCP and outbound/inbound in firewall settings
Remove any -multihome switches
Make sure steamCMD is updated
Then, run server.bat to update SatisfactoryDedicatedserver.exe (follow the instructions to configure the .bat if you haven't done so; google the instructions)
Throw in a reboot or 3 just in case
That's how I finally got it working.

[Entryx89]

Thanks for your feedback.

TCP/UDP 7777 was already configured, but I was starting with "-multihome". After remove this command, the server is reachable and I can connect.

[chillkill]

If you are hosting using docker via unraid change the Network Type in the container settings to Host.

[Rowan]

Check your netstat.

I'm betting your server is binding TCP:7777 to the loopback interface (127.0.0.1) and not your server's IP address. To solve that problem under Linux, we used rinetd to create an internal port-forward of the above, so the server routed <IP>:7777/tcp to 127.0.0.1:7777/tcp, and then external client server managers could talk to it and play.

Here is an article from their QA:

https://questions.satisfactorygame.com/post/66e07bca772a987f4a8a9c02

[Chaos "Fox" Overlord]

Environment:

Satisfactory 1.0 Dedicated Server via Steam on Ubuntu 24.04 (vRoot)


Problem:

UDP Listner 0.0.0.0:7777, but TCP (API) Listner only on 127.0.0.1:7777, thus not reachable, thus leading to "Failed to connect to API"-Error in Client


Solution:

Setting up a DNAT, Code:

sudo iptables -t nat -A PREROUTING -i <your_external_interface> -p tcp --dport 7777 -j DNAT --to 127.0.0.1:7777
sudo sysctl -w net.ipv4.conf.<your_external_interface>.route_localnet=1

First line sets up the routing from your external interface to 127.0.0.1. The route back is automaticly managed by conntrack.
Second line allows localnet Adresses (e.g. 127.0.0.1) on your external interface after rewrting its destination (see first line) to prevent discarding.
Replace <your_external_interface> with the name of your external interface, e.g. eth0, ens6, etc..


Disclaimer:

Parameter -multihome=0.0.0.0 is (still) used, removing the parameter not tested.
Similar solution for other OS (e.g. Windows) may or may not work.