-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public browser listing shows the server but we arent able to connect. #15
Comments
setting MultiplayerManager failed: Host address is already in use. |
removing node port from the chart allowed me to configure this option
|
ping is still not showing and we are not able to connect to the server. |
firewall logs, everything looks to be routing fine and the ip is routable externally and can communicate back as per the logs.
|
The issue was related to a Nat rule not applying in the correct order. I was able to trace this down with the help of the factorio discord. Looking at the client log located in the appdata directory mentioned here |
How about use https://github.com/ZCube/factorio-port-fixer. According to https://www.factorio.com/blog/post/fff-143 it is the pingpong server that determines the initial port. Therefore, you can use the port you want by simply replacing that server. ( Currently port 34197 is fixed and port forwarding is required. ) It would be nice if hostAliases settings for pods were added. |
It looks like could use my https://github.com/MOZGIII/port-map-operator to solve the issues with NAT in this particular case, and use the |
The server now shows in public browser, however, when attempting to connect through the public browser you will get an error, the server is available on the web and allows inbound connections when connecting to the ip directly. This is due to the fact the outbound ports are randomized and because the server needs to reach out to update the browser with connection details and keepalive state on port 34197.
This is better explained by this writeup on serverfault;
If anyone has any ideas on how we can look to resolve this I would be happy to implement them.
The text was updated successfully, but these errors were encountered: