Guide Minecraft

Minecraft Java Dedicated Server Setup Guide

Host Minecraft Java 26.3 on Windows using Java 25, the official server JAR and TCP 25565. Configure the firewall, router, game rules, security and backups.

Minecraft Java Edition game artwork
Source: coop-legends.de

Overview

Running a Minecraft: Java Edition 26.3 dedicated server lets your group share a world without relying on one player to keep a single-player session open. This Windows guide uses Mojang's official vanilla server JAR, Java 25, and a local-first setup process before enabling internet connections.

It also explains TCP port 25565, firewall rules, router forwarding, DS-Lite, backups, security, and recent changes to server configuration. Version: Java Edition 26.3, released September 15, 2026. Original review: September 17, 2026. These instructions are for Java Edition, not Bedrock's separate server software.

LAN, Realms or your own dedicated server?

OptionBest forDifference
LAN worldPlayers on the same local networkRuns only while the original player hosts.
RealmsA private world with managed hostingMojang handles hosting; invited players can join while the owner is offline.
Dedicated serverA persistent Java world with direct controlYou manage the files, Java, networking, updates and backups.

Mojang experimented with online P2P access to single-player worlds during Java 26.2 development, but removed that feature before release. The 26.2 friends list therefore does not replace Realms or a dedicated server.

Java and Bedrock require different servers

The Java server JAR below works with Minecraft: Java Edition. Bedrock Edition uses a different official dedicated-server application, with default ports 19132 (IPv4) and 19133 (IPv6). A vanilla Java server does not automatically allow Bedrock players to connect. A mixed-edition group needs a separate, verified compatibility setup.

If you prefer rented hosting rather than your own hardware, compare RAM, access to files, backups, mod support, update controls and administrative effort—not just the headline price.

What you need for Java 26.3

Minecraft requires Java 25 from Java Edition 26.1 onward. Mojang switched its bundled runtime to Microsoft Build of OpenJDK 25. To run the standalone server JAR, your command line also needs access to Java 25.

  • A Windows computer to host the server.
  • Java 25 installed and available in PATH.
  • The current official Minecraft Java server JAR.
  • Memory for the operating system, server and any local game client.
  • Router and Windows Firewall access if players will connect over the internet.

Mojang's download page does not prescribe one universal heap size for every world and player count. Treat any fixed -Xms/-Xmx memory figures in older guides as examples, not as universal requirements.

Install Java 25 and download the server JAR

  1. Install Java 25 from a trusted vendor such as Microsoft Build of OpenJDK.
  2. In Command Prompt or Windows Terminal, run java -version and confirm it reports Java 25. If the command is not found, fix the Java installation or PATH.
  3. Create a dedicated server directory, such as C:\MinecraftServer.
  4. Open Mojang's official Java server download page, download the server JAR and move it to that folder.
  5. Optionally rename the file to server.jar.

Use Mojang's JAR for vanilla. Paper, Fabric and NeoForge have separate setup procedures and require compatible software builds.

Start the dedicated server on Windows

Open a terminal in C:\MinecraftServer and run:

java -jar server.jar nogui

The nogui option avoids launching a graphical server interface. You can omit it if you prefer the GUI. The first run generates configuration files, including eula.txt. Read the Minecraft EULA and set its acceptance value only if you agree. Restart the server afterward.

Optional start.bat file

Create start.bat in the server folder with:

@echo off
java -jar server.jar nogui
pause

Launch using this batch file whenever you want to host. Use the server console command stop before closing it or copying world data.

Test locally before changing network settings

  1. Start the server and wait for it to finish loading.
  2. Launch Minecraft Java in the same version.
  3. From Multiplayer on the host PC, connect to localhost.
  4. Then test from another device on the LAN using the server computer's local IPv4 address, which you can find with ipconfig on Windows.

If localhost works but the LAN test fails, check the Windows network profile, server binding and firewall first. Do not change several settings at once; this makes troubleshooting less reliable.

