Halloween at Nexthosting: 10% off game servers with the code – until November 1
Setting up an ARK server: learn how to install SteamCMD, open ports, lock down RCON, and set up autostart so your server...
An ARK server is up and running once you have installed SteamCMD with the right app ID (2430930 for ARK: Survival Ascended, 376030 for ARK: Survival Evolved), opened ports 7777, 7778, and 27015 via UDP, and consistently sealed RCON on port 27020 off from the internet. After that, autostart via systemd or the Windows Task Scheduler ensures the server comes back online after a restart. If you want to save yourself the effort of port forwarding and maintenance, consider renting a server from a hosting provider instead.
In short:
- For a stable ARK server, you should use at least 16 GB of RAM and an SSD; with more players or mods, 16 GB or more is recommended.
- Port forwarding for UDP 7777, 7778, and UDP 27015, as well as restricting the RCON port to local access, is mandatory.
- With more than 10 to 15 players or an extensive mod list, a VPS or dedicated server in a data center usually pays off economically.
- During server installation, users should use app ID 2430930 for ASA or 376030 for ASE to avoid error messages.
- Automatic server startup via systemd or Task Scheduler increases uptime, while regular backups of save files and a secure RCON configuration strengthen security.
Before you type a single line of SteamCMD commands, a more important decision awaits: where should the server actually run? Your own computer at home is the cheapest option and gives you full control over hardware and configuration. The catch is in the details that many people only notice at the first stutter.
A home connection usually has a much lower upload limit than download limit, and upload is exactly what counts when hosting. If the router chokes, all players notice it at the same time as lag. On top of that, your server is only online as long as your PC is running, and a residential connection has virtually no defense against a DDoS attack.
A VPS or dedicated server in a data center solves both problems at once:
The decision depends on three factors: planned player count, mod scope, and how much time you want to put into maintenance. With more than 10 to 15 players or a larger mod list, an ARK server at Nexthosting usually becomes more economical than a home setup once you factor in electricity costs and time spent.
ARK is notoriously demanding, which applies to Survival Evolved just as much as to Survival Ascended. 8 GB of RAM counts as the entry point, but that is only enough for a small, unmodded server with few players. As soon as mods, more map instances, or over 20 players come into play, you should plan for 16 GB or more.
For the CPU, single-core performance matters most, since the server engine does not distribute many calculations cleanly across multiple cores. More cores still help once several server instances or cluster maps run on the same machine.
Storage and drive type:
Pro tip: Do not base your upload calculation on the raw player count alone. Ten active players with many tames and bases generate noticeably more traffic than ten players on an empty map. If you calculate too tightly, you will get the bill in the form of rubberbanding.
A 64-bit operating system is strongly recommended, as the server may otherwise fail to start. Windows Server and current Linux distributions such as Debian or Ubuntu both work, although ASA on Linux needs additional steps via Wine, more on that shortly.
SteamCMD is the command-line tool you use to download and update the server without the graphical Steam interface. The crucial point where many guides online get confused is the correct app ID.
Installing an ARK: Survival Ascended dedicated server uses app ID 2430930. If you are still running ARK: Survival Evolved instead, you need app ID 376030. If you mix up the two IDs, SteamCMD either downloads the wrong game or aborts with an error message.
C:\arkserver or /home/ark/arkserver, and use this path consistently via force_install_dirvalidate to the command with every update, which prevents corrupt installations caused by interrupted downloadsThe validate flag on app_update looks inconspicuous, but in practice it prevents most startup errors caused by incomplete downloads.
On Windows, the installation is comparatively straightforward. You need SteamCMD, an installation folder, and a clean start script.
C:\steamcmdsteamcmd.exe and run login anonymous on first launchapp_update 2430930 validate (for ASA) or app_update 376030 validate (for ASE) and specify the target folder via force_install_dirstart_server.bat containing the start command of the server executable, the map parameters after the question mark, and the additional dash flags after that. Start the server locally and connect in the game via the internal address 127.0.0.1 to check basic functionalityThe most common mistake in the start script is the parameter syntax: map options such as session name or server password belong after the question mark in the query string, while technical flags such as the port belong after that as standalone dash parameters. If the port is mistakenly written into the query string instead of being set as -port=, the server often falls back silently to the default port 7777 without displaying an error message.
Pro tip: Test the start script first without integrating autostart. Only once the server starts up cleanly and is reachable locally is it worth adding it to the Task Scheduler.
For Linux operators, the process looks somewhat different, especially for ARK: Survival Ascended, since no native Linux binary exists for it.
ark, and install SteamCMD via your distribution's package managersteamcmd +login anonymous +force_install_dir /home/ark/arkserver +app_update 376030 validate +quit for ASExvfb-run to provide a virtual display without a real screen. Configure file permissions and ulimit values for the ark user so the process has enough open file descriptors availableExecStartPre automatically runs a SteamCMD update with validate before every startThe Wine workaround for ASA usually works reliably in practice, but deserves a few test runs under real load before you rely on it. If you want to avoid this additional configuration step, a preconfigured ARK server at Nexthosting provides an environment where this is already set up.
A server that only runs as long as a console window stays open is unsuitable for permanent operation. A crash, a computer restart, or an accidentally closed terminal, and the community is left facing a timeout.
On Linux, systemd handles this task reliably. The service starts the server automatically after every boot, restarts it after a crash, and can be configured with an ExecStartPre entry so that a SteamCMD update with validate runs before every start. Important: set a restricted User= and Group= in the service file instead of root, which limits the damage in case of a compromise.
On Windows, the Task Scheduler takes the same role. Two settings are crucial:
Pro tip: Check the logs after every update before you open the server to players. A failed validate often only shows up at the next crash, not immediately at the update itself.
Without correct port forwarding, your server stays invisible to other players, no matter how cleanly the installation went otherwise. The ARK community wiki lists the default ports required for a server without cluster operation.
| Port | Protocol | Function |
|---|---|---|
| 7777 | UDP | Gameplay traffic |
| 7778 | UDP | Peer connection, second gameplay port |
| 27015 | UDP | Server query, provides visibility in the server browser |
| 27020 | TCP | RCON, keep reachable only locally or via VPN |
On Windows, create inbound rules for the UDP ports in Windows Firewall, each for your own start script or the server executable. On Linux, you do this with ufw allow 7777/udp, ufw allow 7778/udp, and ufw allow 27015/udp, or alternatively directly via iptables rules.
On the router, you additionally need a port forward to the server's internal IP address. It is best to assign a fixed LAN IP or a DHCP reservation for this, so the forward does not point to nothing after a router restart. You can check whether the ports are actually reachable with an external port checker, or by having a friend outside your network try to connect.
RCON is the remote administration interface for admin commands, and that is exactly why it should never be openly exposed to the internet. For security reasons, the ARK wiki recommends either keeping RCON local or making it accessible only via a VPN or SSH tunnel.
ServerAdminPassword and store it in a password manager rather than in a text filePro tip: Keep at least three backup generations, not just the latest one. A corrupted save is sometimes only noticed after several hours, by which time the most recent backup may already be just as broken.
Mods are almost standard in ARK, whether obtained through the Steam Workshop or CurseForge. The problem is rarely the installation itself, but underestimating the space required.
A server that can no longer save because the disk is full can, in the worst case, lose all progress from the last several hours. A simple space alert or a weekly manual check is often enough to prevent that.
The server is installed, the ports are open, and still nobody connects. Before you despair, work through this sequence.
netstat (Windows) or ss/lsof (Linux) to check whether the server process is actually listening on the expected ports127.0.0.1 first, then from an external network, to tell router problems from software problemsIf nothing helps despite all these steps, three suspects usually remain: a full disk, wrong file permissions, or a stubborn firewall rule. If you cannot get any further on your own, a rented server gives you access to the provider's technical support.
Self-hosting works, no question. But as the community grows, downtime, port problems, and backup upkeep weigh more heavily than the money saved. Professional hosting with a German location and DDoS protection takes exactly that burden off your shoulders.
— Erik
Anyone who has worked through the steps so far knows: an ARK server does not just run on the side. Port forwarding, autostart configuration, backup rotation, and constantly checking free storage add up to real maintenance effort, especially as the community grows and several mods are added.
Hosting providers take over exactly this part. The servers are often located in Germany, run with DDoS protection, and can be managed through a control panel, without you having to set up port forwarding on your home router. Provisioning is usually quick, and support is there for technical questions instead of leaving you alone with logs and iptables rules.
If you would rather start playing right away than debug SteamCMD commands, you will find the right overview on the page for renting an ARK server. For operators who also want more control over the server environment, for example for several games on the same machine, the VPS options from Nexthosting are worth a look.
You install the server via SteamCMD with the right app ID (2430930 for ASA, 376030 for ASE), open ports 7777, 7778, and 27015 via UDP, and set up autostart via systemd or Task Scheduler. RCON on port 27020 should remain reachable only locally or via VPN, as the ARK community wiki recommends.
Strictly speaking, only self-hosting on your own hardware is free, since SteamCMD and the server software themselves cost nothing. You then pay indirectly through electricity, your internet connection, and your own time for maintenance, backups, and troubleshooting.
That depends on player count, desired location, and support requirements. For operators who want a German server location, DDoS protection, and fast provisioning, an ARK server from Nexthosting is a practical option that already takes care of the technical preparation described in this article.
Download SteamCMD, install the server with the correct app ID and the validate flag, configure a start script with clean parameter syntax, and open the required ports on your firewall and router. For permanent operation, you then add an autostart mechanism via systemd or Task Scheduler.