7DTD - [Steamworks.NET] - Could not initialize GameServer

L

Louellay

New member
Hey.

I have an rented server for 7 Days to Die, and since i updated to Alpha 18 it seems that it won't let the players connect and its stuck on initializing.

When i tried to connect it, it had "Server is initializing, please wait" and it was stuck forever, then i looked at my server logs and saw this:

[steamworks.NET] Could not initialize GameServer

Anyone came across this issue? - Looking for help.

 
We are going to need more information.

What server provider do you use?

Have you attempted to contact them about this? This could be an issue where the server provider does not update the server to the newest version.

 
I have the same issue on an ubuntu box running from my home. Have tried a complete reinstall of both 7d2d via steamcmd. Have checked ports and firewalls. Have also tried a couple of different settings in config xml. Nothing seems to get it to connect to steamworks.

 
I have the same issue, also posted in the 'bugs' thread.

*** FIXED ***

see 2nd post below

export LD_LIBRARY_PATH=. in startup script.

 
Last edited by a moderator:
The wiki misses out a core detail. In your firewall, you need to allow Steam's servers to connect to your server. They use three random ports, so you'll need to monitor your network traffic and see the connections your server attempts to make once it's loaded the map. You can find the IP's here: https://bgp.he.net/AS32590#_prefixes

For my Ubuntu server hosted by Hetzner in Germany, the dedicated 7 Days To Die server tries to connect to this steam server: 162.254.196.84 so I allowed it through my firewall. If you have Ubuntu, I outlined what I did in order to find that IP: https://7daystodie.com/forums/showthread.php?127515-Ports-needed-for-Steamworks-NET

 
The problem is fixed on my server.

the following line was missing

export LD_LIBRARY_PATH=.

Look at the 'startserver.sh' script that is accompanied with the install.

For the past version of 7 Days it didn't seem to be necessary, but for the [A18] it does.

Hope it works for you as well.

 
Thank you Lambik for your answer, but i already had the following line.

The problem lays directly on providers, so i dm'd them and they solved the issue.

 
Wish I knew what your provider did to fix it, I'm having the same issue with my own linux server now
Click to expand...
Did you allow the Steamworks matchmaking server to connect to your server? It's not on the wiki, so you have to find it's IP manually.

 
Thank you for this thread. My server used a custom start script that did not include this export. As soon as I added the export line, it fixed the server start up. The other gotcha was to make sure SELinux was disabled.

 
Where do you add the export line? I can't find anything. I shut my server down to try and add some mods to it specifically:

farm2life

CrosshairGoneWhile Aiming

S420_SimpleUI-Compass

S420_SimpleUI-CraftingQueue

S420_SimpleUI--ForgeInput

S420_SimpleUI-LeftHUD-BuffTimers

When I went to start it back up it refused to initialize, when I removed all traces of all of the mods it continues to refuse to initialize. I'll gladly answer any questions you guys have.

I also have absolutely no idea where to put that export thing, I don't have a "startserver.sh"

Solved: For whatever reason when I shut down the dedicated server it didn't shutdown so therefore it was trying to use ports that were already in use. Found out when I opened task manager

 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top