Configure Windows Firewall and router port forwarding

Do not disable Windows Firewall. Under Windows Security → Firewall & network protection → Allow an app through firewall, permit the Java executable running your server, restricted to the necessary network profile.

For normal Java game connections over the internet, forward the configured server port to the host PC's private address:

SettingDefault
ProtocolTCP
External port25565
Internal port25565
TargetLocal IPv4 of the host PC

Reserve the host's local IP address in your router when possible, so a DHCP change does not break forwarding. Do not expose the whole computer through an unrestricted DMZ or Exposed Host rule just for Minecraft.

If external connections still fail: DS-Lite and IPv6

When LAN works but WAN does not, check whether the connection has a public IPv4 address or is behind provider NAT or DS-Lite. With DS-Lite, the relevant IPv4 NAT can take place at the provider's AFTR, where an ordinary rule on your router cannot control it. A public IPv4, suitable dual-stack configuration or usable IPv6 setup may help, depending on the provider and the players' networks.

How friends join

Friends on the same LAN use the host's local IP address. External players use the externally reachable address in Minecraft's Multiplayer → Add Server interface. With default port 25565, the address normally suffices; with a custom port, use address:port. Share a home public IP only with people who need it instead of posting it publicly.

Update server configuration for Java 26.3

Several old server.properties entries moved to Game Rules in Java 1.21.9, including:

  • pvp → pvp.
  • spawn-monsters → spawnMonsters.
  • enable-command-block → commandBlocksEnabled.
  • allow-nether → allowEnteringNetherUsingPortals.

Do not follow an old guide that simply adds pvp=false to the current server.properties. With sufficient permissions, you can use /gamerule pvp false. Java 26.2 also introduced separate spam thresholds for chat and commands, still relevant to 26.3. Generate configuration files using your current server JAR rather than copying an entire old sample.

Secure and back up your server

  • Enable the server whitelist/allowlist for a private group.
  • Give operator permissions only to trusted administrators.
  • Keep normal Minecraft authentication enabled on an internet server.
  • Expose only the ports and services actually required.
  • Leave the optional Minecraft Server Management Protocol disabled unless you need and secure it.
  • Keep the Java runtime and game server updated to compatible versions.

For a backup, stop the server cleanly with stop, then copy its directory or at least the world and configuration to a separate location. Check the archive, and make a new backup before changing the server JAR. After an update, inspect the console and test world loading and player connections before reopening the server.

Troubleshoot common problems

SymptomCheck
java is not foundJava 25 installation and PATH; try java -version.
Server stops on the first runRead eula.txt and inspect the console.
localhost failsServer process, Java, Minecraft version and console errors.
localhost works, LAN failsLocal IP, network profile and firewall.
LAN works, internet failsRouter forwarding, target IP, public IPv4, DS-Lite/provider NAT.
Incompatible versionMake clients and server use compatible Minecraft builds.

Three notable changes from older guides are the Java 25 requirement, the migration of several former properties to Game Rules, and the removal of the experimental online P2P feature before Java 26.2 was released.

Java 25. Check with java -version before starting the server JAR.

Download the official server JAR, place it in its own folder and run java -jar server.jar nogui after installing Java 25. Review and accept the EULA only if you agree.

By default, TCP port 25565. Forward the configured port only if the server needs direct internet access.

Check the router forwarding rule, local target IP and whether your provider gives you a public IPv4 address. DS-Lite or carrier NAT can block normal IPv4 forwarding.

No. The vanilla Java server does not directly support Bedrock clients; mixed-edition groups need a separate, version-checked compatibility setup.

No. You only need the server accessible on the local network and allowed through the host firewall.

Mojang moved it, along with several other settings, to Game Rules in Java 1.21.9.

Stop it first, then copy the full server directory or at minimum world and configuration files to a separate location. Check backups before making updates.

Realms handles hosting and much of server maintenance. Self-hosting offers greater control but requires you to manage networking, updates and backups.