{"id":409,"date":"2026-08-31T13:04:54","date_gmt":"2026-08-31T13:04:54","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=409"},"modified":"2026-08-31T09:31:15","modified_gmt":"2026-08-31T09:31:15","slug":"how-to-set-up-minecraft-server-on-vps","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/en\/how-to-set-up-minecraft-server-on-vps\/","title":{"rendered":"How to Set Up a Minecraft Server on a VPS"},"content":{"rendered":"
Table of Contents<\/strong><\/p>\n
    \n
  1. Before you put Minecraft on a VPS<\/a><\/li>\n
  2. CPU and RAM are only starting points<\/a><\/li>\n
  3. Prepare the VPS without doing everything as root<\/a><\/li>\n
  4. Install a Java version that fits the server<\/a><\/li>\n
  5. Download and start Paper<\/a><\/li>\n
  6. Heap size, view distance, and actual performance<\/a><\/li>\n
  7. Let systemd own the process<\/a><\/li>\n
  8. Open only the required network ports<\/a><\/li>\n
  9. Give players a hostname<\/a><\/li>\n
  10. Whitelist first, plugins second<\/a><\/li>\n
  11. A running world is not a backup<\/a><\/li>\n
  12. Monitor the game, not just the port<\/a><\/li>\n
  13. Check these before sharing the address<\/a><\/li>\n
  14. Questions I hear often<\/a><\/li>\n<\/ol>\n<\/div>\n

    Before you put Minecraft on a VPS<\/h2>\n

    The first few players rarely expose a Minecraft server’s limits. Five minutes later, three of them may be exploring different chunks, generating new terrain while a plugin saves data and the operating system waits on storage. That is when a VPS that looked comfortably sized starts feeling very small.<\/p>\n

    I plan the resources before downloading the server JAR. The examples below use Ubuntu Server 24.04 LTS, Minecraft Java Edition 1.21.x, and Paper. Paper is a sensible choice when you want plugin support and useful performance settings without straying too far from vanilla Minecraft. If you choose vanilla, the JAR name and start command change; the user, firewall, and backup work still apply.<\/p>\n

    CPU and RAM are only starting points<\/h2>\n

    Minecraft is sensitive to single-thread CPU performance. One world’s main game loop may not benefit much from a provider’s “8 vCPU” label, especially when those virtual CPUs are shared. I check the provider’s CPU policy, processor generation, and storage type instead of counting cores alone.<\/p>\n

    My own 10 Essential Steps to Secure and Harden Your Linux Server<\/a><\/em> checklist starts with choosing an environment I can understand and monitor.<\/p>\n\n\n\n\n\n\n\n\n
    Players and usage<\/th>\nSuggested RAM<\/th>\nNotes<\/th>\n<\/tr>\n<\/thead>\n
    2-5 players, few plugins<\/td>\n2 GB<\/td>\nPossible with a new world and a low view distance<\/td>\n<\/tr>\n
    5-10 players, Paper<\/td>\n4 GB<\/td>\nA reasonable starting point for a small friends-only server<\/td>\n<\/tr>\n
    10-20 players, plugins<\/td>\n6-8 GB<\/td>\nWatch world generation and plugin behavior closely<\/td>\n<\/tr>\n
    Modpack or busy world<\/td>\n8 GB and above<\/td>\nAccount for the mods’ memory requirements separately<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    These are starting points, not promises. World generation, view distance, mob counts, and plugin behavior can matter as much as player count. If the VPS runs other services, physical RAM is not all available to Minecraft.<\/p>\n

    On a 4 GB VPS, I normally leave roughly 700 MB to 1 GB for the operating system, SSH, monitoring, and filesystem cache. Setting the Java heap to -Xmx3G<\/code> may look efficient, but allocating nearly everything to Java can push the machine into swap. If you need swap, see How to Create Swap Space on a VPS for Linux Memory Management<\/a><\/em>. Swap is not RAM.<\/p>\n

    Prepare the VPS without doing everything as root<\/h2>\n

    Logging in as root and running every command directly is convenient. It also makes a bad plugin or an incorrect command much more dangerous. I create a separate account for the Minecraft process and keep administrative work separate from game data.<\/p>\n

    ssh root@SERVER_IP\napt update && apt full-upgrade -y\napt install -y sudo\nadduser --disabled-password --gecos \"\" minecraft\nusermod -aG sudo minecraft\nhostnamectl set-hostname mc-01<\/code><\/pre>\n
    Replace mc-01<\/code> with your own hostname. My production prompts are red, and my test machines have distinct hostnames. I once got within one keystroke of running rm -rf<\/code> on the wrong server; the hostname in the terminal stopped me. Since then, checking the hostname has been a pre-flight check, not a vague good habit.<\/p>\n
    If you use SSH keys, copy yours to the new account:<\/p>\n
    ssh-copy-id minecraft@SERVER_IP<\/code><\/pre>\n
    Do not disable root SSH access until you have tested a separate session as minecraft<\/code>. After that test succeeds, restrict root and password authentication in \/etc\/ssh\/sshd_config<\/code>:<\/p>\n
    PermitRootLogin no\nPasswordAuthentication no<\/code><\/pre>\n
    Validate the configuration before applying it:<\/p>\n
    sshd -t && systemctl reload ssh<\/code><\/pre>\n
    Changing the SSH port is not security by itself. I prefer fail2ban and nftables, while still reading the logs to see what actually reaches the server. The Minecraft port will be public, so do not skip the checks in 10 Essential Steps to Secure and Harden Your Linux Server<\/em>.<\/p>\n
    Install a Java version that fits the server<\/h2>\n
    The Java version must match the Minecraft and Paper versions. For Minecraft 1.20.5 and later, Java 21 is the normal starting point for the Paper releases I use. Check the release notes for your exact build before installing anything.<\/p>\n
    apt install -y openjdk-21-jre-headless curl wget unzip ufw\njava -version<\/code><\/pre>\n
    The output should show Java 21, for example openjdk version \"21.0.x\"<\/code>. Minecraft 1.20.4 and older commonly use Java 17, but the server and Paper documentation should decide the final version.<\/p>\n
    The JRE is enough to run the server. There is no need for a full JDK unless you have another task that actually requires one.<\/p>\n
    Download and start Paper<\/h2>\n
    Switch to the Minecraft account and create a dedicated working directory. This layout makes version changes and backups less confusing.<\/p>\n
    su - minecraft\nmkdir -p \/home\/minecraft\/server\ncd \/home\/minecraft\/server\nwget -O paper.jar 'PAPER_DOWNLOAD_URL'\nls -lh paper.jar<\/code><\/pre>\n
    Replace PAPER_DOWNLOAD_URL<\/code> with the download link for your selected Minecraft version from Paper’s official download page. I am not hard-coding a URL because Paper releases change. Do not run a random JAR because its filename looks familiar; compare its SHA-256 checksum with the published value.<\/p>\n
    sha256sum paper.jar<\/code><\/pre>\n
    If the value does not match, stop there. This check takes seconds.<\/p>\n
    The first start creates the EULA file and normally exits immediately:<\/p>\n
    cd \/home\/minecraft\/server\njava -Xms2G -Xmx3G -jar paper.jar --nogui<\/code><\/pre>\n
    Read the EULA. If you accept it, update the value:<\/p>\n
    sed -i 's\/^eula=false$\/eula=true\/' eula.txt<\/code><\/pre>\n
    Start the server again and wait for the world to generate. Initial map generation can produce a short burst of CPU and disk activity, so do not judge the VPS from that first minute alone.<\/p>\n
    Heap size, view distance, and actual performance<\/h2>\n
    -Xms<\/code> sets the initial Java heap, while -Xmx<\/code> sets its upper limit. They do not have to be identical on a small VPS. Leave room for the operating system.<\/p>\n
    On a 4 GB machine, I usually begin with -Xms2G -Xmx3G<\/code>. On an 8 GB machine, I might allocate 5-6 GB, depending on the plugins and player count. More heap does not fix every performance problem. If the main CPU thread cannot keep up with chunk generation, adding another 4 GB will not repair the TPS.<\/p>\n
    These are conservative starting values in server.properties<\/code>:<\/p>\n
    view-distance=8\nsimulation-distance=6\nonline-mode=true\nmotd=Friends' Minecraft Server\nmax-players=10<\/code><\/pre>\n
    view-distance<\/code> controls how many chunks are sent to a player. simulation-distance<\/code> controls the area where entities, redstone, and similar mechanics remain active. Raising both without a reason increases CPU work, especially on a small VPS.<\/p>\n
    When performance is poor, measure before changing settings. Check Paper’s timings or profiling tools alongside CPU load, memory pressure, disk activity, and player movement. I have seen “the server needs more RAM” become the diagnosis simply because someone looked at memory usage and stopped there.<\/p>\n
    Let systemd own the process<\/h2>\n
    Leaving an SSH session open with java<\/code> running in the terminal is fine for testing, not for a live server. tmux<\/code> can preserve a session when SSH drops (I moved away from screen<\/code> years ago), but systemd gives the service a proper boot sequence, restart policy, and log location.<\/p>\n
    Create the service file as root:<\/p>\n
    exit\nvim \/etc\/systemd\/system\/minecraft.service<\/code><\/pre>\n
    [Unit]\nDescription=Minecraft Paper Server\nAfter=network-online.target\nWants=network-online.target\n\n[Service]\nUser=minecraft\nGroup=minecraft\nWorkingDirectory=\/home\/minecraft\/server\nExecStart=\/usr\/bin\/java -Xms2G -Xmx3G -jar paper.jar --nogui\nRestart=on-failure\nRestartSec=10\nTimeoutStopSec=60\n\n[Install]\nWantedBy=multi-user.target<\/code><\/pre>\n
    User=minecraft<\/code> matters. The server does not run as root, so a vulnerability in Paper or a plugin does not automatically grant unrestricted access to the operating system. It is not a complete security boundary, but removing unnecessary privileges still helps.<\/p>\n
    systemctl daemon-reload\nsystemctl enable --now minecraft\nsystemctl status minecraft --no-pager<\/code><\/pre>\n
    You should see active (running)<\/code>. If it fails, do not restart it repeatedly. Read the logs:<\/p>\n
    journalctl -u minecraft -n 100 --no-pager\njournalctl -u minecraft -f<\/code><\/pre>\n
    While repairing a server that failed to boot after a kernel update, I had to work through rescue mode and chroot<\/code>. That incident reminded me to take a snapshot before a significant change. I do that before Java or plugin updates now.<\/p>\n
    Open only the required network ports<\/h2>\n
    Minecraft Java Edition uses TCP 25565<\/code> by default. Open only the traffic you need with UFW:<\/p>\n
    ufw default deny incoming\nufw default allow outgoing\nufw allow OpenSSH\nufw allow 25565\/tcp\nufw enable\nufw status verbose<\/code><\/pre>\n
    If SSH uses a non-standard port, replace OpenSSH<\/code> with the actual port rule. Before enabling the firewall, verify a second SSH connection without closing the current one. Otherwise, you can lock yourself out of the VPS.<\/p>\n
    Bedrock players need more than a Java server. A bridge such as GeyserMC and usually a UDP port are required. If you are serving Java Edition only, do not open an unnecessary UDP rule.<\/p>\n
    Give players a hostname<\/h2>\n
    An address such as mc.example.com<\/code> is easier to share than an IP address. Add an A record pointing that name to the VPS IPv4 address. If you use IPv6, check that the AAAA record points to the intended server; a wrong AAAA record can affect only some players, which makes the problem particularly annoying.<\/p>\n
    dig +short A mc.example.com\ndig +short AAAA mc.example.com<\/code><\/pre>\n
    When DNS is involved, I go to the terminal before the control panel. If dig +short<\/code> does not return the address you expect, changing Minecraft settings will not help. If the server uses a non-default port, players must connect with an address such as mc.example.com:25570<\/code>. An SRV record can hide the port, but an A record is simpler for a first setup.<\/p>\n
    Whitelist first, plugins second<\/h2>\n
    When the server is running, use its console to grant yourself operator access and enable the whitelist:<\/p>\n
    op PLAYER_NAME\nwhitelist on\nwhitelist add PLAYER_NAME\nsave-all<\/code><\/pre>\n
    A whitelist prevents unknown players from entering a private world. Give OP privileges only to accounts that need them. Plugin administrators are not root, either; a malicious or outdated plugin can still damage every file the Minecraft user can access. Do not test an unknown JAR on a live server.<\/p>\n
    Paper plugins go in \/home\/minecraft\/server\/plugins<\/code>:<\/p>\n
    install -d -o minecraft -g minecraft \/home\/minecraft\/server\/plugins\nsystemctl stop minecraft\ncp plugin.jar \/home\/minecraft\/server\/plugins\/\nchown minecraft:minecraft \/home\/minecraft\/server\/plugins\/plugin.jar\nsystemctl start minecraft<\/code><\/pre>\n
    Run these commands with root privileges. Add plugins one at a time so you know which change caused a problem. If you want container-based management, see How to Install Docker on a VPS and Run Your First Container<\/a><\/em>. Docker does not remove the need to understand Java, storage, or backups.<\/p>\n
    A running world is not a backup<\/h2>\n
    A Minecraft world contains hours of other people’s work. Disk failure, a bad plugin, a corrupted chunk, or an abusive player can make it unusable.<\/p>\n
    For a consistent backup of a small server, I prefer saving the world and briefly stopping the service:<\/p>\n
    systemctl stop minecraft\ntar -czf \/var\/backups\/minecraft-$(date +%F).tar.gz \n  -C \/home\/minecraft\/server world world_nether world_the_end server.properties whitelist.json ops.json\nsystemctl start minecraft<\/code><\/pre>\n
    This creates a local archive. A file on the same VPS will not save you if the VPS disappears. Copy it to external storage with rsync or borgbackup, then test the restore. A backup that has never been restored is only a hopeful pile of bytes.<\/p>\n
    Once a month, I extract one archive into a temporary directory and check that the world files are present and readable. Testing is part of taking the backup.<\/p>\n
    You can automate this with cron, but check the schedule twice. I once added an extra asterisk to a cron entry; the backup script ran every minute and a mail queue grew behind it. A tiny syntax mistake can turn into an expensive night in systems administration.<\/p>\n
    Monitor the game, not just the port<\/h2>\n
    Uptime Kuma can tell you whether the port responds. It cannot tell you whether the game is running well. Sending CPU, RAM, disk usage, and disk latency to Prometheus with node_exporter, then viewing them in Grafana, gives a more useful picture.<\/p>\n
    In my homelab, a failing fan once made the temperature graph climb in steps. The graph warned me before the players did.<\/p>\n
    To inspect disk usage:<\/p>\n
    df -h\nncdu -x \/home\/minecraft\/server<\/code><\/pre>\n
    The -x<\/code> flag matters: ncdu<\/code> stays on the same filesystem instead of wandering into mounted paths. If the world directory grows unexpectedly, inspect world generation, log files, and plugin caches.<\/p>\n
    If the service is running but nobody can connect:<\/p>\n
    systemctl status minecraft --no-pager\nss -ltnp | grep 25565\nufw status\nmtr -rwzbc 20 mc.example.com<\/code><\/pre>\n
    The ss<\/code> output should show Java listening on the port. If the port is listening, the firewall is open, and DNS is correct, use mtr<\/code> to inspect the network path. Packet loss at an intermediate hop is not automatically a Minecraft problem; some routers limit ICMP responses.<\/p>\n
    When players say “there is lag,” separate TPS, CPU load, and network latency. Lowering view distance may reduce CPU pressure, but it will not fix high ping. Adding RAM will not remove an entity flood caused by a broken plugin.<\/p>\n
    Check these before sharing the address<\/h2>\n
      \n
    • Does the Java version match the Minecraft and Paper versions?<\/li>\n
    • Does the server run as minecraft<\/code> instead of root?<\/li>\n
    • Will it start after a reboot with systemctl enable minecraft<\/code>?<\/li>\n
    • Does UFW expose only SSH and the required Minecraft port?<\/li>\n
    • Is the whitelist enabled, with OP accounts limited?<\/li>\n
    • Do you have an external backup that has been restored successfully?<\/li>\n
    • Do you have alerts for CPU, RAM, disk usage, and service status?<\/li>\n<\/ul>\n
      If you cannot answer yes to all of these, wait before announcing the server. I still catch myself saying “it works for now” and postponing monitoring or backups. That is how a small maintenance task becomes a night shift.<\/p>\n
      Questions I hear often<\/h2>\n
      How much RAM does a Minecraft server need?<\/h3>\n
      A Java server for 2-5 players with few plugins can start with 2 GB, but the operating system also needs memory. As player count, mods, view distance, and world generation grow, 4 GB or more may be necessary.<\/p>\n
      Which Java version should I use for a Minecraft VPS?<\/h3>\n
      Minecraft 1.20.5 and newer versions generally use Java 21, while older versions commonly use Java 17. Confirm the exact version in the relevant Paper notes and the server startup output.<\/p>\n
      How do I point a domain name to a Minecraft server?<\/h3>\n
      Add an A record for the subdomain pointing to the VPS IPv4 address. If the server uses a port other than 25565, players must append the port or you must configure a suitable SRV record.<\/p>\n
      Can I back up the server without stopping it?<\/h3>\n
      Yes, but a copy taken while the world is being written may be inconsistent. On a small server, save-all<\/code> followed by a short stop is safer; more advanced setups can use filesystem snapshots and restore tests.<\/p>\n
      For me, setup is not finished when the first player connects. It is finished when the server starts after a reboot and a backup has successfully come back. I do not send the IP to the group chat until both tests pass.<\/p>\n","protected":false},"excerpt":{"rendered":"
      A practical walkthrough for setting up a Paper Minecraft Java server on an Ubuntu 24.04 VPS, with resource planning, security, systemd, DNS, and tested backups.<\/p>\n","protected":false},"author":2,"featured_media":407,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[1479,43,1470,1473,687,1482,1476,29],"class_list":["post-409","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hosting","tag-java-en","tag-linux","tag-minecraft-server","tag-paper-en","tag-server-administration","tag-systemd","tag-ubuntu-server","tag-vps"],"lang":"en","translations":{"en":409,"tr":408},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/409","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=409"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/409\/revisions"}],"predecessor-version":[{"id":411,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/409\/revisions\/411"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/407"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}