4 minutes ago, ich777 said:

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

Hey ich, so just to make sure, br0 should NOT work at the moment? And would require coffee stain to correct the loopback issue? Thank you.

6 minutes ago, ich777 said:

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

Not on my side.

 

1 minute ago, Kegath said:

Hey ich, so just to make sure, br0 should NOT work at the moment? And would require coffee stain to correct the loopback issue? Thank you.

I'm not 100% sure with br0 but it could be the case that it won't work, I just tested host network and it works fine over here.

 

Yes this is something that CoffeeStain needs to fix because there is no documentation on how to change the listen address for the API (TCP port) and I don't think you can actually change that.

2 minutes ago, AK20000 said:

Not on my side.

 

What network did you use before? Did you use more than one NIC in your system?
A few users already confirmed that it's working with the workaround to remove multihome and use the host network (I already tested this over here and I'm also able to connect to the server).

Not sure if it will help anybody having the API issue with Satisfactory, but after switching to host and removing -multihome=0.0.0.0, I also had to hit force update for it to work on my end.

4 minutes ago, ich777 said:

I'm not 100% sure with br0 but it could be the case that it won't work, I just tested host network and it works fine over here.

 

Yes this is something that CoffeeStain needs to fix because there is no documentation on how to change the listen address for the API (TCP port) and I don't think you can actually change that.

My instance works on HOST, but not on br0 (server api error)

Edited September 10, 20242 yr by Kegath

Just now, Kegath said:

My instance works on HOST, but not on br0

Thanks for letting me know, so only host network and removing -multihome is the way to go for now until CoffeeStain releases a fix for that.

2 minutes ago, ich777 said:

Thanks for letting me know, so only host network and removing -multihome is the way to go for now until CoffeeStain releases a fix for that.

Not working for me either. I only have 1 nic in the system and before I was using a Custom network.

 

Now I have tried to delete the container and re-installed it again. Changed to Host and removed -multihome 0.0.0.0 from the Game Parameters:

 

 

 

Still not working tho

 

9 minutes ago, gevsan said:

Still not working tho

Maybe that's the culprit, was this custom network on a dedicated subnet?

Did you yet try to force an update from the container (enable Advanced View on the Docker page and click the blue text "force update"), maybe a rebuild from the container (which is what a force update does) is the solution to your issue.

 

Please also check the port forwarding since it will now use the IP from Unraid itself.

1 hour ago, Snappie88 said:

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

worked here as well. api error is resolved.

Anyone getting encryption token missing, or is it the same as the API error?

did the changes but still not working (host removed multihome.. + fresh docker install+force update)

the server is sort of running but i become ingame this message: "Could not connect to the server. Failed to connect to the Server API.

And the log say: (hope that help a bit ^^)

Edited September 10, 20242 yr by MaNs0n

For people whom the network=host work-around isn't working - it started to work for me once I changed the 'Network Protocol' to 'IPv4 + IPv6' under Settings->Network Settings.

 

 

17 minutes ago, zTemmu said:

For people whom the network=host work-around isn't working - it started to work for me once I changed the 'Network Protocol' to 'IPv4 + IPv6' under Settings->Network Settings.

 

 

Thanks! this helped for me

 

and thanks to ich777 for all the nice Docker!

19 minutes ago, zTemmu said:

For people whom the network=host work-around isn't working - it started to work for me once I changed the 'Network Protocol' to 'IPv4 + IPv6' under Settings->Network Settings.

This is strange I'm using IPv4 only and it is working here to.

I have to say that I'm also using ipvlan for Docker, no Bond and the default Bridge in the network settings.

40 minutes ago, ich777 said:

This is strange I'm using IPv4 only and it is working here to.

I have to say that I'm also using ipvlan for Docker, no Bond and the default Bridge in the network settings.

I am also only IPv4 and it's working.

Side note I use DiscordGSM (docker) and it's not able to query Satisfactory. Not an ich777 Docker issue just thought I would mention

 

49 minutes ago, bbreau6 said:

