Closed npmaile closed 3 years ago
This is the behavior on the client.
If you haven't already, could you try specifically using UDP for all ports?
Eg. -p 7777:7777/udp -p 15000:15000/udp -p 15777:15777/udp
EDIT: Updated the repository readme with this information, as I have confirmed it locally and this should be resolved by binding the UDP ports.
This has solved my problem Thanks for the help, and thanks for saving me from having to do this work myself!
Describe the bug When running the server, I am unable to connect to it from the game client.
To Reproduce Steps to reproduce the behavior:
docker create --name satisfactory --mount source=satisfactoryGame,target=/steamcmd/satisfactory --mount source=satisfactorySaves,target=/app/ -e "SATISFACTORY_START_MODE=0" -e -p 7777:7777 -p 15000:15000 -p 15777:15777 didstopia/satisfactory-server:latest
docker start satisfactory
Expected behavior An initiated connection between the game client and the server
Environment (please complete the following information):
Ubuntu 20.04.3 LTS
Version: 20.10.8
Additional context Server logs:
I have a firewall rule that opens all ports, so connectivity doesn't appear to be the issue. Also, I was able to connect with the client (but not start a game) when running the server on bare metal.