How to self-host a Minecraft server on Linux with Paper

Install the right Java version

First, choose the Paper build you plan to run. Then check whether Java is already installed:

java -version

If you do not have the required version yet, install it with your package manager. For example, on a recent Debian or Ubuntu system:

sudo apt update
sudo apt install openjdk-21-jre-headless

That package name is an example for Paper builds that still use Java 21. If you choose a build that Paper documents as requiring Java 25, install a Java 25 runtime instead.

Verify again:

java -version

Create a dedicated server user

Do not run your Minecraft server as your normal login user or as root.

Create a dedicated system user and a home directory for server files:

sudo useradd \
  --system \
  --home /srv/minecraft \
  --create-home \
  --shell /usr/sbin/nologin \
  minecraft

Create a place for the live server and backups:

sudo mkdir -p /srv/minecraft/server
sudo mkdir -p /srv/minecraft/backups
sudo chown -R minecraft:minecraft /srv/minecraft

Download Paper

Paper publishes runnable JARs from its downloads page. Copy the exact download URL for your target version, then switch to the server user and place the file in the server directory. Naming it paper.jar keeps later commands simple:

sudo -u minecraft -H bash
cd /srv/minecraft/server
curl -Lo paper.jar "<paper-download-url>"

You now have the server binary, but the rest of the server files do not exist yet. The first start creates them.

Run the server once and accept the EULA

Start the server once so Paper can generate the working directory:

cd /srv/minecraft/server
java -Xms2G -Xmx4G -jar paper.jar --nogui

The first run stops because the EULA has not been accepted yet. Edit eula.txt and change eula=false to eula=true:

sed -i 's/^eula=false$/eula=true/' /srv/minecraft/server/eula.txt

At this point you also have server.properties, logs/, plugins/, and the world folders on disk.

Create a start script

You can start the server with a long Java command every time, but it is cleaner to put that command in a script.

Create /srv/minecraft/server/start.sh with content like this:

#!/usr/bin/env bash
cd /srv/minecraft/server
exec java -Xms2G -Xmx4G -jar paper.jar --nogui

Then make it executable:

chmod +x /srv/minecraft/server/start.sh

Two quick notes here:

• Xmx is the maximum heap the JVM can use
• more RAM is not always the answer to lag, especially if your single-core CPU performance is weak
• do not set Xmx right up against a VPS, container, or panel memory limit

If you are hosting a small friends-only server, start conservatively and increase memory only when you have evidence that you need it. If the host gives the process a hard memory limit, leave room for Java outside the heap and for the operating system. Paper's troubleshooting docs call out crashes where the memory limit is too close to -Xmx.

Run the server with systemd

systemd is a better long-term setup than manually keeping the process alive in a shell window.

Create /etc/systemd/system/minecraft.service:

[Unit]
Description=Minecraft Paper Server
After=network.target

[Service]
User=minecraft
Group=minecraft
WorkingDirectory=/srv/minecraft/server
ExecStart=/srv/minecraft/server/start.sh
Restart=on-failure
RestartSec=10
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target

Reload systemd, enable the service, and start it:

sudo systemctl daemon-reload
sudo systemctl enable --now minecraft

Useful commands from here on:

sudo systemctl status minecraft
sudo journalctl -u minecraft -f
sudo systemctl restart minecraft
sudo systemctl stop minecraft

Open the game port

For Minecraft Java, the default server port is 25565/TCP unless you changed it in server.properties.

If you use ufw, open that port:

sudo ufw allow 25565/tcp

If this server lives behind a home router, you also need to forward 25565/TCP from the router to the machine's local LAN IP.

If this server lives on a VPS, you usually do not need "port forwarding" at all. You need an inbound firewall or security-group rule that allows 25565/TCP.

Set the basics in server.properties

Before inviting people, open server.properties and set the obvious items:

• motd
• difficulty
• gamemode
• max-players
• view-distance
• simulation-distance
• white-list

Two defaults matter more than people think:

• Keep online-mode=true unless you fully understand the security tradeoff.
• Turn the allow list on if this is meant to be a private server.

A few server.properties fields deserve extra care:

Use Paper's server.properties reference when you are unsure what a field actually controls.

Install plugins carefully

Paper becomes much more useful once you add plugins, but plugin quality varies a lot.

A few practical rules:

• add one plugin at a time when the server is new
• keep a copy of the plugin JAR and its config before large changes
• restart only after you know what changed
• track your plugin versions alongside your Minecraft version

The messy part of Minecraft administration often starts here, not at the Java install step.

Back up the right things

At minimum, back up:

• the world folders
• plugins/
• server.properties
• any plugin-specific config that matters to your economy, permissions, or moderation flow

For a small server, a simple first pass is enough:

1. stop the server cleanly
2. archive /srv/minecraft/server
3. copy the archive to another disk or object store

Do not treat "the disk is still there" as a backup strategy.

Update without making a mess

Paper updates are usually straightforward, but major Minecraft upgrades still deserve caution.

A safe update flow looks like this:

1. Take a backup.
2. Read the Paper and plugin changelogs for your target version.
3. Replace paper.jar with the new build.
4. Start the server and watch the console closely.
5. Check that plugins, permissions, and world loading all behave normally.

If you jump across major Minecraft versions, expect at least some plugin churn.