Table of contents
BenefitsRenting vs local servers1. Prep server files2. Choose server hardware3. Configure settings4. Open ports (local)5. Start the server6. Join your server!TroubleshootingVPS or dedicated server?
Get the industry’s best gaming servers
See game servers

ASKA dedicated server setup guide

If you’re already hooked on ASKA’s survival-meets-Viking vibe, running your own server is the next step. Whether you’re building a clan with friends or just want a persistent world that doesn’t shut down when you log off, hosting your own server unlocks full control and 24/7 access. You don’t have to be a sysadmin to pull it off, just follow the steps below.

Let’s walk through how to set up an ASKA dedicated server, whether you’re running it from your own PC or renting from a provider.

Ready to build your tribe?

Let’s fire up that server and make the gods envious!

Explore dedicated servers
Build now

Benefits of hosting your own server

A dedicated server gives you full control over your ASKA world, along with better stability for multiplayer.

  • Persistent world: Your server stays online whether you’re playing or not.
  • Custom settings: Tweak PvP, difficulty, seed generation, and more.
  • Better performance: Especially when renting a server built for hosting.
  • Mod freedom: Add or update mods without worrying about breaking someone else’s game.
  • Invite-only access: Share your IP or password with friends, no randoms allowed.

Renting vs hosting locally

Both local and rented hosting work, but they come with different trade-offs. Here’s how they compare.

Local hosting pros:

  • Free if your hardware’s up to it
  • Full access to files on your own machine
  • No third-party provider required

Local hosting challenges:

  • You need a strong CPU, SSD, and high upload bandwidth
  • Uptime depends on your PC being on
  • Requires router configuration (port forwarding)
  • Exposes your home IP to the internet

Rented server pros:

  • 24/7 uptime in a secure data center
  • Professional support if you get stuck
  • No impact on your gaming PC’s performance
  • Built-in DDoS protection and automated backups

Rented server challenges:

  • Monthly fee
  • Slight learning curve on your first server

If you plan to host long-term or play with a group across time zones, renting is usually the smarter move for stability and performance.

Step 1: Prep your ASKA server files

Currently, ASKA doesn’t have a standalone dedicated server app on SteamCMD, so you’ll need to start from your installed game files.

If hosting locally:

  1. Install ASKA through Steam on your PC
  2. Navigate to:
    C:\Program Files (x86)\Steam\steamapps\common\ASKA
  3. Copy the entire ASKA folder to a new directory for server use
  4. Optional: Remove any unused assets or client-side mods
  5. You’ll launch the server from this folder later.

If renting a server, you’ll manually upload and configure the game files. Here’s what to do:

  1. Install ASKA on your local machine via Steam. Just like with local hosting, install the game and find the folder:
    C:\Program Files (x86)\Steam\steamapps\common\ASKA
  2. Compress the ASKA folder. Zip or tar the entire ASKA game folder into a single archive (ASKAServer.zip). This makes it easier to upload everything at once.
  3. Access your server. Log into your hosting provider’s control panel or connect via SSH (for gaming VPS or dedicated servers). Make sure you have SFTP access enabled.
  4. Upload the compressed folder. Use an FTP client like FileZilla to upload the zipped ASKA folder to your server’s root or home directory (e.g., /home/aska/).
  5. Extract the files on the server. Once uploaded, use your host’s file manager or run a command like unzip ASKAServer.zip (or tar -xvzf ASKAServer.tar.gz) to unpack the files.
  6. Install prerequisites (if needed). Make sure your server has required dependencies like DirectX redistributables or .NET/Mono installed. If you’re running Linux, you may need Wine or a compatibility layer unless a Linux-native build is available.
  7. Set permissions. Ensure the server files have the proper execute permissions using:
    chmod +x ASKAServer.exe (or the equivalent startup script)
  8. Prepare to configure and launch. You’re now ready to set config options and start the server, which we’ll cover next.

Step 2: Choose your server hardware

ASKA isn’t extremely demanding, but multiplayer and larger worlds benefit from solid specs.

Minimum specs for local hosting (up to 4–6 players):

  • Quad-core CPU
  • 8 GB RAM
  • SSD storage
  • 10 Mbps upload

Recommended specs for larger groups or modded worlds:

  • 6–8 core CPU with high single-thread performance
  • 16 GB+ RAM
  • NVMe SSD
  • 50+ Mbps upload

If you’re renting, look for a provider that offers:

  • Game VPS or dedicated servers with root access
  • DDoS protection
  • 99.99% uptime guarantee
  • Easy file access via FTP or control panel

Step 3: Configure your server settings

ASKA stores its config files in a folder like /Config or alongside the server executable. Settings are usually saved in .ini or .json format. Adjust the following before launch:

  • ServerName: Name that shows in the server browser
  • Password: Optional, but recommended for private sessions
  • MaxPlayers: Typically 4–16
  • PvPEnabled: True or false
  • WorldSeed: Fixed for predictable maps
  • SaveInterval: In minutes, for autosaves

Make a backup of your config file before editing. Typos in syntax can crash the server at launch.

Step 4: Open ports (local only)

