Skip to main content
news Version 0.9.0.0 Released (15th July 2026) - v0.9.0 - AASM comes to Linux, with critical backup fixes, the Genesis: Par…

Linux guide · AASM v0.9.0+

Install an ARK Ascended Server on Linux

Install the native AASM Linux app, verify the download and create your first managed ASA server.

Published · Updated by Cryptek · Estimated time: 35 minutes

Direct answer

Direct answer: Install AASM’s native Linux .tgz, launch ARK Server Manager in a 64-bit graphical session, then use Add New Server. AASM runs natively; it manages Studio Wildcard’s Windows-only ASA dedicated server through Proton/Wine and uses SteamCMD for game-server files.

AASM v0.9.0 is AASM’s first Linux release. The same archive includes Ark Ascended Server Manager and ASA RCON Manager. You do not run the Windows AASM executable through Wine, and you do not need to assemble a separate server-management script.

Before you start

  • 64-bit Linux with a graphical desktop session. Ubuntu 22.04+ or Debian 12+ is recommended.
  • 16 GB RAM minimum; 32 GB recommended when you plan to run multiple ASA servers.
  • A modern quad-core CPU or better and SSD storage with roughly 30 GB free per server, plus room for backups and updates.
  • A stable internet connection for the AASM archive, SteamCMD, game files and mods.
  • One AASM licence per machine. A 14-day trial is available if you are evaluating the Linux host.

Download the Linux archive from the official site

Download AASM v0.9.0 for Linux from arkascendedservermanager.com. The file is a .tgz archive; keep it in your Downloads folder until it has been verified.

Only use the download hosted on arkascendedservermanager.com. AASM does not require a third-party download mirror.

Verify the SHA-256 fingerprint

Open a terminal in the download folder and calculate the archive fingerprint. If your browser used a different filename, replace the example filename with the one you downloaded.

sha256sum v0.9.0.tgz

The result must match:

9aa34b7c0e3a2740491b684c9eaeaa1d5e9a7e1492062c4320b0bd7b34f4f9c7
Stop if the hashes differ. Delete the incomplete or unexpected file and download it again from the official download page.

Extract AASM inside your home folder

Use your file manager’s Extract Here action, or extract the archive from a terminal:

mkdir -p "$HOME/Applications/aasm"\ntar -xzf "$HOME/Downloads/v0.9.0.tgz" -C "$HOME/Applications/aasm"

Keep all extracted files together. Avoid system-owned locations such as /usr or /opt unless you have deliberately configured their ownership and permissions.

Allow the application to execute

Open the extracted folder. If double-clicking ARK Server Manager does nothing, right-click it, open Properties → Permissions, and enable Allow executing file as program.

You can also set the executable bit from a terminal opened in the extracted folder:

chmod +x "ARK Server Manager"

Launch native AASM for the first time

Double-click ARK Server Manager. On first launch AASM registers the Server Manager and RCON Manager in your applications menu with their icons.

Architecture check: AASM itself is a native Linux application. Proton/Wine is used for the ASA dedicated server binary, not for the AASM desktop interface.

AASM’s Linux data is stored under ~/.local/share/aasm and remains in place across in-app updates.

Create the ASA server

From the AASM dashboard, select Add New Server, then choose Install New Server. Give the server a clear name, choose a writable install directory on SSD storage, and continue through the wizard.

A SteamCMD console window opens while AASM downloads or updates the server. Let that process finish; the console closes automatically when the operation completes.

Do not install the live ASA server inside AASM’s application folder or inside ~/.local/share/aasm. Use a dedicated, writable server-data directory with enough room for game files, mods, staging data and backups.

Configure ports, backups and the first start

Review the server name, map, game port, query port, RCON port, passwords, backup location and restart schedule before the first start. Permit the required UDP/TCP ports in the Linux firewall and upstream router when players connect from outside your local network.

Start the server, wait for AASM to show it as ready, then connect with one test client. Create a manual backup after that first successful launch and confirm the backup file exists before enabling unattended maintenance.

Your Linux ASA server is managed by AASM

AASM is now installed natively, the ASA server files are managed through SteamCMD and Proton/Wine, and you have verified both a player connection and a first backup. Add remote Web UI access or a second clustered map only after this baseline is stable.