ADisorderlyFashion Posted August 22 Report Posted August 22 I'm currently having difficulty connecting to my own server. I have the default port, 42420, forwarded on both TCP asnd UDP, this is from a fresh download of the server files. I attempted the version which includes both the client and server binaries just in case that somehow resolved it, still nothing. The server itself isn't showing any errors, but there's a line I'll discuss later that I only saw while writing this that might be related. I don't have logs for the client I tried to connect to yet, but I will post those once I do. I'm testing connecting via a steam deck, so I'll need to grab the files from that and put it on the machine I'm using to post this. I also tried changing "Upnp" to "true" in the server config, no effect. Both devices are running Linux, the client SteamOS with Vintagestory installed via flatpak and the server is running on a personal device running Arch. The server is version 1.22.6. I'm aware 1.22.7 is out, but it's not out on flatpak, so I'm unable to test if the matter is resolved on 1.22.7. I saw somewhere that enabling advertising could resolve the issue, but I ran into the issue someone else had of not being able to connect to the master server. The error says that the port is not open. The only relevant information I saw in the server logs was the following line: [Server Event] Device with external ip 192.168.x.yy found, but this is a private ip! Might not be accessible. Created mapping for port 42420 anyway. I'm not sure if this was referring to the device trying to connect or the server itself, though. It only shows when I had advertising on. Regardless of everything I listed above, the client device doesn't ever show a visual error in the game itself. It simply stays on the loading screen until the connection eventually times out. I was unsure when I wrote this if I was meant to make a new thread about it or comment on the one I mentioned about the master server issue, because that is only one symptom of my problem and that thread hasn't had a comment since February, so it would almost certainly have been a necro-post. If I should comment anyway, I will delete this thread and post this as a comment there.
Chaneques Posted September 1 Report Posted September 1 The servers quite easy to setup, just ensure the server config has the right ports that you want to enable its setup as a default. Secondly ensure the router has the right ports enabled for port forwarding to the private ip address where the server is hosted you can find this by typing cmd and ipconfig. It will say 192.168. or 192. something. And third ensure windows firewall has the right ports enabled for incoming traffic..
ADisorderlyFashion Posted September 2 Author Report Posted September 2 On 9/1/2026 at 8:42 AM, Chaneques said: just ensure the server config has the right ports that you want to enable its setup as a default. Secondly ensure the router has the right ports enabled for port forwarding to the private ip address where the server is hosted The port is set to the default 42420, that port is open for the device's IP on the network. Quote And third ensure windows firewall has the right ports enabled for incoming traffic.. Quoting the post you replied to, "Both devices are running Linux."
Recommended Posts