I have the dedicated server program up and going. Dispit the system being updated to current version and the few mods i had. I had it goibg and it worked fine but after i did a server restart after having it up for a few days. My server is now not showing itself even though i did not change no settings on my side. Im still scratching my head trying to figure this out. I could use some help with this issue please.
Can you direct connect to it?
A couple things could be happening:
It is just too soon after restart and the server hasnt registered with fls to show up in the list
Its a testlive server and you have to include the testlive steamid in the dedicated server launcher exe command line
Your ports somehow became unset to allow connections
It usualy shows up about 5 to 10 mins when I reactivate ut but ive let it gobfor about mins and it still does not show up
For the ports the loghts were green when i checked then and no issues for that
Have you tried direct connecting?
Yes i have still would not connect
Is the server on the same machine you are playing the client on, and if so, is multihome checked? Is it set to live branch? Are you inadvertently trying to connect with the public beta client instead of live (or vice versa)? Do you have battleeye checked and not using battleeye (or vice versa)?
Which mods?
When a server first starts, it goes through a bit of a boot process. New servers on somewhat decent hardware take no longer than 2-3 minutes to show up on the browser after a restart. Assuming no issues.
Servers having a ton of errors will take longer. Usually caused by mods that are either outdated, or in some rare cases they are replacing things they probably shouldn’t be touching, in which case they are doing so in ways the game doesn’t like or in conflict with other mods.
You can also have an issue with the database. Older databases of popular servers can reach gigabyte levels of memory space. These take longer to load up. But they should still load up consistently. If a database has a lot of errors, even if it is relatively small, it can take longer to boot up.
In some of these cases it takes them longer to contact the server browser server. Server checks in with the browser every minute. But this can be delayed by errors.
Best thing to do is check the server’s logs. A healthy server will just show a string of LogServerStats: Status report with one about every minute. With the occasional warning (if running mods). But that’s when its running.
On start up, you’re going to see a whole slew of warnings, most of which can be ignored. Unless of course they keep repeating and don’t stop. Then you can get an idea sometimes of which mod is causing the issue. Not always though.
If it is a mod issue, you will have to figure out which one it is. But usually looking at your mod list and seeing if any haven’t been updated since September is a good indicator (depending on what the mod is).
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.