{"id":20466,"date":"2024-12-26T15:06:47","date_gmt":"2024-12-26T15:06:47","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=20466"},"modified":"2026-06-15T18:05:33","modified_gmt":"2026-06-15T18:05:33","slug":"aska-dedicated-server-installation-guide","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/aska-dedicated-server-installation-guide\/","title":{"rendered":"ASKA Dedicated Server Installation Guide"},"content":{"rendered":"\n

ASKA, the Viking survival and village-builder from Sand Sailor Studio, ships with an official dedicated server so your settlement keeps running whether or not the host is online. The setup has a few sharp edges that trip up almost everyone: the server uses a different<\/em> SteamCMD App ID than the game, the config file has a literal space in its name, and your server stays invisible in the in-game browser until you add a valid Steam authentication token. This guide walks through every step in detail so your world is online and discoverable on the first try.<\/p>\n\n\n\n

If you’d rather skip the manual work entirely, a one-click managed ASKA server<\/a> handles SteamCMD, ports, and config for you. But if you want to self-host, read on \u2014 everything you need is below.<\/p>\n\n\n\n

ASKA dedicated server: the key facts<\/h2>\n\n\n\n

Before downloading anything, it helps to know the numbers you’ll need. ASKA is still in Early Access in 2026 (it launched June 20, 2024), with the recent “Seaborne Raiders” major update and more content planned through the year. Co-op is hard-capped at 4 players<\/strong> \u2014 one host plus up to three friends \u2014 and that cap is a game limit, not a server setting you can raise.<\/p>\n\n\n\n

Item<\/th>Value<\/th><\/tr><\/thead>
ASKA game App ID<\/td>1898300<\/td><\/tr>
Dedicated server SteamCMD App ID<\/td>3246670<\/td><\/tr>
Server executable<\/td>AskaServer.exe (Windows-only)<\/td><\/tr>
Config file<\/td>server properties.txt (note the space; plain text)<\/td><\/tr>
Steam Game Port<\/td>7777 (TCP\/UDP)<\/td><\/tr>
Steam Query Port<\/td>27015 (TCP\/UDP)<\/td><\/tr>
Max players<\/td>4 (hard cap)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Keep that table handy \u2014 the two App IDs in particular are the source of most failed installs. You install the server with 3246670<\/strong>, but you create the authentication token under 1898300<\/strong>. We’ll return to that.<\/p>\n\n\n\n

Platform support: Windows native, Linux via workarounds<\/h2>\n\n\n\n

This is important to settle before you pick a machine. The ASKA dedicated server only ships a Windows build<\/strong> \u2014 there is no native Linux depot. If you’re on Linux, you have two community paths: run it through Wine\/Proton, or use a community Docker wrapper (images such as jimbit0\/aska-dedicated-server<\/code> and struppinet\/aska-dedicated-server<\/code> exist). Those Docker images are community-maintained and their quality isn’t officially verified, so test before trusting one with a long-lived world.<\/p>\n\n\n\n

For the smoothest experience, host on Windows or use a provider that has solved the Linux compatibility layer for you.<\/p>\n\n\n\n

Step 1: Install the server with SteamCMD<\/h2>\n\n\n\n

SteamCMD is Valve’s command-line tool for downloading dedicated server files. The ASKA server supports anonymous login<\/strong>, so you don’t need to provide Steam credentials. Download SteamCMD, then run:<\/p>\n\n\n\n

steamcmd +login anonymous +app_update 3246670 validate +quit<\/code><\/pre>\n\n\n\n
The validate<\/code> flag checks file integrity and re-downloads anything corrupt \u2014 worth keeping in your update command going forward. A few early-adopter forum posts complained that anonymous login “didn’t work as expected” right after the server released, but this appears to have been resolved. If it ever fails for you, re-run the command; transient Steam content-server hiccups are usually the culprit.<\/p>\n\n\n\n
By default the files land in a folder like:<\/p>\n\n\n\n
:\\SteamLibrary\\steamapps\\common\\ASKA Dedicated Server\\<\/code><\/pre>\n\n\n\n
If you run a control panel like WindowsGSM, the files may instead live under a serverfiles\/<\/code> directory. Note the executable name varies slightly across guides (you’ll see both AskaServer.exe<\/code> and ASKAServer.exe<\/code>); the primary-style setup guides use AskaServer.exe<\/strong>, so that’s the spelling to expect.<\/p>\n\n\n\n
Step 2: Configure server properties.txt<\/h2>\n\n\n\n
ASKA is configured through a single plain-text file named server properties.txt<\/strong> \u2014 yes, with a space in the middle, and no .ini<\/code> or .json<\/code> structure. You’ll find it in the same folder as the executable after the first launch. One quirk worth knowing: the ports are written into the file on the first launch only<\/strong>. After that, any changes require you to edit the file by hand and restart.<\/p>\n\n\n\n
The field names below are confirmed across credible host knowledge bases. Note that some third-party templates float around the web listing settings like PvPEnabled<\/code>, WorldSeed<\/code>, SaveInterval<\/code>, or a “4\u201316 max players” range \u2014 those look auto-generated and contradict ASKA’s real 4-player cap, so don’t trust them. Stick to the verified fields here:<\/p>\n\n\n\n
Setting<\/th>Purpose<\/th><\/tr><\/thead>
Display name<\/td>Name shown in the in-game server browser<\/td><\/tr>
Password<\/td>Restricts access; leave empty for an open server<\/td><\/tr>
Max players<\/td>Session cap \u2014 4 is the game hard-cap<\/td><\/tr>
Steam Game Port<\/td>How players connect (default 7777)<\/td><\/tr>
Steam Query Port<\/td>How the server appears in lists (default 27015)<\/td><\/tr>
Region<\/td>Server visibility \/ connection quality<\/td><\/tr>
Authentication token (GSLT)<\/td>Steam server auth \u2014 must be filled (see Step 4)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Set a clear Display name<\/strong>, pick a Region<\/strong> close to your players for the lowest latency, and add a Password<\/strong> if you want a private session. Leave the Authentication token<\/strong> field for now \u2014 we generate that in Step 4. A few additional world options (such as a “keep server world alive” toggle that controls whether the world keeps simulating with no players connected) are reported by some hosts but not broadly confirmed; if you see them, the safe default is to leave them as shipped until you’ve read the developers’ documentation.<\/p>\n\n\n\n
Step 3: Open the right ports<\/h2>\n\n\n\n
ASKA uses a two-port split, and both must be reachable from the internet for players to find and join your server:<\/p>\n\n\n\n