nachopants

Have patched and updated, server found in list, select it, hit connect, connection time's out on attempting to join. Firewall is off.

I'll take that as a yes How STUPID though, to break the entire linux stack by not releasing parallel updates, come on guys, how the hell are we supposed to support this game and build a community when you show us no respect what-so-ever. We are spending hours trying to do your debugging for you, and you don't even give us the respect of professional communication.

Sigh, so it's all broken again today. Linux updated to 18.12 which seems to be the latest available, Windows 18.15, and the Clients at 18.11 can't connect to linux. Can anyone else verify?

I have attempted three, none of these alternatives appears to honour the ports set either in the command line, or the json file neither working $ ./ShooterGameServer Ocean -GridConfig=../../ServerGrid.json $ ./ShooterGameServer Ocean -GridConfig=/usr/atlas/ShooterGame/ServerGrid.json $ ./ShooterGameServer Ocean?ServerX=0?ServerY=0?QueryPort=27001?Port=7001?SeamlessIP=x.x.x.x -log -server -NoBattlEye -GridConfig=/usr/atlas/ShooterGame/ServerGrid.json Where x.x.x.x is replaced by my server's external IP address.

Hi mate, Thank you for your help but if you take a second look at my console output, there is no Signal 11 error. I'm raising an entirely new issue I think. I do indeed delete the entirety of the Saved directory on server start, I receive no signal 11 error, the log states the server has started successfully. However, strangely, I get port 30000 open and the server sits there chewing resources, unable to connect. Port 30000 is not mentioned in any json file, nor the launch command. Strange. Also I should add, just to make sure I wasn't making any glaring errors here, I configured a Windows instance yesterday with the exact same process I am using with the grid editor, json files, redis configuration and so on. On Windows, it worked flawlessly, so I'm confident the Linux and Windows binaries simply behave differently with identical configs. (with adjustments only to pathing, /home/atlas/ShooterGame vs c:\atlas\ShooterGame etc)

Spent today trying to get this running, no luck. Ubuntu 14.04.5 Steamcmd installed correctly, Atlas installed correctly. Have attempted a 1x1 and 2x2 grid. Have used a remote redis instance as defined in ServerGrid.ServerOnly.json Service boots with: atlas@ip-10-0-1-243:~/ShooterGame/Binaries/Linux$ ./ShooterGameServer Ocean -GridConfig=/home/atlas/ShooterGame/ServerGrid.json Using binned. 4.5.1-0+UE4 7038 3077 408 10 [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. Setting breakpad minidump AppID = 834910 It starts the services, uses a lot of cpu & memory and seems to stall here. It appears to ignore the ServerGrid.json configuration, the only port that becomes open is 'port 30000' (which I have not requested anywhere) I have also attempted defining the port in the launch command, this is also ignored. I can only get as far as a listening service open on port 30000 which I cannot connect to. Server does not become listed in Atlas directory.

Can confirm this is miles away from stable (or possible as best as I can tell) on AWS via the AWS Linux 2, Centos 7, or RHEL 7 operating systems. If this is only designed to work on Ubuntu with outdated openssl libraries, then say that, don't say "linux"