Side note I use DiscordGSM (docker) and it's not able to query Satisfactory.

Since the container uses now the host network you have to enable "Host access to custom networks" in the Docker settings, this is disabled by default and your containers can't actually communicate if they are in a custom network with the host:

(at least that's the issue in your case I think)

Can't test atm, but looks like there was a workaround found that doesn't involve using the host network:

https://github.com/wolveix/satisfactory-server/commit/59f700d605672b06669b06572583b441e07a7255

6 hours ago, Snappie88 said:

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

Having issues with other player timing out, had to update my port forward for 7777 to TCP and he was able to see the server but now can't connect. Not sure if this is docker related though

Edit: Verified game files and fixed.

Edited September 10, 20242 yr by Byrd

1 hour ago, ahal said:

Can't test atm, but looks like there was a workaround found that doesn't involve using the host network:

https://github.com/wolveix/satisfactory-server/commit/59f700d605672b06669b06572583b441e07a7255

I confirm this fixed the issue for me. So basically set:

 

GAME_PARAMS=-log -unattended -ini:Engine:[HTTPServer.Listeners]:DefaultBindAddress=any

This is in addition to the other fixes ich777 mentioned earlier, namely exposing port 7777 for both TCP and UDP (and making sure both are port forwarded in your router and removing the other two ports.

With those in place, no need to use the `host` network. In the previously linked Github thread, apparently a proper patch to fix this issue is expected to drop tomorrow.

Edited September 11, 20242 yr by ahal

Ich77 - thanks for the great plugin.  I've been using it for a long time without a hitch.  Unfortunately, even after following today's posts on the topic, I'm still having issues (for me it's still the --ERROR: Couldn't find a game executable, something went probably wrong with the download!---).  I've updated the container, then removed it and reinstalled it multiple times all with the same result.  I went as far as uninstalling the container, rebooting the server, and reinstalling, just in case that would have helped.  Any idea what I should do to fix it?   Thanks!

 

 

Satisfactory Error.txt

29 minutes ago, Trinacria said:

Ich77 - thanks for the great plugin.  I've been using it for a long time without a hitch.  Unfortunately, even after following today's posts on the topic, I'm still having issues (for me it's still the --ERROR: Couldn't find a game executable, something went probably wrong with the download!---).  I've updated the container, then removed it and reinstalled it multiple times all with the same result.  I went as far as uninstalling the container, rebooting the server, and reinstalling, just in case that would have helped.  Any idea what I should do to fix it?   Thanks!

 

 

Satisfactory Error.txt 1.4 kB · 0 downloads

Nevermind.  Got it sorted.  I uninstalled the container, deleted the Satisfactory directory from appdata, then reinstalled the container.  At that point, the server appeared online in the game, but I got the API error.  After that I followed the previous suggestion to enable IPv4 + IPv6 and that fixed it all for me.  Again, thanks for all the hard work!

@spotopolis, @Snappie88, @Jerky_san, @cybersteel8, @bbreau6, @gevsan, @rickyh, @emub. @Kegath, @AK20000, @rocklord2004, @Skwerls, @Torbjorn, @MaNs0n, @zTemmu, @ahal, @Byrd, @Trinacria

 

The Satisfactory container is now fixed and will work regardless if you are using bridge, br0, host,... network.

 

Just makes sure if this an existing installation to click force update on the Docker page (with advanced view enabled), remove multihome from GAME_PARAMS, create a new port entry with container port and host set to 7777 with protocol TCP.

 

For new installations everything will work right OOB.

 

 

 

 

In game screenshot:

Hey @ich777, thank you for working tirelessly on that issue yesterday! Do you, by any chance, have a Kofi or any other page where we can send you a tip for your hard work?

 

Cheers!

7 minutes ago, 6.9 said:

Hey @ich777, thank you for working tirelessly on that issue yesterday! Do you, by any chance, have a Kofi or any other page where we can send you a tip for your hard work?

No worries, I'm really glad that it is now "fixed".

Sure, in the first post from this thread or in the CA App on every application you got installed from me.