What you need
- Windows 10 or 11, 64-bit. The current FerNode build targets Windows x64.
- Java 17 or newer. Java 21 LTS is a good default for current Paper builds.
- 4 GB of RAM minimum. 8 GB is more comfortable if you plan to run plugins or a few friends.
- Free disk space. A small world plus backups fits in a few GB, but leave room to grow.
- A wired or stable connection if other people will join from outside your network.
Hosting from home is fine for friends. For a public server that must stay online, a paid Minecraft host is usually cheaper than leaving a PC running all day.
1. Install Java and check it
Install a 64-bit Java 21 build, such as Eclipse Temurin. During installation, enable the
option that adds Java to PATH. Then open PowerShell and run:
java -version
You should see a version line starting with 17, 21 or newer.
If Windows reports that Java is not recognized, the install did not add it to
PATH; reinstall with that option or point FerNode at the Java executable
manually.
2. Download FerNode and verify it
Use the download panel. The portable ZIP is the
simplest option: extract it to a short path such as C:\FerNode and run the
app. The installer is convenient if you want a Start menu entry.
The download panel publishes a SHA-256 checksum. To compare it in PowerShell:
Get-FileHash .\Server-Tool-1.2.1-win-x64.zip -Algorithm SHA256The hash must match the value shown on the site exactly. If it does not, delete the file and download it again. Windows SmartScreen may warn about an unsigned app; only continue when the hash matches and the file came from the official release page.
3. Create the server
Open FerNode and create a new server. Give it a name, choose Paper, pick the Minecraft version you want, and select an empty folder for the server files. Keep the path simple:
C:\Minecraft\SurvivalAvoid a folder inside OneDrive or another syncing service. Sync tools can lock files while the server is writing them and corrupt a world.
Allocate memory based on the whole machine, not just the server. Leave at least 2 GB for Windows. A useful starting point is 4 GB for a small vanilla-style server and 6–8 GB if you add plugins or several players.
4. Accept the EULA and start once
Minecraft servers require you to accept the Mojang EULA before the first successful
start. FerNode shows the prompt and writes eula=true to
eula.txt after you accept. If you start the server outside the app, edit
eula.txt yourself.
Start the server and watch the console. The first run generates the world, which can
take a minute. Wait for a line containing Done before you connect. If the
console closes immediately, read logs/latest.log for the actual error.
5. Join the server
On the same PC, open Minecraft and connect to localhost. On another device
on the same network, use the PC's IPv4 address. Find it with:
ipconfig
Use the address next to the active adapter, for example 192.168.1.20. If
Windows Firewall prompts you, allow Java on private networks. Do not allow it on public
networks unless you understand the risk.
For friends outside your network, forward TCP port 25565 on your router to
the PC's local address. Give them your public IP, not the 192.168.x.x
address. If your ISP uses carrier-grade NAT, port forwarding will not work and you will
need a tunnel or a hosted server instead.
6. Tune the basics before inviting people
Open server.properties while the server is stopped. These settings keep a
small server stable:
| Setting | Suggested | Why |
|---|---|---|
view-distance | 8 | Lower values reduce CPU and bandwidth; raise it only if you have headroom. |
simulation-distance | 6 | Controls how far farms and mobs tick; lower values help on small machines. |
online-mode | true | Verifies Minecraft accounts. Keep it on unless you run a proxy. |
white-list | true | Only approved players can join. Add yourself before enabling it. |
max-players | 5–10 | A realistic limit for the RAM you allocated. |
Add yourself to the whitelist with whitelist add YourName in the console,
then run whitelist on. Test with a second account or a friend before you
announce the address.
7. Back up before you need to
A backup only counts if you have restored one. Stop the server, copy the world folders
and plugins/ somewhere else, then start the server again. Repeat on a
schedule you will actually keep, and keep at least one copy off the machine.
FerNode can take backups from its dashboard. Use them, but also keep a manual copy before major changes such as a Minecraft version upgrade or a plugin replacement.
8. Security basics
- Do not run the server as a Windows administrator.
- Use
online-mode=trueand a whitelist on any server that is reachable from the internet. - Give operator status only to people who need it.
- Keep Java, Paper and plugins updated, and read release notes before jumping versions.
- Never share your console, hosting panel or remote access credentials.
What is inside the server folder
The first start creates a set of files and folders. Knowing what each one is prevents most accidental damage later.
| Item | What it is |
|---|---|
server.jar | The server software. Replacing it is how you change version or platform. |
eula.txt | Records that you accepted the Mojang EULA. |
server.properties | Ports, whitelist, view distance and the other server-wide settings. |
world/ | The overworld. The Nether and End use separate folders. |
plugins/ | Plugin JARs and, after first start, one config folder per plugin. |
logs/ | Session logs. The first place to look when something fails. |
config/ | Paper's own configuration files, when present. |
ops.json, whitelist.json | Operators and whitelisted players. |
crash-reports/ | Reports written when the server crashes hard. |
Deleting a world folder deletes that world. Renaming it is a safer way to "start over": the server generates a fresh world with the new name while the old one stays on disk.
Paper, Spigot or Vanilla?
FerNode creates Paper servers by default because Paper runs Spigot plugins and performs better under load. Spigot is the compatibility baseline and is the right choice only when a plugin explicitly requires it. Vanilla has no plugin support at all.
Switching later is mostly a matter of replacing the server JAR for the same Minecraft version. See the server software comparison before you move a world between them.
Your first week
- Take a backup before inviting anyone. A fresh world is easy to lose and easy to protect.
- Test a restore. Copy the world to another folder and start a server from it on a different port.
- Watch the console at peak time. Look for
Can't keep upwarnings and plugin errors. - Add a permissions plugin before you add staff. Operator status should be rare.
- Write down the Java, Paper and plugin versions. You will need them for bug reports.
- Decide an update policy. Update on a schedule, not the hour a new version releases.
Most first-week problems are configuration, not hardware. Read the log before you buy more RAM, and change one setting at a time so you know what helped.
If the first start fails
A first start that closes immediately is almost always one of four problems. Read the last few lines of the console before it exits, then match it here.
| Symptom | Likely cause | Fix |
|---|---|---|
| "Java is not recognized" | Java is missing or not on PATH. | Install a 64-bit JDK and select its executable in FerNode. |
| "You need to agree to the EULA" | eula.txt is missing or false. | Accept the EULA once; the file should contain eula=true. |
| "Address already in use" | Another server or program holds the port. | Stop the other process or change server-port. |
| Console stops with no "Done" | World generation or a plugin error. | Wait a minute, then read logs/latest.log for the first error. |
Do not fix these by deleting files at random. Each message points at a specific cause, and the log keeps the detail that the console scrolls past. If the window closes too quickly to read, start the server from a terminal so the output stays visible.