How to Run an ARK: Survival Ascended Dedicated Server on Linux

Yes, you can host ASA on Linux, but not with a native Linux server executable. Studio Wildcard distributes the Windows dedicated-server depot, so a 64-bit Linux host must run ArkAscendedServer.exe through Proton or Wine. The practical choices are a managed Linux application such as ARK Ascended Server Manager (AASM), a Docker image that bundles SteamCMD and GE-Proton, or a manual SteamCMD installation supervised by systemd.

Prefer not to run the server on your own PC? Godlike.Host offers hosted ARK: Survival Evolved servers with free DDoS protection and up to three free backups a day.

This guide explains How to Run an ARK: Survival Ascended Dedicated Server on Linux, including hardware, ports, map identifiers, first launch, updates, backups, security and troubleshooting. It also clarifies which older ARK: Survival Evolved instructions are unsafe to copy when you set up an ASA dedicated server on Linux.

#	Preview	Product	Price
1		ARK: Survival Evolved Pins - Dodo	$11.99	Buy on Amazon
2		ARK: Survival Evolved Pins - Rex	$11.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

What Linux support actually means for ASA

ARK: Survival Ascended does not currently have a native Linux dedicated-server binary in the implementations covered here. The server files are Windows files, and Linux supplies the compatibility layer that runs them. AASM’s 2026 guide describes the arrangement plainly: “the ASA dedicated server binary from Studio Wildcard is Windows-only and is run through Proton/Wine.” The Docker documentation from ferment9348 makes the same distinction: “Wildcard ships no native Linux server binary, so this installs the Windows depot and runs ArkAscendedServer.exe under GE-Proton.”

That architecture has two practical consequences. First, the host operating system can be Linux while the game process remains a Windows executable. Second, instructions written for ARK: Survival Evolved (ASE) can contain the wrong executable names, map identifiers or launch syntax. Treat the official and community wiki pages as references, then verify every argument against ASA behavior before putting the server in service.

#1 Best Overall

ARK: Survival Evolved Pins - Dodo

• Official ARK: Survival Evolved licensed merchandise, featuring the Dodo sculpted in textured iron
• Compact pin measuring about 1.6 in (4 cm) across and 0.5 in (1.2 cm) thick - light enough for caps, denim and tote bags
• Raised, textured surface gives the design real depth instead of a flat printed look
• Made in Japan - the pin back attaches securely and sits flat without dragging the fabric down
• A gift for ARK players, survival game fans, and dinosaur enthusiasts

$11.99

Buy on Amazon

Choose an operating model

Pick the management approach before installing files. The game binary is the same Windows depot in each case; what changes is how SteamCMD, Proton, configuration, updates and recovery are handled.

AASM: the managed route

AASM is a native Linux management application rather than a replacement server binary. During setup it installs the ASA depot through SteamCMD, prepares a Proton or Wine prefix and gives you controls for maps, settings, updates, backups, schedules, Web UI access and RCON. The initial setup assumes a graphical Linux session. Once the server and Web UI are configured, the machine can run without a monitor.

This is the shortest path when you want routine tasks—restart windows, update cycles, backup jobs and remote administration—in one interface. Confirm the application’s current license terms before deployment, especially if you plan to operate several instances.

Docker and GE-Proton: the reproducible route

The cited Docker image downloads SteamCMD and GE-Proton when the container starts for the first time. Configuration is expressed as environment variables, which makes a deployment repeatable across hosts. Persist the server’s data location outside the disposable container layer so a rebuild does not remove saves, configuration or downloaded content.

The documented map value for The Island is TheIsland_WP, not the map spelling commonly seen in ASE examples. Set a distinct SERVER_NAME, the desired MAX_PLAYERS, any MODS list and the documented CROSSPLAY option before inviting players. Keep the image’s port mappings aligned with the host firewall and router.

Manual SteamCMD and systemd: the control route

Install SteamCMD on the 64-bit Linux host, download the ASA depot, and use Proton or Wine to launch the Windows executable. A systemd unit (or an equivalent service manager) can enforce start-on-boot, restart behavior, dependency ordering and log capture. This arrangement is flexible, but you must write or maintain the update, backup, validation and monitoring logic.

The official setup material mixes ASE and ASA examples. In particular, ASA uses -port=<port>; do not blindly copy the older ?port=<port> form. Check every other argument against current ASA documentation before adding it to a service file.

Prepare the Linux host

Use a supported 64-bit Linux distribution, a modern multi-core processor and SSD storage. ARK performs heavy random I/O while loading assets, writing saves and handling mods, so an SSD is preferable to a spinning disk.

