Dedicated Server

[R!PSAW]

Not sure if the update came out for the server yet but mine updated 'something'

However, I'm seeing an error that shows 'Failed to connect to Server API' when trying to connect to the server?

[Holtron]

I'll try a fresh install I suppose.

[negativefx]

Error log is reporting:

Project file not found: /home/steam/Steam/steamapps/common/SatisfactoryDedicatedServer/FactoryGame/FactoryGame.uproject

This is the same error I saw on Windows when trying to directly run FactoryGameSteam.exe before they fixed the client version.
Based on this, I suspect dedicated server executables are seeing the same issue as client.

[Xorinzor]

Originally posted by negativefx:

Based on this, I suspect dedicated server executables are seeing the same issue as client.

That's very unlikely since the server does run. It just doesn't seem to establish a connection.

[froggleston]

How did you start your server? I used to use the `multihome 0.0.0.0` setting which gave me the error. Starting the server without this option, i.e. `./FactoryServer.sh` worked.

[R!PSAW]

These are the red errors in seeing in my console log:

0]LogOnlineSchema: Error: Invalid schema category lobby: Service descriptor id lobby not found.
0]LogOnlineSchema: Error: Invalid schema category lobbymember: Service descriptor id lobbymember not found.

[froggleston]

@joe This usually means you still have something running on 7777

[Bloodimus]

I got it working. Opened 7777/tcp and updated files via steamcmd like 3-4 times.

[Xorinzor]

Can confirm that removing the "-multihome=0.0.0.0" argument fixed it for me

[Joe Piscopo]

Changing the port away from the default 7777 got it to work for me at least when not connecting through a firewall

[Holtron]

Removing "-multihome=0.0.0.0" from the service file worked for me as well. Asks for a Certificate approval but then plays nice. Thanks @froggleston.

[Fana]

Ich777's docker on Unraid seems to be the problem, it doesn't work even locally, so that might be your problem if you're using that docker.

[Cherubum]

Server listens on TCP:7777 for localhost only. So im guessing those with dedicated servers on the same box as their game will work but those connecting over network will not.

[Dragon]

I had to set network_mode: host for a dockerised version to work, not sure if it's binding an additional port somewhere (Tried allowing both tcp and udp on 7777 and others)

[Legion495]

Originally posted by Xorinzor:

Same issue here, server log does show this message "LogNet: NotifyAcceptingConnection accepted from: <MY_IP>" but the connection just won't establish.

Same. Says even "Not Authenticated" in the Server Manager.

[Anonimiss]

Originally posted by Kuromi:

just open TCP/UDP 7777 i had only UDP open after that its works

Thanks, was able to get my server working after adding TCP to my firewall rules and adjusting my Port Forwarding to include both TCP/UDP.

After, I restarted the server. A certificate message appeared in the game, I clicked Yes and then was able to get in.