micah68ph

I think it was initially. But Ark added an option in the in-game server browser for "LAN Servers" I think. That's also where the MultiHome setting came from. I ran an Ark server for a bit and when I added MultiHome to the startup script settings it started working fine. Lame that Atlas isn't working the same way.

yeah

So lame. I have a dedicated server with 128GB RAM, 20x 2.2Ghz cores and fiber internet. All my buddies are connected and able to play and I can't join them and official servers are toxic or broken.

I think it's in the bat file that launches the server

I tried that but still no luck. Nothing changed on the Atlas side. I could ping the public IP, but it didn't change that the server never showed up in steam favorites by public IP and never showed up in-game server browser for me.

Yes. In the multi-grid examples I've seen each one gets a unique rcon number

I think you have to pick one of the island types that already has a Freeport.

Yep. I ran steamcmd and saw it happen again. The more you knowwwww!

Alrighty, I've gotten some tips from folks in other threads but I'm gonna start a new one in an attempt to cover all my bases. I'm successfully hosting a 3x3 Atlas server on a dedicated physical server. Folks are able to connect via the steam favorites and in-game server browser. I, however, cannot connect from my gaming PC on the LAN. This is my startup script for each of the 9 server instances (obviously tweaked for serverx/y and ports). Some people swear this "just works" for them after they add MultiHome but no luck for me. I tried adding a loopback adapter to my public IP and that didn't change anything. I have never seen my server in the in-game server browser. I can however see it when I add it as 10.0.0.11:57561 in Steam Favorites. When I try to join through favorites though it kicks back that it can't query the server. I feel pretty confident this is a hairpinning issue and the problem is that I can't get the Atlas game client to allow me to host it publicly and connect locally at the same time. I see people have created LAN-only servers by setting all their IP's to just the private IP. I'm guessing if I do that then the folks outside the network won't see it anymore though. I also see some folks reported success by using high end routers in place of their ISP router so that they could unblock the hairpinning at the edge. I don't have a router for that right now though so that's not an option for me. Any ideas? Has anyone else been able to host a server for external access and also connect from a separate PC on their LAN?

Hey Gang, I'm having trouble cleanly patching my server. I'm hoping there is a script out there or some tips you all might have. I created a 3x3 grid with guidance from the following Youtube vid (https://www.youtube.com/watch?v=Sq7KvmGY9Iw). Aside from not being able to connect from the LAN it's working and friends can connect and play. In order to patch, I click the X or Ctrl+C on each of the server windows and then do the same on the Redis window. Then I run SteamCMD to patch the server, and when it's done run my batch file to spin it all up again. The problem though is that every time I do this, it seems like redis-server.exe doesn't actually shut down. I get errors as soon as the game servers start up and when I start poking around I see that redis-server.exe is still running in task manager so it isn't starting up fresh. I cant' kill it in task manager. I've spent hours trying various elevated command prompt or powershell commands to kill it and it just won't die. So I reboot my physical server, run the batch file to start the game server and it works. I don't want to reboot my physical server every time I patch the game server. There's gotta be something I'm missing here. Any tips on how to cleanly shut down, patch and restart the game servers without bouncing the hardware/OS level?

Interesting. After patching this morning, my ServerGrid.json did not have any of the DB connection strings in them anymore so I'm manually adding those back. It also changed the password in my redis.conf file back to 'foobared' so I had to reset that. It was working fine when I went to sleep last night so I know I hadn't made any other changes. I shut down the server, patched via SteamCMD, started back up and started getting errors.

And now that the server is patched it's crashing with no other changes having been made. sigh.

Oh gotcha. I'll ignore that as a data point then.

Thanks for the suggestion @Teach. I had tried that as well but no luck. Could ping the public IP at that point but nothing changed on the Atlas side. I'm wondering if there is something lower level I'm missing. I've never seen my server in my in-game browser, nor the LAN tab in Steam and only ever saw the server show up active when I added it by internal IP on the Steam Favorites. I think you said you need to be able to connect from in-game server list so I'm trying to think down that route. I'm patching the server right now and hoping maybe it wasn't showing up because I was behind a minor version. Expecting it'll still error though.

So I'm in a similar boat to others who have a functioning server that people can get to, set multihome and still can't connect locally from another computer on the LAN. This is my startup bat file I was able to add it to favorites using the local IP and can view info on the server Connecting from there yields the following error, but it sounds like some of you are saying you shouldn't be able to connect this way anyhow I do NOT see it on the LAN tab And I do NOT see it in the in-game browser I don't have NAT acceleration on my CenturyLink modem/router. My eyes are starting to go blurry staring at suggestions and re-reading files so I'm hoping I'm just missing something simple. Any suggestions would be appreciated.

You shouldn't need a ? unless you are passing a new value for something