Selune

Hi. I'm trying again to run an Atlas grid on our Debian 10 box, but without success (Curl 3/4 incompatibility ...). Has anyone succeeded in installing an Atlas server in a Docker container? (I'm not an expert for docker...) Rgs

That's true, even if it's a little more complicated in fact... The linux binary never really worked because it's requiring the unsecure 1.0.0 version of system SSL library, which is absolutely prohibited on every recent Linux distributions. The Atlas devs never fixed this. I've read in this forum some people succeded in making it work though, but nobody knows (not even themselves) how they did it. I like alot this game, and I really hope devs will get a look at this...

Has Grapeshot Games definitively buried the idea of a dedicated server for their game? That would be stupid : there are thousands of players waiting for it... The success of a game like ARK came from the base players' community, and not from the paid hosting companies !

So many weeks we are waiting for an usable Atlas server, we finally gave up and came back to ARK. I'll keep an eye sometimes to the dev bug fixes but no much more time to waste. Bye !

I confirm this critical issue even on Linux Debian (stable) : abnormal process cpu load activity (starting often at 25-30 %CPU, and later oftern around 98-104 %CPU, particularly when players connect to) We planned our community grid openning for the 17th of february. Should we delay it (again and again) ?

Hi. Quite same issue for me. I just have a 4 cores Xeon (64 GB RAM DDR4) and each process overflows each one core. I tried the fix l used for ARK some years ago, by raising file limit. But it changes nothing. In our case with this bug we won't be able to open more regions than freeport... if not fixed quickly our community will have to give up the idea of a private ATLAS server... that would be dramatic for us....

I know it was supposed to be, but Jat was then expecting some feedback from us about this fix

@Jatheish For your info (maybe this could help your dev team) it finally works for me. (I installed stretch deb compatible package libssl-1.0.2 and changed the Redis port to conform to my iptables) I'm doing further tests on process stability and moreover on save file corruption issue. I let you know

CentOS 7 has always shipped 1.0.1e and later. You can't run 1.0.0 on CentOS as it's been discontinued upstream by openssl and it is lacking fixes for the last X many high severity openssl vulnerabilities. Quite same problem on my Debian, but I can install backports packages to install ssl1.0.0 Anyway even with ssl1.0.0 it doesn't work for me... I really feel like sailing in full fog ...

It still doesn't run for me ... Same problem as before : server process seems ok, netstat shows right ports are listening, firewall opened to a wide ports range, I've even rebuilt the whole servergrid.json, and still no significant log or output (and the server doesn't appear in the steam servers' list ofc). Anyway I suspect my ssl libs (libcrypto) to be wrong. I'm checking at it right now Thanks for the update, @Jatheish

I'm using only one external IP. No particular firewall settings (I opened a wide range of ports both tcp and udp for testing purposes), nor NAT or other exotical stuff. I just tried to : $ sudo apt-get install libssl1.0.0/jessie-backports But no more success I'm sending you a mp with the infos. (Thanks for your help)

Ok I understand but why I can't even make the server appear on Steam servers list ? I think I have an issue that others here don't have...

I tried it and that's right : this script is awesome. Very complete and secure. And you're right about the atlas server : its binary has issues the script cannot fix by itself...

It doesn't work neither...

Could you please give us the result of this command ? apt list libcurl* And the content of your ShooterGame/Saved/Logs/ShooterGame.log Thank you