After Satisfactory 1.0 update dedicated server no longer properly works. Seems like they changed path to where the server executable is.

 

text  error  warn  system  array  login  


Session terminated, killing shell...kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
---Ensuring UID: 99 matches user---
---Ensuring GID: 100 matches user---
---Setting umask to 0000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
Logging directory: '/serverdata/serverfiles/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1721172922
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
Logging directory: '/serverdata/serverfiles/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1721172922
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x11) preallocating, progress: 58.69 (2525713987 / 4303569976)
 Update state (0x61) downloading, progress: 1.82 (78382436 / 4303569976)
 Update state (0x61) downloading, progress: 11.33 (487585113 / 4303569976)
 Update state (0x61) downloading, progress: 19.83 (853393384 / 4303569976)
 Update state (0x61) downloading, progress: 27.73 (1193532405 / 4303569976)
 Update state (0x61) downloading, progress: 35.17 (1513580138 / 4303569976)
 Update state (0x61) downloading, progress: 43.03 (1851753897 / 4303569976)
 Update state (0x61) downloading, progress: 52.78 (2271533645 / 4303569976)
 Update state (0x61) downloading, progress: 61.31 (2638638782 / 4303569976)
 Update state (0x61) downloading, progress: 68.87 (2963705013 / 4303569976)
 Update state (0x61) downloading, progress: 76.87 (3308171801 / 4303569976)
 Update state (0x61) downloading, progress: 80.65 (3470865316 / 4303569976)
 Update state (0x61) downloading, progress: 84.09 (3618796115 / 4303569976)
 Update state (0x61) downloading, progress: 87.46 (3763761350 / 4303569976)
 Update state (0x61) downloading, progress: 90.86 (3910237774 / 4303569976)
 Update state (0x61) downloading, progress: 94.89 (4083866316 / 4303569976)
 Update state (0x61) downloading, progress: 98.45 (4236766874 / 4303569976)
 Update state (0x81) verifying update, progress: 2.84 (122295288 / 4303569976)
 Update state (0x81) verifying update, progress: 18.06 (777267739 / 4303569976)
 Update state (0x81) verifying update, progress: 26.95 (1159925598 / 4303569976)
 Update state (0x81) verifying update, progress: 42.01 (1807817528 / 4303569976)
 Update state (0x81) verifying update, progress: 58.89 (2534476195 / 4303569976)
 Update state (0x81) verifying update, progress: 72.91 (3137534577 / 4303569976)
 Update state (0x81) verifying update, progress: 86.41 (3718897946 / 4303569976)
Success! App '1690800' fully installed.
---Prepare Server---
---Server ready---
---Start Server---
--ERROR: Couldn't find a game executable, something went probably wrong with the download!---

** Press ANY KEY to close this window ** 

 

Satisfactory 1.0 was released however the game executable has been renamed in the latest release.

 

---Start Server---
--ERROR: Couldn't find a game executable, something went probably wrong with the download!---

12 minutes ago, saskiuhia said:

After Satisfactory 1.0 update dedicated server no longer properly works. Seems like they changed path to where the server executable is.

4 minutes ago, emub said:

Satisfactory 1.0 was released however the game executable has been renamed in the latest release.

I just pushed an update, please update the container itself.

 

You also have to add the port 7777 TCP like this in the template:

 

and you can delete those ports from the template:

15 minutes ago, ich777 said:

I just pushed an update, please update the container itself.

 

You also have to add the port 7777 TCP like this in the template:

 

and you can delete those ports from the template:

I tried this and also updated the container and while in-game, trying to connect to the server, I am getting an API error

1 minute ago, spotopolis said:

I tried this and also updated the container and while in-game, trying to connect to the server, I am getting an API error

What port are you using to connect?

Trying to connect on 7777

Thanks for updating the container straight away, really appreciate it!

 

I am however also receiving the API failure.

 

 

Using the following setup (ports 7777, 157777, and 150000 are all opened on the router):

 

 

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, 20241 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"