Host your own Minecraft server (without the command line)

Published 4 August 2026 · SparkBox team

Renting a Minecraft server costs about £8–15 a month, and the day you stop paying, the world your kids built goes away. If you already have a SparkBox — a NAS, a mini PC, an old laptop — it can host that world itself, for nothing, and the save files stay on your hardware forever. This guide gets you from “nothing installed” to “my friend just joined” without typing a single command.

1. What you're actually installing

The app is called Crafty Controller. Think of it as a dashboard for Minecraft servers: you open it in your browser, click a button to create a world, and it handles the fiddly parts — downloading the right Minecraft version, starting and stopping the server, taking automatic backups, and showing you who's online.

You never touch a terminal, and you never edit a config file unless you want to. SparkBox installs it, points it at a folder for your worlds, and makes sure you can find the login password.

2. Install it (one click)

1. Open your SparkBox dashboard and go to Apps.
2. Find Game Servers and click Install.
3. Wait a couple of minutes. The first start takes longer than most apps because it sets up its database and generates its own security certificate.

When it's ready, a Game Servers tile appears on your Home page.

3. Create your first server

1. Click the Game Servers tile. Your browser will warn you about the certificate — that's expected. The panel is encrypted with a certificate your own box generated, which browsers can't vouch for because nobody else issued it. Click Advanced → Proceed.
2. Sign in as admin. The password is in your dashboard under Settings → Service Passwords — Crafty makes up its own password the first time it runs, and SparkBox copies it there so you can find it.
3. Change that password once you're in (Crafty's own Settings → Users). Crafty owns that credential, so SparkBox can't reset it for you later.
4. Use the server wizard: give the world a name, pick Minecraft Java, and choose a version.

4. Getting your friends connected

Inside your house, people connect using your box's local address and the port, like 192.168.1.50:25565. That works immediately, no setup.

From outside your house it needs one more step, and this is the part guides usually skip:

• On a NAS or home PC: you have to tell your router to send Minecraft traffic to your box. That's called port forwarding — forward port 25565 to your SparkBox's local address. Every router words this differently ("Port Forwarding", "Virtual Server", "NAT"), so search your router's model plus "port forwarding". SparkBox can't do this step for you: it's your router's setting, not your server's.
• On a VPS: nothing to do. SparkBox opens its own firewall for the ports it publishes, and your friends connect to the server's public address.

Your friends then join with your public address (or a free dynamic-DNS name if your home address changes).

5. How much memory you need

Be honest with yourself here, because this is what decides whether the server feels good or terrible:

• The panel itself is light — about half a gigabyte.
• Each running world wants 2GB or more on top of that. A vanilla server with a few friends is comfortable at 2–4GB. Big modpacks want 6GB+ and will be miserable with less.
• SparkBox caps the whole thing at 4GB by default, which fits the panel plus one normal world. If you're running a modpack or a second world and you have the memory to spare, a Backer can raise that limit in the per-app overrides.

If your box has 4GB total and it's already running Jellyfin and Immich, a Minecraft server is going to be tight. That's not a SparkBox limitation — Minecraft is genuinely memory-hungry.

6. When something goes wrong

"My friend can't connect." In order of likelihood: their Minecraft version doesn't match the server's; port forwarding isn't set up on your router (from outside the house); or the server isn't actually running — check the panel.

"The server keeps stopping." Almost always memory. Give it more, or run fewer things at once.

"I lost the admin password." Settings → Service Passwords shows the one Crafty generated at setup. If you already changed it inside Crafty, that's the one that works and only you have it.

Legend supporters can also just ask Tom AI in the dashboard — it can read the server's actual logs and tell you what the error means in plain English, which beats guessing.