Massif Sack Posted February 21 Report Posted February 21 Hiya! I've had a succeful server with my friends for a while now. A while back I upgraded my modum through my ISP, and ever since that happened my friends have not been able to connect to the server. Port forwarding and firewalls permission are all set up properly like they should. I have both been checking with my friends and port-checker websites constantly, but everything I've tried is not working. I also run servers for other games which all work perfectly fine, the only problem is VS. I also tried setting up an entirely fresh server, but this one is also inaccessible. I've tried just about anything at this point, such as a full reinstall, giving the .exe full permissions in my firewall, checked every setting of my modum in its firewall or port forwarding/triggering, using a different port, etc.. I regularly use other servers on this machine, and even set up a little TCP ping server on 42420 which worked perfectly fine. It's been a while (over a year) since we last played, so I'm wondering if anything happened in "recent" updates. Is there something I'm overlooking? Let me know if there's additional information you need from me to come to a conclusion, and thanks in advance for your help :)
Zane Mordien Posted February 21 Report Posted February 21 (edited) 5 hours ago, Massif Sack said: Hiya! I've had a succeful server with my friends for a while now. A while back I upgraded my modum through my ISP, and ever since that happened my friends have not been able to connect to the server. Port forwarding and firewalls permission are all set up properly like they should. I have both been checking with my friends and port-checker websites constantly, but everything I've tried is not working. I also run servers for other games which all work perfectly fine, the only problem is VS. I also tried setting up an entirely fresh server, but this one is also inaccessible. I've tried just about anything at this point, such as a full reinstall, giving the .exe full permissions in my firewall, checked every setting of my modum in its firewall or port forwarding/triggering, using a different port, etc.. I regularly use other servers on this machine, and even set up a little TCP ping server on 42420 which worked perfectly fine. It's been a while (over a year) since we last played, so I'm wondering if anything happened in "recent" updates. Is there something I'm overlooking? Let me know if there's additional information you need from me to come to a conclusion, and thanks in advance for your help //media.invisioncic.com/r268468/emoticons/smile.png Can you not connect or is it refusing connection? The whitelist is turned on by default as of about a year ago in 1.21 I think. If you haven't played since the whitelist was defaulted to on then that could be the problem. If the whitelist is the problem then you need to do one of these things: add yourself to the whitelist in the console commands, add yourself manually to the white list file, or turn off the whitelist in the serverconfig file. I've had issues turning if off in the serverconfig sometimes so that may not always work. Edited February 21 by Zane Mordien
Massif Sack Posted February 21 Author Report Posted February 21 34 minutes ago, Zane Mordien said: Can you not connect or is it refusing connection? The whitelist is turned on by default as of about a year ago in 1.21 I think. If you haven't played since the whitelist was defaulted to on then that could be the problem. If the whitelist is the problem then you need to do one of these things: add yourself to the whitelist in the console commands, add yourself manually to the white list file, or turn off the whitelist in the serverconfig file. I've had issues turning if off in the serverconfig sometimes so that may not always work. Sadly not the case. The error message from the connecting party is that they're unable to connect due to a timeout for a response (the same one you get when you don't port forward). The server also does not log anything when they try to connect, meaning that the connection request does not even reach the server, or something within the server itself is broken.
Zane Mordien Posted February 22 Report Posted February 22 1 hour ago, Massif Sack said: Sadly not the case. The error message from the connecting party is that they're unable to connect due to a timeout for a response (the same one you get when you don't port forward). The server also does not log anything when they try to connect, meaning that the connection request does not even reach the server, or something within the server itself is broken. I've definatly had similiar problems after I changed or updated my server install. Drove me crazy until I figured out whatever small error was not allowing it to work. Sounds like you're using the base port 42420 so you don't need to change the port in the serverconfig. The log files say it is booted up properly I assume? Can you connect inside the network? Are you running the server through Pterodactyl, virtual machine, docker container, etc...? I mainly use Pterodactyl and as a App in TrueNas.
Massif Sack Posted February 22 Author Report Posted February 22 16 hours ago, Zane Mordien said: I've definatly had similiar problems after I changed or updated my server install. Drove me crazy until I figured out whatever small error was not allowing it to work. Sounds like you're using the base port 42420 so you don't need to change the port in the serverconfig. The log files say it is booted up properly I assume? Can you connect inside the network? Are you running the server through Pterodactyl, virtual machine, docker container, etc...? I mainly use Pterodactyl and as a App in TrueNas. Haha yea I'm going insane trying to figure out what the problem is. It uses the normal 42420 and boots up perfectly fine. I can connect and play within the network, only external connections struggle. I'm not using a VM or docker, the setup is as simple as it gets (probably bad practice, but didn't want to go through the effort).
Zane Mordien Posted February 22 Report Posted February 22 @Massif Sack It sounds stupid maybe, but have you tried a different port for VS just to see? If your other games are working with the port forwarding it's hard to understand why VS isn't.
Massif Sack Posted February 22 Author Report Posted February 22 57 minutes ago, Zane Mordien said: @Massif Sack It sounds stupid maybe, but have you tried a different port for VS just to see? If your other games are working with the port forwarding it's hard to understand why VS isn't. It's one of the things I tried when I started getting desperate. No difference sadly (used port 12345)
Zane Mordien Posted February 22 Report Posted February 22 7 minutes ago, Massif Sack said: It's one of the things I tried when I started getting desperate. No difference sadly (used port 12345) I'm running out of ideas. Whenever this has happened to me I end up having an issue with the serverconfig file somehow. Other than that it's the lame port forwarding issue, but you have other servers that run so it seems like you understand port forwarding on your router. Did you set the port in the serverconfig when you made the change? Have you tried putting the IP address in the server config file? "ServerName": "Vintage Story Server", "ServerUrl": null, "ServerDescription": null, "WelcomeMessage": "Welcome {0}, may you survive well and prosper", "Ip": null, "Port": 42420, "Upnp": false, "UpnpInfiniteLifetime": false, "CompressPackets": true,
Massif Sack Posted February 23 Author Report Posted February 23 18 hours ago, Zane Mordien said: I'm running out of ideas. Whenever this has happened to me I end up having an issue with the serverconfig file somehow. Other than that it's the lame port forwarding issue, but you have other servers that run so it seems like you understand port forwarding on your router. Did you set the port in the serverconfig when you made the change? Have you tried putting the IP address in the server config file? "ServerName": "Vintage Story Server", "ServerUrl": null, "ServerDescription": null, "WelcomeMessage": "Welcome {0}, may you survive well and prosper", "Ip": null, "Port": 42420, "Upnp": false, "UpnpInfiniteLifetime": false, "CompressPackets": true, Yes I did change the Port setting in the JSON. When it comes to the IP setting, I'm not entirely sure how it works, but I tried both my external IP and internal device IP and neither makes a difference.
Recommended Posts