A dedicated server isn’t just a machine running ARK. It’s a controlled environment where your rules matter, and the world stays stable.
When you run ARK on dedicated hardware, you remove the unpredictable parts. You get NVMe storage that handles ARK’s constant writes, consistent CPU performance, and great support that keeps your tribe’s ping under control. Most importantly, the world stays online even when your own PC is off.
If you want to understand how to make a dedicated server on ARK without wasting days on trial and error, Linux is the cleanest and most reliable path. This guide uses Ubuntu 22.04 and the community-maintained ARKSurvivalAscended-Linux installer.
The workflow covers deployment, configuration, port setup, map (world) management, whitelisting, security, performance tuning, and long-term maintenance.
You end up with a clean, repeatable ARK dedicated server setup.
You should host ARK on a dedicated server if you want:
Hosting ARK on a dedicated server isn’t complicated. If you want to understand how to host a dedicated server on ARK without any guesswork, you’re in the right place.
Before continuing, make sure you have:
Before installing anything, choose hardware that can survive ARK’s load. The game hits CPU, RAM, and disk far harder than most survival titles, so the right dedicated server matters more than the installation script.
ARK hammers a single core during startup, then spreads load across others.
For real stability, aim for 4–6 cores for small and medium tribes, and 8–12 cores if you use heavy mods or multiple maps.
More cores mean faster world loads, higher tick rate, and better mod performance.
Even an empty ARK world eats 10–12 GB of memory.
Add mods, big structures, or a busy tribe, and 20+ GB becomes the real baseline.
If your RAM is too low, ARK won’t crash loudly — it will hang, restart loops, or silently corrupt saves.
ARK updates are huge. Maps grow. Mods pile up.
Use NVMe storage of at least 100–150 GB for a clean modded setup, and 150–200 GB of NVMe storage if you run multiple maps or long-term worlds.
NVMe solves most of the stutter issues players complain about because it absorbs constant writes without freezing the world.
If your tribe is spread across countries, place the server geographically between them.
is*hosting’s global locations make it easy to pick the one that keeps everyone’s ping stable.
ARK is not a lightweight game. It loads huge amounts of world data into memory and hammers the disk with constant writes.
|
Players |
CPU |
RAM |
Drive (NVMe) |
Mods |
|
1–4 |
4 cores |
16 GB |
80–100 GB |
Vanilla |
|
5–10 |
6 cores |
24 GB |
120–150 GB |
Light mods |
|
10+ |
8 cores |
32–64 GB |
150–200 GB |
Heavy mods |
This is where the real setup begins — the Linux workflow designed for stability, clarity, and predictable behavior.
Everything below has been tested on the Ubuntu 22.04 environment. Before you open an SSH client, there's one option you should know about.
You can manage your ARK server in two different ways:
Most guides mention SSH only, but the Terminal comes with advantages that make the entire installation safer, especially if you’re new to Linux or switching between devices.
You have two options; both work for the entire installation.
You will see the same prompt you would see in SSH:
root@your-server:~#
From here, you can perform the entire ARK deployment from your browser.
On Windows, macOS, or Linux in a basic terminal:
ssh root@YOUR_SERVER_IP
Example:
ssh root@5.46.66.27
Type your password. If you’re using SSH keys, the process is identical — the server accepts the key and logs you in.
After login, you’ll see the standard Ubuntu prompt.
Update base packages:
apt update
apt upgrade -y
Install essentials:
apt install -y curl wget sudo python3 python3-venv python3-pip
Python is required for the manage.py interface.
This step relies on a mature, community-maintained deployment toolkit created specifically for running ARK: Survival Ascended on Linux servers.
The project provides a fully automated installation workflow and abstracts away the manual complexity normally required for ARK:
In practice, this installer becomes the foundation of your entire server environment, ensuring a predictable layout and stable long-term maintenance. The community keeps the installer updated, so it usually stays ahead of ARK’s patch chaos.
Download the installer script:
cd ~
wget -O server-install-debian12.sh \
https://raw.githubusercontent.com/cdp1337/ARKSurvivalAscended-Linux/main/dist/server-install-debian12.sh
And install:
chmod +x server-install-debian12.sh
Verify it:
ls
You should see server-install-debian12.sh.
Note: The installer is labeled for Debian 12 but is tested and works on Ubuntu 22.04 as well.
Run:
./server-install-debian12.sh
The installer will ask:
Create steam user?
Y
Primary server IP?
5.46.66.27
(or your real IPv4)
Secondary server IPs?
Press Enter.
Enable firewall (UFW)?
Y
ARK will download (AppID 2430930), configure SteamCMD, build directories, and initialize system services.
When everything is done, you’ll see:
Success! App '2430930' fully installed.
Your installation lives in:
/home/steam/ArkSurvivalAscended/
This is the moment where you’ve successfully completed the core steps of setting up a dedicated ARK server.
Now we need to set up the map.
Run:
cd /home/steam/ArkSurvivalAscended/
sudo ./manage.py
You’ll see something like:
This interface allows you to:
Select your map and press its number:
4
ARK prefers ASCII names.
Press:
N
Name it something simple:
IsHost_ARKSA_Island
Press:
E
Press:
A
Set:
Admin Password: your_admin_pass
RCON Password: your_rcon_pass
You now control everything in-game through:
enablecheats your_admin_pass
When players search online for how to run a dedicated server for ARK, this is the configuration step they often miss.
Press:
S
Startup facts:
When it’s ready:
Status: Running
To exit the manager, press:
B
Q
Your server continues running.
Everything should look like this:
Run:
ss -tulpn | grep -E '7701|27001'
You want:
udp ... 0.0.0.0:7701 …
tcp ... 0.0.0.0:27001 …
If ports aren’t open, the server doesn't launch successfully.
Check logs:
tail -n 50 /home/steam/ArkSurvivalAscended/ShooterGame.log
Check status:
ufw status verbose
If missing:
ufw allow 7701:7709/udp
ufw allow 27001:27009/tcp
ufw reload
Never blindly run:
ufw enable
If UFW is already in production mode, it can break connectivity.
This step is crucial for understanding how to host a dedicated server for ARK safely.
Launch ARK on your PC. Open the console:
open YOUR_IP:7701
Example:
open 5.46.66.27:7701
If the server is password-protected, ARK will prompt you. If you see character creation, your server works.
Launch ARK: Survival Ascended on your PC. Open Multiplayer and go to Server Settings. Enable the option that shows Unofficial.
MARK the checkbox: Show Player Servers.
Use the search field and enter the server name you configured. For example:
IsHost_ARKSA_ISLAND
Your server appears on the list once the browser finishes refreshing. Select it and connect.
The game loads into character creation. Create your survivor and enter the world. The server now runs 24/7 on your dedicated server, and you can play without interruptions.
A public ARK server attracts random players as soon as it appears on the Unofficial list. If you want full control over who joins, lock the server and whitelist your group.
Edit the main server configuration:
nano /home/steam/ArkSurvivalAscended/GameUserSettings.ini
Add or update the following lines:
ServerPassword=joinpass
ServerAdminPassword=adminpass
Save the file and restart the server through manage.py to apply the changes.
If you want the server to be inaccessible to anyone outside your group, use the whitelist file. The players (their Steam IDs) listed here can join even if the server has a password.
Open the whitelist:
nano /home/steam/ArkSurvivalAscended/PlayersJoinNoCheckList.txt
Add Steam64 IDs, one per line:
76561198000000001
76561198012345678
Save the file and restart the server.
With these settings applied, the server stays private, and only the players you approve can join.
Find IDs here: https://steamid.io
This is a core component of how to make a dedicated server on ARK feel truly private and secure.
There are basic steps for maintaining the ARK dedicated server.
sudo /home/steam/ArkSurvivalAscended/manage.py
U
apt install htop
htop
If RAM exceeds 85%, upgrade to the dedicated server.
Snapshots help you recover from mod failures.
crontab -e
Add:
systemctl restart ARKascended@TheIsland_WP.service
cd /home/steam/ArkSurvivalAscended/SavedArks
rm *.bak
Keep at least one.
If you’re trying to understand how to set up a dedicated ARK server without getting stuck on invisible issues, start here.
Many players fail their first ARK dedicated server setup because they skip basic checks — usually ports, RAM limits, or mods. Here are the problems every ARK admin eventually runs into, along with the fixes that actually matter.
First, check the direct connection. If this works, the game’s browser is the problem, not your server.
open IP:PORT
If the direct connection fails, continue below.
Run:
ss -tulpn | grep 7701
ufw status
If the port isn't listening, then the server never finishes launching.
If UFW blocks it, open the port and reload.
High ping in ARK feels like fighting inside syrup — delayed movement, stuttering dinos, and PvP that turns into a lottery. The real causes are usually simple.
If your dedicated server is on the wrong side of the planet, nothing will save the ping.
Pick a region physically close to your players. is*hosting offers several global locations for dedicated servers, so you don’t need to settle for something “somewhere in Europe.”
Sometimes the issue isn’t your server — it’s that one friend whose Wi-Fi drops packets like crazy.
Ask them to run:
ping <your_server_ip> -t
High spikes on their side are a local network problem, not your dedicated server.
Some mods add huge creatures, structures, or scripts that drag the tick rate down.
Wildcard updates frequently break mods or configs. If the world loads but behaves strangely (missing engrams, broken spawns, empty inventories), your save is likely corrupted post-update.
Use is*hosting’s free weekly backups to roll back. You restore the entire dedicated server snapshot, not individual ARK files, which avoids chasing down dozens of broken assets.
It’s also the fastest way to recover from the “We installed 12 mods, and everything exploded” scenario.
Your ARK: Survival Ascended environment is now fully deployed and configured according to best practices for Linux-based hosting. You’re operating a stable, maintainable, and predictable server stack suitable for long-term use, updates, and player load.
You now have:
Your ARK server is now under full administrative control, behaves consistently across reboots, and remains online without dependency on client hardware or home networks.
Want to try another game? Try to host Command&Conquer on a VPS.