Multiple Restarts when trying to set up server and cant see server
Hi, Im trying to bring back my mod Devastation. Its been years since Ive run a server. I downloaded a clean game, did the patch, and added my mod exactly where it was before. When I run it, it looks, like it loads all the way. I don't see a heartbeat confirmed and then it will restart again and again. I am at a loss. Ive turn off the AV and think Ive opened port 28000 on my att router. Suggestions?
One common issue with older mods crashing is scripts that attempt to connect to websites/domains that no longer exist, so if you had a web connector script in the past, it may need stripped out.
If it doesn't crash, it's likely a problem with the restarter.
Assuming you're starting it with ispawn, what command line are you sending it? Something like this? Does it receive the correct port, matching the one in your mod prefs? What's the last message you see when the server loads?
Ispawn performs queries locally to see if the server is responding every few seconds, so if the server takes a little too long to start up, it can prematurely restart it in some configurations I can provide you with a modified, more lenient, version if you think this is your issue.
You might try shutting off the fwall for the test duration as well as dmz the ip of the server in the rooter to see if you get anywhere. If so then set the rooter to dmz the server ip and enable the server fwall and try again. SAomewhere along the line you should find the blockage.
If you type echo($IPv4::InetAddress); it'll show the address that the master server should believe you're connecting from -- if this is not accurate for whatever reason (e.g. if you have multiple network adapters) you can try binding the server to a specific address with the $Host::BindAddress prefs variable. Leave it empty to unset it if you don't have a static address or don't know what it's used for.
In most cases however this is simply a case of the port either being unreachable or not routed to the host behind a nat. Assuming you're using the default, make sure you have port 28000 over UDP unblocked on your firewall, and have forwarded that same port to the correct host on your router.
Got challenge request
Sent challenge response
Connection request from: ip 192.168.1.74:58743
accepting connect... Client ID = 0
Sending accept: 2100
Got disconnect packet.
Client 2100 Disconnected.
Issuing Disconnect packet.
On the other computer, I see connecting. Then nothing happens and a UE
In most cases, the first attempt should show you the error description in the disconnect message on the client.
If both the client and the server use the same external address (check the address reported at http://master.tribesnext.com/whatismyip on the client machine matches the server address you're joining), you should be able to join from the internet, barring any additional routing or network issues preventing it.
Otherwise, it's really recommended when playing on your local network to connect to the LAN address. For this to work without the external IPs matching, if your client is connecting from 192.168.1.74, the server address you're attempting to connect to must also be within the 192.168.0.0/16 range, or else the script will think there's an attack attempt.
Which addresses are you actually connecting to in each failed attempt? Have you tried using queryLanServers(28000); with the server list open to send a broadcast ping within your network?
The address you should in almost every case use yourself to connect/ping the server, within your LAN, is the server's LAN address (192.168.x.x).