To let others join your local server, you’ll need to allow traffic through your router.

  1. Open your router’s admin panel (usually at 192.168.1.1)
  2. Port forward the ASKA port—most likely 27015 (UDP/TCP)
  3. Make sure Windows Firewall also allows this port
  4. Use a site like CanYouSeeMe.org to confirm it’s open

If this sounds like a hassle, that’s another reason to rent a server—no port forwarding required.

Step 5: Start the server

Use the server executable or launch command included with your ASKA install.

To launch, run ASKAServer.exe or use a command-line launch with flags like:
ASKAServer.exe -log -server -port=27015

Watch the console for errors. If the world loads and the port is open, you’re good to go.

If you’re on a rented VPS or dedicated server, use your host’s terminal or control panel to run the command from the correct directory.

Step 6: Join your server

Now it’s time to jump in.

  • Local join: Use direct IP connect inside ASKA
  • Public join: If you’ve made your server public, it should show in the in-game browser
  • Private friends: Share your public IP and port (e.g., 123.45.67.89:27015) and the server password

Everyone joining should be on the same ASKA version and have matching mods installed.

Troubleshooting common issues

Here are quick fixes to common problems:

  • Server not appearing in browser: Make sure your server is set to public in the config file and that you’ve correctly forwarded the default port (usually 27015). If you’re behind a NAT or using a firewall, your server might not broadcast properly, try connecting directly via IP instead to verify that it’s online.
  • Friends can’t connect: Double-check that you’re sharing your public IP address (not your internal one), and confirm that the port is open using a tool like CanYouSeeMe.org. Also verify that your friends are entering the correct port number in addition to the IP (e.g., 123.45.67.89:27015).
  • Crash on launch: This is often due to typos or missing brackets in your config file, corrupted world data, or missing runtime libraries. Open the launch window or server console and review the error message, fix the line causing issues or try starting with a fresh world file to isolate the problem.
  • Mod mismatch: ASKA may not auto-sync mods, so all players must install the same mods in the same order on their local machines. Check each player’s mod list and version numbers, and make sure the host/server is using the same versions to avoid desync or connection failures.
  • Server loads but no one can connect: Check your Windows Firewall or server-side firewall rules to ensure ASKA’s port is allowed on both TCP and UDP. On Linux-based VPS servers, confirm that UFW or firewall is not blocking access, use ufw allow 27015/udp (or the port you configured) to open it up.
  • Can’t save or access world data: This could be a permissions issue, make sure the server executable has write access to the directory it’s running in. On rented Linux servers, confirm the user account running the server owns the directory and has write permissions (chown -R user:group /path/to/server).
  • Server restarts or shuts down unexpectedly: This is often caused by memory limits on VPS plans or unhandled exceptions. Check your server logs for out-of-memory errors or fatal exceptions, and consider upgrading your VPS or switching to a dedicated host if it keeps happening under normal usage.

For more help, check ASKA’s Discord or community forums.

VPS vs dedicated server rental for gaming

When renting server hardware for ASKA, you’ll usually choose between a Virtual Private Server (VPS) and a full dedicated server. Both let you host your game remotely, but they serve different needs depending on scale and performance.

VPS: Ideal for small to mid-size groups

A VPS gives you a slice of a physical server, with isolated resources like CPU cores, RAM, and storage. It’s cost-effective and fast to deploy, making it a solid choice for casual or private ASKA multiplayer sessions.

Best for:

  • 2–6 player co-op
  • Lower/moderate mod usage
  • Short- to medium-term server lifespans
  • Budget-conscious hosts

Pros:

  • Affordable monthly pricing (often $5–40)
  • Scales up easily with your needs
  • Good for learning Linux or server basics

Cons:

  • Limited total performance (shared hardware)
  • May throttle under heavy CPU or disk load
  • Not great for massive worlds or 24/7 activity

Dedicated server: Built for heavy use and long-term worlds

A dedicated server gives you the entire physical machine, no sharing. This is the top-tier option for serious hosts running large or persistent ASKA worlds.

Best for:

  • 6+ players or heavily modded setups
  • Always-on servers with daily use
  • Hosting multiple game servers or services
  • Long-term communities or streamers

Pros:

  • Maximum performance and stability
  • No noisy neighbors or resource contention
  • Easier to manage backups, automation, and mod testing

Cons:

  • Higher cost ($70+/month)
  • May require more server management experience
  • Overkill for casual or solo use

Which one should you choose?

If you’re hosting for a small group of friends and want to keep things affordable, a VPS is usually enough, as long as you choose one with SSDs and 4+ CPU cores. 

But if you’re building a persistent world, plan to add heavy mods, or want complete isolation and power, go with a dedicated server. It’s more expensive, but you get total control and future-proof performance.

Succeed as a game hosting reseller

How to start selling Minecraft servers

Watch on demand

Additional resources

How to start selling Minecraft servers →

Turn a hobby into a side-hustle

Latency and rage-quitting →

Liquid Web’s industry study on latency and gaming

Dedicated vs. listen servers →

Pros and cons of each so you can decide what you need