Jump to content
Upcoming Ally Crew Count Patch Read more... ×

TruWrecks

Pathfinder
  • Content Count

    96
  • Joined

  • Last visited

Community Reputation

33 Excellent

About TruWrecks

  • Rank
    Landlubber

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for responding quickly. I'm not saying anything was done maliciously. I was just reporting what was found. I scanned the suspected file again with Malwarebytes and it was also positive for the same infection. The previous version has no false or otherwise flags for infection. The virus may have come from something else, but it is slim because I only download tools for running my server and the infection only showed up in the update to AutoUpdate utility. It also was the only download on the server in over a week so the options are few. -Tru
  2. After my server downloaded the 1.0.5 update Windows Defender found Trojan/Win32/Azden.A!d in the Updater Utility executable. I highly recommend everyone scan your files. I love this tool but this security issue needs to be resolved. -Tru
  3. This is an issue again. No beds are usable or visible if you die on my dedicated server. Build 4269067 on Windows Server 2016 and Windows 10 Pro 1903.
  4. This no longer works post server update to version 4269110 for Windows. All 4 server now try to save in a common directory named SavedArks. This started after the patch and reboot tonight. The servers are not updating or using the AltSaveDirectory locations at all right now. I have checked, double checked and rebuilt my server and the same issue persists. This is not a configuration issue that I can find. It was working. Now all my servers are down in this grid with the same problem. Server build: 4269067 OS version: Windows 10 Pro build 1903 running on Oracle VirtualBox on Debian Linux 10. Server is allocated 28 GB of RAM, 8 CPU cores and 50 GB of SSD storage. There are no resource issues. Running the latest SteamCMD distribution for Windows. I posted about this in the Bug section but no response.
  5. TruWrecks

    AltSaveDirectoryName doesn't work after update 4269110

    Does anyone know why this is happening? I'll post it in the Dedicated Server section also. If this is configuration I can't find anything that would cause it.
  6. TruWrecks

    AltSaveDirectoryName doesn't work after update 4269110

    Completely rebuild my server today with a new config and same problem. This is on a Windows Dedicated Server.
  7. TruWrecks

    AltSaveDirectoryName doesn't work after update 4269110

    This is one of my server launch batch files: @Echo off :Start C:\Steam\Servers\Atlas\ShooterGame\Binaries\Win64\ShooterGameServer.exe Ocean?ServerX=0?ServerY=0?AltSaveDirectoryName=A1?MaxPlayers=20?ReservedPlayerSlots=0?QueryPort=57550?Port=5750?SeamlessIP=x.x.x.x -log -server -NoBattlEye -ExclusiveJoin -ForceRespawnDinos echo Press Ctrl-C if you don't want to restart automatically ping -n 30 localhost goto Start The IP has been removed. This launch string was working perfectly yesterday afternoon.
  8. AltSaveDirectoryName=A1 AltSaveDirectoryName=B1 AltSaveDirectoryName=A2 AltSaveDirectoryName=B2 This no longer works post server update to version 4269110 for Windows. All 4 server now try to save in a common directory named SavedArks. This started after the patch and reboot tonight. The servers are not updating or using the AltSaveDirectory locations at all right now. I have checked, double checked and rebuilt my server and the same issue persists. This is not a configuration issue that I can find. It was working. Now all my servers are down in this grid with the same problem. Server build: 4269110 Version: 315.7 OS version: Windows 10 Pro build 1903 running on Oracle VirtualBox on Debian Linux 10. Server is allocated 28 GB of RAM, 8 CPU cores and 50 GB of SSD storage. There are no resource issues. Running the latest SteamCMD distribution for Windows.
  9. You mean you had to "downgrade" your server to Ubuntu to get around that error. The error caused by using an outdated and compromised OpenSSL-1.0.0 package in the Linux server build. Having been a recent hacking victim I'll pass on running a known compromised OpenSSL package on my servers.
  10. Unlikely since I've been bugging them about this since the launch of the Linux server.
  11. Or 3 weeks from tomorrow
  12. Exactly! Over a month of updates that are lagging behind the client in most cases by severe days, and refusing to update a HACKED version of OpenSSL. Yes OpenSSL-1.0.0 was HACKED over a year ago and that is why it is NOT RECOMMENDED! Why do you think I've been saying Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Update OpenSSL! Get it yet?
  13. I noticed there is a 1.7 GB update for the Linux server code. Time to find out if they updated OpenSSL and fixed the save game issues. OpenSSL - No /home/steam/Atlas/Server/ShooterGame/Binaries/Linux/ShooterGameServer: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory Save games I can't test because the servers won't start until OpenSSL is FIXED!
  14. I would love to run the server for myself. I would love it to just run and not be a server I need to devote several hours a day to keep it working smoothly.
×