AASM Linux Troubleshooting Guide

Check the processor architecture and confirm you are inside a normal graphical desktop session:

The architecture should report x86_64. AASM is a desktop application; it is not designed to run as a headless system service over a shell-only session.

In the extracted folder, right-click ARK Server Manager, open Properties → Permissions, and enable Allow executing file as program. Or open a terminal in that folder and run:

Launching from the terminal keeps immediate startup output visible. Copy the exact error text if the application exits.

AASM must be able to write its own data directory and every managed server, backup and cluster directory. Check the important paths:

If your actual server path is elsewhere, check that location instead. Files copied from NTFS, a network share or another Linux account may belong to the wrong user.

ASA server installs, verification, mod downloads, backups and staged updates can temporarily need more space than the final server directory. Check memory and every relevant filesystem:

AASM requires 16 GB RAM at minimum and recommends 32 GB for multiple servers. Keep roughly 30 GB per ASA installation plus separate capacity for mods, backups, staging and SteamCMD working files.

A SteamCMD console opens while AASM installs, verifies or updates an ASA server. Do not close it while files are being processed. A large game or mod update can remain busy without visible movement in the AASM dashboard.

If the same operation repeatedly fails, record the final SteamCMD lines, confirm internet access and free space, and retry the operation from AASM after the failed console has closed. Do not start overlapping install or verify jobs against the same server directory.

That points to the managed server process rather than the native AASM interface. Confirm the server install or import points to the root containing ShooterGame, run a single update/verify operation, then review the map, launch arguments, ports and available RAM.

Let AASM manage the ASA server’s Proton/Wine environment. AASM itself should remain the native Linux app. Avoid introducing an unrelated global Wine prefix while diagnosing an AASM-managed server.

After a Windows-to-Linux migration, reselect every path that previously used a drive letter. Check server roots, backup folders, shared cluster data, SFTP keys, HTTPS certificates and any custom script or launch argument that contains a path.

Linux paths are case-sensitive. /home/simon/Ark and /home/simon/ark are different directories.

First confirm AASM shows the server as ready and test from the same local network. Then verify the configured game, query and RCON ports are not reused by another server.

Inspect listening sockets:

Allow the intended ports through the Linux firewall and forward the required game/query ports in the router for internet players. RCON and AASM’s Web UI should only be exposed according to your access and security plan; they are separate from the game port.

AASM’s Linux application data is stored under ~/.local/share/aasm. Server installations and backup directories may be elsewhere. Before reinstalling, record those locations and copy the data directory plus current world and cluster backups to a safe location.

If the issue remains, include the following in a support request:

• Linux distribution/version and desktop/session type
• AASM version and whether the failure affects AASM, SteamCMD or the ASA server process
• Exact timestamp, action and full error text
• Whether it is a clean install or Windows migration
• Available RAM and disk space
• Whether a simple unmodded test server starts
• Relevant AASM/SteamCMD log excerpt with passwords, tokens, public IP details and other secrets removed

Use the contact page or the official AASM Discord.