Please give me some time I have to look into what's causing this.

 

@spotopolis & @Snappie88

Are you also all sure that you've forwarded the TCP port in your firewall too?

Yes. And this is a local server on my home network, so even If I didn't, port forwarding shouldn't matter as I am directly connecting to the local IP

Just now, ich777 said:

Please give me some time I have to look into what's causing this.

 

Are you also all sure that you've forwarded the TCP port in your firewall too?

Aye, both TCP and UDP. And no worries, I'm just happy you're here!

I see there is another user hosting a Docker for Satisfactory on the official Discord. It looks like they are working on the API fix as well.

I'm getting the same error about API people on the subreddit are speculating it's because they added TLS and it's using a self signed cert.

I'm getting the API failure too. Does it have to do with the self-signed certificate that was regenerated? I've mapped the TCP and UDP port on the container, both 7777

@ich777

Here is a link to the github where they (Wolveix) are working on the API issue.

(4) 1.0 API Connection Issue · Issue #260 · wolveix/satisfactory-server (github.com)

Edited September 10, 20242 yr by spotopolis

You guys have to give me some time I'm currently not at home and I can't push a fix that you are demanding so immideately.

 

I know already what the issue is.

Sorry. Not trying to be demanding. Trying to assist. No rush on my end. I appreciate your work. I use a lot of your containers.

I removed Multihome from the perms and it worked for me

1 minute ago, bbreau6 said:

I removed Multihome from the perms and it worked for me

Please double check, that doesn't fix it for me, the actual problem is that the http api binds to the loopback interface so to speak 127.0.0.1 and not 0.0.0.0 so it will not work properly, I assume if you change the network mode to br0 or host that it will work but this is not the recommended way of doing it.

So the actual workaround for now is to either set the containers Network mode to Host or br0 (if you choose br0 give it a local IP address) and remove -multihome=0.0.0.0 from the EXTRA_PARAMS

2 minutes ago, ich777 said:

Please double check, that doesn't fix it for me, the actual problem is that the http api binds to the loopback interface so to speak 127.0.0.1 and not 0.0.0.0 so it will not work properly, I assume if you change the network mode to br0 or host that it will work but this is not the recommended way of doing it.

Removing multihome did not work for me either.

Just now, gevsan said:

Removing multihome did not work for me either.

Set the network as mentioned here:

 

1 minute ago, ich777 said:

Please double check, that doesn't fix it for me, the actual problem is that the http api binds to the loopback interface so to speak 127.0.0.1 and not 0.0.0.0 so it will not work properly, I assume if you change the network mode to br0 or host that it will work but this is not the recommended way of doing it.

I re-checked and yes my container was set to Network Type: Host

I've got a temporary workaround courtesy of Wolveix. Unraid is weird so you need to delete any old 15000 ports. Remove multihome. Then add a new port of 7777 for TCP (7777 for UDP should be included). Change network mode from bridge to host (do this at your own risk) but that fixed the API error. Seems this is ultimately a coffee stain studio issue.

My network is br2 and I removed -multihome=0.0.0.0 and that did not fix it for me.

4 minutes ago, ich777 said:

Set the network as mentioned here:

 

Yes, i changed to Host

 

Command execution
docker run
  -d
  --name='Satisfactory'
  --net='host'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="Satisfactory"
  -e 'GAME_ID'='1690800'
  -e 'UDP_PORT_7777'='7777'
  -e 'GAME_PARAMS'='-log
  -unattended'
  -e 'VALIDATE'=''
  -e 'UID'='99'
  -e 'GID'='100'
  -e 'UMASK'='0000'
  -e 'USERNAME'=''
  -e 'PASSWRD'=''
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/satisfactory.png'
  -v '/mnt/user/appdata/steamcmd':'/serverdata/steamcmd':'rw'
  -v '/mnt/cache_doc/appdata/satisfactory':'/serverdata/serverfiles':'rw'
  --restart=unless-stopped 'ich777/steamcmd:satisfactory'
da8788fdafcd7620ca82fd393b03797819c0a7512ccd002e1a42f0e4402b79d2

The command finished successfully!

 

Im still getting the "Failed to connect to the Server API"

1 minute ago, emub said:

My network is br2 and I removed -multihome=0.0.0.0 and that did not fix it for me.

My network is br0 with local ip 192.168.0.51, I deleted -multihome=0.0.0.0 and it still has the api error

 I changed to host and removed multi home and playing now.. They also posted a quick fix in the github but we can't do that one I don't believe.

43 minutes ago, ich777 said:

So the actual workaround for now is to either set the containers Network mode to Host or br0 (if you choose br0 give it a local IP address) and remove -multihome=0.0.0.0 from the EXTRA_PARAMS

This worked for me (network mode = host). Another player succesfully connected to me as well. Thanks!

Hi,

the main Problem is the TCP 7777.

I use wireshark to trace this.

The server answer the syn with a rst.

 

I add a new port TCP 7777 and restart the server.

But it didn't work. And they doesn't show Container Port.

 

And yes, I use every dedicated server with "host" an an own ip address.

And -multihome=0.0.0.0 is removed.

 

edit. Client and unraid are in the same network.

Edited September 10, 20242 yr by AK20000

The main reason is that it won't work is because they bind the API to the 127.0.0.1 and that's why it's not working:

 

TCP is now used for the API which won't work unless you set the network host.

If it still is not working when you are setting it to host then something else is going on.

 

You also have to remove -multihost from GAME_PARAMS to get it to work.

 

They have to fix that it doesn't listens on 127.0.0.1 instead it has to be 0.0.0.0 and from what I saw they already working on that but it will take them one or two days.

Ok, no problem. I can wait.

Thanks.

Best regards

Andreas

2 minutes ago, AK20000 said:

Ok, no problem. I can wait.

However the workaround with removing -multihome=0.0.0.0 and using Host network for the container should work fine.