"SteamSocketOpenSource: gethostname failed ()" Server Issue

[Mantequilla]

I run a server from my own computer for me and one other friend to play on. I just made it yesterday and have made a server the same way in the past using SteamCMD. We are using the Crystal Isles map and my server start command line looks like this:

start ShooterGameServer.exe CrystalIsles?SessionName=MAD_cause_BAD?MaxPlayers=6?Port=7777?QueryPort=27015?ServerPassword=4234?ServerAdminPassword=4234

I have portforwarded both 7776-7778 and 27014-27016 ports. I launched the server the first time and it came up with this error:

"SteamSocketOpenSource: gethostname failed ()
gethostname failed ()

https://cdn.discordapp.com/attachments/285570297892175882/725209505893187604/unknown.png

Shortly after these messages the server launcher crashes before it finishes fully loading up the server. I am yet to find a fix for this, so anything that may fix it is appreciated.

[Toooni]

The only thing i can tell you is that your crash is not related to this "gethostname failed" message. You can ignore this message.
Thats some "feature" wildcard added with Crystal... it has no negative and no positive effect. All servers are seeing this.

Your crash is mostly related to any mods you have installed.

[Mantequilla]

Originally posted by Toooni:

The only thing i can tell you is that your crash is not related to this "gethostname failed" message. You can ignore this message.
Thats some "feature" wildcard added with Crystal... it has no negative and no positive effect. All servers are seeing this.

Your crash is mostly related to any mods you have installed.

I have tried my server with and without the mods installed or put into ActiveMods. It doesn't work 90% of the time and occasionally the server will launch. I really don't understand what could be the problem here....

[General Dolphin]

I've been having the same error over the last week since the most recent patch. Been looking at a lot of different posts to try to find a fix and seem to have found similar things to you - changing port forwarding etc. I wouldn't mind so much having the gethostname failed message pop up but the server was visible as a random name and no password despite both of these having been specified in ark server manager and although I could join the server on my machine (same computer) my friends could not (time out message).

Given the recent crossplay addition with Epic Games I thought maybe that was the problem so I enabled Vivox (- UseVivox) to make it Steam only. Although I am still getting the gethostname failed message my server ran perfectly with no issues including the correct server name and password. I also enabled RCON but I doubt that will have made a difference.

Perhaps try this and see if you get the same luck!

Dolph.

[Mantequilla]

Originally posted by General Dolphin:

I've been having the same error over the last week since the most recent patch. Been looking at a lot of different posts to try to find a fix and seem to have found similar things to you - changing port forwarding etc. I wouldn't mind so much having the gethostname failed message pop up but the server was visible as a random name and no password despite both of these having been specified in ark server manager and although I could join the server on my machine (same computer) my friends could not (time out message).

Given the recent crossplay addition with Epic Games I thought maybe that was the problem so I enabled Vivox (- UseVivox) to make it Steam only. Although I am still getting the gethostname failed message my server ran perfectly with no issues including the correct server name and password. I also enabled RCON but I doubt that will have made a difference.

Perhaps try this and see if you get the same luck!

Dolph.

Thanks a lot for recommending this fix to me. It worked for me too, thankfully. It is pretty misleading when the issues it shows in the command prompt isn't actually the problem.