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

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