Open goofball222 opened 2 months ago
Hey @goofball222! Sorry to hear that, could you try ghcr.io/wolveix/satisfactory-server:dev-301
and let me know if that addresses the issue for you, please?
Does not appear to be any change in state with that image:
root@satisfactory:/config# netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:7777 0.0.0.0:* LISTEN
tcp 0 0 172.17.0.3:59010 35.227.230.186:443 ESTABLISHED
tcp 0 0 172.17.0.3:38006 185.125.190.82:80 TIME_WAIT
tcp 0 0 172.17.0.3:38062 104.26.13.205:443 ESTABLISHED
tcp6 0 0 :::35469 :::* LISTEN
tcp6 0 0 2607:XXXX:XXXX:XXXX::55068 2620:2d:4000:1::101:80 TIME_WAIT
tcp6 0 0 2607:XXXX:XXXX:XXXX::55080 2620:2d:4000:1::101:80 TIME_WAIT
udp 0 0 0.0.0.0:7777 0.0.0.0:*
udp6 0 0 :::7778 :::*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 3 [ ] STREAM CONNECTED 116911191
unix 3 [ ] STREAM CONNECTED 116910130
unix 3 [ ] STREAM CONNECTED 116911190
unix 3 [ ] STREAM CONNECTED 116910131
root@satisfactory:/config# ps auxwww
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
steam 1 0.0 0.0 2892 760 ? Ss 18:05 0:00 /bin/sh /config/gamefiles/FactoryServer.sh -Port=7777 -ini:Engine:[HTTPServer.Listeners]:DefaultBindAddress=any -ini:Engine:[Core.Log]:LogNet=Error -ini:Engine:[Core.Log]:LogNetTraffic=Warning -ini:Engine:[/Script/FactoryGame.FGSaveSession]:mNumRotatingAutosaves=5 -ini:Engine:[/Script/Engine.GarbageCollectionSettings]:gc.MaxObjectsInEditor=2162688 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:LanServerMaxTickRate=30 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:NetServerMaxTickRate=30 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:ConnectionTimeout=30 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:InitialConnectTimeout=30 -ini:Engine:[ConsoleVariables]:wp.Runtime.EnableServerStreaming=1 -ini:Game:[/Script/Engine.GameSession]:ConnectionTimeout=30 -ini:Game:[/Script/Engine.GameSession]:InitialConnectTimeout=30 -ini:Game:[/Script/Engine.GameSession]:MaxPlayers=16 -ini:GameUserSettings:[/Script/Engine.GameSession]:MaxPlayers=16
steam 109 5.3 2.2 2953340 749940 ? Sl 18:06 0:25 /config/gamefiles/Engine/Binaries/Linux/FactoryServer-Linux-Shipping FactoryGame -Port=7777 -ini:Engine:[HTTPServer.Listeners]:DefaultBindAddress=any -ini:Engine:[Core.Log]:LogNet=Error -ini:Engine:[Core.Log]:LogNetTraffic=Warning -ini:Engine:[/Script/FactoryGame.FGSaveSession]:mNumRotatingAutosaves=5 -ini:Engine:[/Script/Engine.GarbageCollectionSettings]:gc.MaxObjectsInEditor=2162688 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:LanServerMaxTickRate=30 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:NetServerMaxTickRate=30 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:ConnectionTimeout=30 -ini:Engine:[/Script/OnlineSubsystemUtils.IpNetDriver]:InitialConnectTimeout=30 -ini:Engine:[ConsoleVariables]:wp.Runtime.EnableServerStreaming=1 -ini:Game:[/Script/Engine.GameSession]:ConnectionTimeout=30 -ini:Game:[/Script/Engine.GameSession]:InitialConnectTimeout=30 -ini:Game:[/Script/Engine.GameSession]:MaxPlayers=16 -ini:GameUserSettings:[/Script/Engine.GameSession]:MaxPlayers=16
root 423 1.0 0.0 7636 2940 pts/0 Ss 18:14 0:00 bash
root 431 0.0 0.0 10072 1368 pts/0 R+ 18:14 0:00 ps auxwww
docker inspect satisfactory
shows:
"Labels": {
<snip>
"org.opencontainers.image.ref.name": "ubuntu",
"org.opencontainers.image.version": "22.04",
"version": "vDEV-301"
}
so it's definitely running on the updated image.
Hm, that's strange. So, we removed multihome
entirely from this image, which is why SERVERIP
had no effect. We did this as Coffee Stain said it was no longer needed, as it should bind to all available interfaces.
dev-301
added it back to see whether it would make a difference, though clearly not. It seems others are heaving issues with IPv6 in the Satisfactory Discord server, so I suspect it's a bug with the new server unfortunately.
This is similar to the issue I encountered before. The Satisfactory server requires a UDP port for the game port and a TCP port for the API port. Actually, the server still listens on IPv6, but only on port UDP6/7778. However, the API port is not bound to an IPv6 address. Therefore, even if you connect to the game port in IPv6 format within the game, you will still be prompted with an API connection error. For Docker containers, this issue is unlikely to cause any impact. If systemd is used to manage the server, it can listen to requests on :::7777 and forward them to 127.0.0.1:7777.
(base) ovoovo@ubuntu:~$ netstat -tunlp | grep Factory
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:7777 0.0.0.0:* LISTEN 3269100/FactoryServ
tcp6 0 0 :::36429 :::* LISTEN 3269100/FactoryServ
udp 0 0 0.0.0.0:7777 0.0.0.0:* 3269100/FactoryServ
udp6 0 0 :::7778 :::* 3269100/FactoryServ
Not sure if this is a material change to the image, or something in the game server itself with 1.0. It appears the server process no longer listens internally on IPv6 regardless of the
SERVERIP
environment variable. This behavior continues even after the current 1.0 game hotfix and workaround removal from the image.Exec'd into running container & ran
apt update && apt install net-tools
to provide access to netstat -Container attached to docker default bridge network does have IPv6 connectivity and IPv6 global transit. IE: can
ping6 ipv6.google.com
ifinetutils-ping
is added to running container.Current docker-compose.yml