Install system updates and your chosen container runtime or desktop components before downloading the game. Leave working space for a second copy during validation or an update, and ensure the service account can write saves, logs and backups without running the game as root.

Install the server and compatibility layer

1. Install SteamCMD or let your manager do it

AASM and the Docker image can manage SteamCMD for you. For a manual deployment, install SteamCMD using the package instructions for your distribution, create a dedicated ASA directory and download the Windows server depot there. Run validation after the first download and after any interrupted update.

Do not mix files from an ASE installation into the ASA directory. Keep one data path per instance so that maps, configuration, logs and backups cannot overwrite one another.

2. Create the Proton or Wine prefix

Start the executable through the compatibility layer selected by your management method. AASM creates and maintains the prefix automatically. The Docker image uses GE-Proton. With a manual service, define the prefix and working directory in the service environment so restarts use the same Windows-style installation rather than creating a fresh prefix.

The first launch can take longer while Proton initializes files and the server builds caches. Watch the service log instead of assuming that a quiet terminal means failure.

3. Apply the ASA launch syntax

Use the ASA form -port=<port> for the game port. The distinction from ASE’s ?port=<port> syntax is important: an otherwise healthy process can start without listening where you expect if you paste the wrong form. Add only arguments confirmed for ASA, and record the final command or manager settings so another administrator can reproduce them.

Open the network paths

A server that starts locally can still be unreachable from the Internet. Permit the selected ports in the Linux firewall, then forward the same ports through the home router or cloud security group to the Linux host. If you run more than one instance, assign each instance a non-conflicting port set.

For a host using UFW, the rules follow the same port and protocol values, for example:

• sudo ufw allow 7777/udp
• sudo ufw allow 7778/udp
• sudo ufw allow 27015/udp
• sudo ufw allow 27020/tcp only if RCON is required

Use equivalent firewalld or cloud-security-group rules when appropriate. Restrict RCON to a trusted management network instead of opening it to every Internet address. After applying rules, test from a client outside the host’s local network; a local test can succeed even when router forwarding is wrong.

Configure the ASA instance

Server identity and map

Give the instance a unique server name so players can distinguish it from other servers. Select an ASA map identifier, not an ASE label. For The Island, the Docker documentation uses TheIsland_WP. If you use another map, confirm its current ASA identifier in the release documentation for that map.

Rank #2

ARK: Survival Evolved Pins - Rex

• Official ARK: Survival Evolved licensed merchandise, featuring the Tyrannosaurus sculpted in textured iron
• Compact pin measuring about 1.6 in (4 cm) across and 0.5 in (1.2 cm) thick - light enough for caps, denim and tote bags
• Raised, textured surface gives the design real depth instead of a flat printed look
• Made in Japan - the pin back attaches securely and sits flat without dragging the fabric down
• A gift for ARK players, survival game fans, and dinosaur enthusiasts

$11.99

Buy on Amazon

Players, passwords and administration

Set the player limit deliberately. Configure the server password and administrator password before making the server public, and keep those credentials out of shell history, shared configuration repositories and public support logs. The Docker documentation warns that ARK writes passwords to ShooterGame.log in clear text. Treat log files as sensitive, restrict their permissions and rotate or archive them securely.

Mods and crossplay

Add mods through the manager’s mod field or the container’s MODS variable, using the syntax required by that implementation. Keep a written list of enabled mods and update them during a maintenance window; a changed mod set can increase startup time or prevent a save from loading. The Docker image exposes CROSSPLAY as a setting, so decide whether crossplay is needed and verify the resulting behavior with an external client.

Persistent data

Back up the save directory, configuration and any mod-related data before changing maps or applying a major update. In Docker, bind or otherwise persist the data directory outside the container lifecycle. In AASM or a manual service, identify the exact instance directory and include it in the backup job rather than backing up only the executable files.

Start the server and perform a first-connection test

1. Start the service from AASM, your container orchestration command or systemd.
2. Follow the live log until the process has finished loading the selected map and is listening on the configured ports.
3. From a client on an external network, connect using the server’s public address and query port where applicable.
4. Join with an administrator account, verify the player limit, test an administrative action and confirm that a save is created.
5. Stop and restart once to prove that the service returns to the same map, settings and save.

AASM recommends proving one external client connection before adding maps or building a cluster. That sequence isolates firewall, NAT, Proton and configuration problems while the installation is still simple.

Automate updates, restarts and backups

