1.0 API Connection Issue (FIX INSIDE)

[wolveix]

STATUS

IT WORKS 🎉

You shouldn't have any issues with the latest docker image. Available via the tags below:

• latest
• dev
• v1.8.0
• v1.8
• v1.7.3
• v1.7

You also need to ensure that BOTH ports 7777/udp AND 7777/tcp are port forwarded etc. You do not need ANY other ports.

If you see issues about the port binding in the log file, Coffee Stain confirmed to me that these messages are meaningless, please disregard them. The same goes for the certificate being self-signed. If you're getting a certificate key missing error when trying to join, make sure you've added the server through the in-game - server manager FIRST.

If you're unsure, please re-read the README before opening new issues. Every single person that has reported an issue since the fix went out either hadn't updated their Docker image, or were using the old Satisfactory ports.

Summary

I spoke with a Coffee Stain developer for a while and we troubleshooted together to figure out the issue. Essentially, there's an issue with how the TCP bind for the API disregards multihoming. You can reproduce the issue we see with the container by running it on baremetal with -multihome set to anything. No, we are not using -multihome within the container. Yes, this is an issue we need to wait for them to fix.

They've confirmed that the patch will be released in the next few days (week of September 9th)!

[chichi13]

Good Luck!

[wolveix]

Might have found the issue, hold tight!

[ikiris]

ok what did i miss? XD

[richardbenson]

Just in case you haven't seen it, I assume it's because of this:

LogHttpListener: Created new HttpListener on 127.0.0.1:7777

[wolveix]

No, it's not because of that.

The API binds to a random port right now, looking for a config flag for it

[wolveix]

You can get around the issue for now by running net=host for the container

https://docs.docker.com/engine/network/drivers/host/

[Fabricio20]

For those on docker-compose, that is network_mode: 'host', server works fine for me with this workaround.

[wolveix]

I'll continue searching for the flag, assuming CoffeeStain added one that is

[iceyy0044]

Can i somehow do that when iam using the docker image inside pterodactyl egg ? Or i need to wait for the author to fix it aswell ?

[Tctcl]

Can i somehow do that when iam using the docker image inside pterodactyl egg ? Or i need to wait for the author to fix it aswell ?

I'll fork the official egg and send a link in here for that

[iceyy0044]

Okay, thanks.

[ankemp]

You can get around the issue for now by running net=host for the container

https://docs.docker.com/engine/network/drivers/host/

Can't do this when you bind to a static IP on a different subnet, ideally we can configure the port manually.

[megamertag]

by any chance, i deployed it on a truenas scale instance custom app, how do i change the network mode, if somehow someone know that

[dbaje]

The network host workaround is not a one size fits all solution. If you are forwarding requests from one server to another, that's also an issue.

[dbaje]

by any chance, i deployed it on a truenas scale instance custom app, how do i change the network mode, if somehow someone know that

You can't. One way to do it in scale, is to bind your container to the network bridge so it can get an IP address and then you connect to that IP.