Host a Minecraft Server on an Old PC

This guide is for non-technical users who want to turn a spare Windows/Linux machine into a small Minecraft Java server with Swarm Hosts.

It covers:

  • realistic prerequisites for older hardware
  • installing the Swarm Host agent
  • launching your first Minecraft server
  • network/reachability expectations
  • backup and world-file safety
  • what is and is not supported in Early Access
  • what to do when things go wrong

1) Check your old PC can handle it

At minimum, you need a machine that can run Docker reliably.

For a smooth first server on this old hardware, target:

  • 4 GB RAM minimum (8 GB for better stability)
  • 2 CPU cores minimum
  • one dedicated SSD/HDD with a free path for /data and saves (20+ GB free to start)
  • a stable power source and internet connection that stays up most of the day
  • router admin access for one forwarded port

If the machine is older than this, start with a public server test on another host and keep expectations small (fewer players, lower settings, shorter sessions).

2) Prepare the host network and machine

  • Use an Ubuntu/Debian Linux host.
  • Prefer wired ethernet over Wi-Fi.
  • Put the host on a stable local IP (for home routers this is easiest if you reserve its IP in DHCP settings).
  • Make sure no other heavy workload is running when you launch the Minecraft server.

3) Install Docker and the Swarm Host agent

Use the normal installation path first:

  1. Sign in to Swarm Hosts.
  2. Open Profile -> Agent download and copy your registration token.
  3. On the host machine, run the installer:
curl -fsSL https://swarmhosts.com/agent/install/linux.sh | sudo bash -s -- --name old-pc-host
  1. In the web UI, open Swarm hosts and confirm the host shows up.
  2. Open the host detail page and confirm heartbeats are green.

The installer creates a systemd service so the agent restarts after reboots. Use the full install guide if you need a custom data root, port range, Windows foundation setup, or manual Docker troubleshooting.

4) Make a realistic uptime plan

On older hardware, unexpected reboots are the biggest cause of player disruption.

  • Disable laptop/PC sleep while hosting.
  • Keep updates, browser downloads, and large transfers off the host.
  • Use a UPS if your area has frequent brownouts.
  • Leave the server on overnight only if your internet and power are stable.

If you lose uptime, your server appears to go offline in Swarm Hosts and players see a failed join.

5) Launch your first Minecraft Java server

  1. Open Launch.
  2. Choose Minecraft Java.
  3. Select your old PC swarm host. If it is not listed or does not look online, return to Swarm hosts and fix the agent, Docker or Podman, disk space, or data-root issue before launching.
  4. Give the server a short name.
  5. Start with conservative settings:
  6. Memory: 2048 MB on very small hosts, 3072 MB on 8 GB boxes.
  7. Max players: start at 2–4.
  8. Keep defaults you are unsure about.
  9. Click Launch.

Useful defaults for older hardware:

  • Keep VERSION on the current stable option.
  • Keep TYPE on the default and avoid heavy mod-heavy presets.
  • Keep DIFFICULTY, GAME_MODE, and world settings simple at first.

6) Verify the server is reachable

Watch these in order:

  1. Deployment status: pending_deploy → dispatched → running.
  2. Deployment detail page:
  3. player address is visible (<PUBLIC_IP>:<PORT>)
  4. public reachability badge is healthy
  5. Minecraft status check shows ready

Do not share the address until the Minecraft status check passes. For this path, a raw TCP socket can be up before the game is truly accepting players.

7) Router and firewall expectations

Even with a running deployment, players still need network access.

  • Forward exactly the assigned game port in your router to the host’s LAN IP.
  • Use the protocol shown in the deployment page for Minecraft Java (TCP on 25565 today).
  • Keep host firewall rules aligned with the host's selected port.

If you do not have public port-forwarding ability:

  • many ISPs behind CGNAT/private-only IPv4 will block inbound connections
  • you may need to use a different connection or ask support for alternatives

If you are unsure which ports to open, follow Port Forwarding Basics.

8) Backups and world files (do this before mods)

For old machines, a backup saves you from accidental deletes and bad experiments.

  • Open a deployment in Swarm Hosts and create a manual backup before changing config files.
  • Use scheduled backups as soon as you are happy with your baseline world.
  • Minecraft data lives in persistent storage in the deployment; your world files are kept under /data/world in the container.
  • For file changes, use the deployment File Manager and restart the deployment if needed.

Because old disks are often smaller, make sure backups stay small by limiting test worlds during early setup.

9) Early Access limits to plan around

Swarm Hosts is early-access for this flow. Today:

  • Minecraft Java is the flagship path.
  • advanced tuning, modpack orchestration, and custom runtime flags are intentionally limited.
  • some diagnostics are intentionally UI-first and may be less strict than a full game-client join flow.
  • behavior can change as platform confidence matures.

This means start with a simple vanilla server, validate it works end-to-end, then expand.

10) Troubleshooting and support

If status is stuck or players cannot join:

If you only need to double-check the game requirements, jump to Minecraft Java game docs.

Next action

Your next action: launch your first server with 2048 MB memory and 2–4 players, wait for running + Minecraft check pass, then perform one shared-play test with a friend from a mobile network.