ASA needs routine maintenance because the Windows depot, Proton build, mods and configuration can change independently. Schedule updates during a published maintenance window, stop the server cleanly, validate files when an update is interrupted, then restart and test the external connection.

Plan daily or more frequent restarts according to your community’s tolerance for downtime. Keep rolling backups rather than a single latest copy, and periodically restore one to a separate test directory. Monitoring should check both the process and the network response; a process that exists but no longer answers queries needs attention.

LinuxGSM documents a useful operational pattern for its ARK workflow: commands for start, stop, restart, update, validate, backup and monitor, plus log viewing and cron scheduling. Its page is explicitly for ARK: Survival Evolved, so treat those command names as an automation model and verify ASA support before placing them in production. The project also recommends data-center hosting for consistent uptime; that is a hosting recommendation, not an ASA-specific performance test.

Secure the installation

• Run the service under a dedicated, unprivileged account.
• Allow only the game, peer, query and deliberately enabled RCON ports through the firewall.
• Restrict RCON by source address or private network whenever possible.
• Protect ShooterGame.log and backups because passwords may appear there in clear text.
• Keep SteamCMD, the container image, Proton build and Linux packages updated during maintenance windows.
• Document who can reach the Web UI, systemd controls or container socket.
• Test a restore before you need one; an untested backup is only an assumption.

Troubleshoot the common failure modes

The process starts but players cannot connect

Check that the server is listening on the intended ASA port, that UDP 7777 and 7778 are allowed on the host firewall, and that the router or cloud security group forwards them to the correct machine. Check UDP 27015 if a query or listing tool is the symptom. Test from outside the local network to rule out a hairpin-NAT limitation.

The executable exits immediately

Read the Proton or Wine log and the ASA server log, then confirm that the service uses the same prefix and working directory on every start. Verify the depot and run a file validation. A manual installation should also confirm that the service account can read the Windows files and write its save and log paths.

An update leaves the server in a broken state

Stop the instance, preserve the current save and logs, run the platform’s validation operation, and retry during the maintenance window. Do not delete the save directory as a first response. If the problem follows a mod update, restore the last known-good mod set and test the server before re-enabling changes one at a time.

The wrong map or settings load

Inspect the effective environment variables, manager profile or systemd command rather than editing a second configuration file. Confirm that the map uses an ASA identifier such as TheIsland_WP, and ensure only one instance is pointing at the save directory.

Memory or disk usage keeps climbing

Compare usage with the 16 GB baseline and the 32 GB recommendation for multiple servers or a full cluster. Check free SSD space against the 30–50 GB per-server allowance, then add room for saves, mods, staging files and rolling backups. Reduce the number of simultaneous instances or expand resources before the filesystem reaches capacity.

RCON works locally but not remotely

Confirm that TCP 27020 is enabled only where required, that the service is configured to use it, and that the firewall and cloud or router rule agree. If remote RCON is not essential, close the public rule and administer through a private network or the manager’s protected interface.

Expand to additional maps or a cluster

Do not add a second map until one instance has passed an external connection, restart, update and restore test. A cluster increases memory, disk and administrative load; AASM’s 32 GB figure is its recommendation for multiple ASA servers or a full cluster, not a guarantee for every mod combination.

Give each instance its own data directory, service identity, log path and non-conflicting ports. Apply updates in a controlled order, back up every instance before the change, and verify travel or shared-cluster behavior only after each individual server is healthy. Docker can reproduce additional containers, while AASM provides cluster-oriented management; manual systemd units offer the most control but require you to maintain those relationships yourself.

Which method should you use?

The essential decision is not Linux versus Windows; it is how much compatibility-layer and operations work you want to own. AASM is the pragmatic choice for an administrator who values integrated scheduling and backups. Docker suits teams that already operate containers and want a reproducible deployment. Manual SteamCMD and systemd suit experts willing to maintain every script and recovery path.

Whichever route you select, keep the Windows-depot and Proton architecture in mind, use ASA-specific arguments and map identifiers, open only the required ports, and prove an external connection before scaling. That is the reliable way to host ASA on Linux without inheriting assumptions from older ASE guides.

Quick Recap

Bestseller No. 1

ARK: Survival Evolved Pins - Dodo

Raised, textured surface gives the design real depth instead of a flat printed look; A gift for ARK players, survival game fans, and dinosaur enthusiasts

$11.99

Bestseller No. 2

ARK: Survival Evolved Pins - Rex

Raised, textured surface gives the design real depth instead of a flat printed look; A gift for ARK players, survival game fans, and dinosaur enthusiasts

$11.99

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.