BarenAD Posted December 18, 2023 Report Share Posted December 18, 2023 (edited) Hello everyone!) I got a problem when creating my own server: "the server appears in the list of servers for a while and disappears, but it works all the time". Environment: This is dedicated server placed in my home. I have white IP. But global routing goes to the router and then the local network with port forwarding. But all traffic goes to the server by default. (So IP server don't filled because server haven't this global interface) The main OS on the server is centos-7. The server itself is located inside a docker container where centos-7 is also located. (linux) The port is selected by default 42420. It's open. The route to the container is configured. Friends connect and play successfully. server version: 1.18.15 I sees similar posts from other people but none of them contains a solution. Here they are: https://github.com/anegostudios/VintageStory-Issues/issues/526 https://github.com/anegostudios/VintageStory-Issues/issues/1665 (This says about other ports uses in server. Interesting. I opened this ports and routed ports to container. It didn't work.) https://www.vintagestory.at/forums/topic/5634-my-server-isnt-showing-up-on-the-server-list-i-added-the-ip-and-im-using-the-default-port Does anyone have any ideas? Maybe anybody knows more about the work of this part? How does it work? Does the server update statistics or does the master server poll after the initial initialization of the connection? Maybe reasons: Server think incorrect definition my server because server haven't IP inside configuration. (The server was not displayed if there were special characters inside the name. It was also not displayed in the game when using "/server config name" (now yse correct symbols )). Server use other ports / type protocol (udp?) for update stats which don't has opened and no route inside server. Edited December 18, 2023 by BarenAD hidden other link Link to comment Share on other sites More sharing options...
BarenAD Posted December 19, 2023 Author Report Share Posted December 19, 2023 I found the reason, I just needed to read the logs more carefully) Link to comment Share on other sites More sharing options...
Recommended Posts