Game Servers
How to Make a Minecraft Server for Friends (UK Guide, 2026)
By Adam Eastwood · · 9 min read
Quick answer
To make a Minecraft server: install Java 21, download the server software (vanilla or Paper), accept the EULA, and launch it with allocated RAM. Friends on your network can join immediately; for friends elsewhere you must either port forward 25565 on your router or rent a hosted server, which skips networking entirely.
Setting up a private Minecraft server for your friend group is one of the most satisfying projects in gaming — your own world, your rules, no strangers. The software side takes about fifteen minutes. The part that trips most people up is the networking: getting friends outside your house connected, which on many UK broadband connections is harder than it should be. This guide covers both paths: hosting on your own PC, and renting a server.
If you already know you don't want to leave a PC running or fight your router, a hosted Minecraft server gives you the same result — an address your friends type in and join — without any of the port-forwarding steps below. Otherwise, let's build it by hand.
What do you need before you start?
- Java 21 — Minecraft 1.20.5 and later require Java 21. Download Temurin (Adoptium) or another OpenJDK build. Older versions of the game need older Java, so match Java to your target Minecraft version.
- A machine to run it on — a spare PC or your gaming PC with at least 8GB of total RAM if you also want to play on the same machine. The server needs 2–4GB to itself for a small group.
- Server software — the official vanilla jar from minecraft.net works fine; most people use Paper instead because it performs better and supports plugins while staying compatible with vanilla clients.
How do you set up the server software?
- Make a folder for the server (e.g.
C:\mc-server) and put the server jar in it. Everything the server creates — world, configs, logs — lands in this folder. - Run it once from a terminal in that folder:
java -Xmx4G -Xms4G -jar server.jar nogui. It will exit immediately having writteneula.txt. - Accept the EULA — open
eula.txtand changeeula=falsetoeula=true. - Start it again with the same command. First launch takes a minute or two while it generates the world. When you see “Done” in the console, the server is live. Save the command as a
.batfile (Windows) or.shscript (Linux/macOS) so you can start it with a double-click. - Test it yourself — open Minecraft on the same machine, add a multiplayer server with the address
localhost, and join.
A few server.properties settings worth changing straight away: set white-list=true and add your friends with whitelist add TheirName in the console so strangers can never join; set view-distance=8 if the machine is modest; and give yourself operator rights with op YourName.
How do friends join your server?
This is where the two situations diverge, and it is worth understanding why. Friends on the same network (same house, same Wi-Fi) can join right away using your PC's local IP address — find it with ipconfig on Windows (look for “IPv4 Address”, usually something like 192.168.1.x).
Friends on the internet cannot reach that address, because your router hides your whole home network behind one public IP. To let them in, you must tell the router to forward Minecraft traffic to your PC — port forwarding — or sidestep the problem entirely with a tunnel or a rented server.
How does port forwarding work?
- Give your PC a fixed local IP. Either reserve its address in the router's DHCP settings or set a static IP on the PC. If the PC's local address changes, your forwarding rule silently breaks.
- Log in to your router — typically at
192.168.1.1or192.168.0.1; UK ISP routers usually print the admin password on a sticker on the unit. - Add a forwarding rule for external port
25565(TCP) pointing to your PC's local IP, port25565. Some router interfaces call this “virtual server” or “NAT rules”. - Allow Java through the firewall — on Windows, accept the firewall prompt on first launch or add an inbound rule for port 25565.
- Share your public IP — search “what is my IP” and give friends that address. If your ISP rotates your public IP, a free dynamic-DNS name saves you re-sharing it every few weeks.
The CGNAT problem on UK broadband
Here is the catch nobody mentions: a growing number of UK ISPs put customers behind carrier-grade NAT (CGNAT), meaning you share a public IP with other households and inbound connections can never reach you — port forwarding simply will not work, no matter how correctly you configure it. This is common on some full-fibre and mobile-broadband providers. The tell-tale sign: the “WAN IP” shown in your router (often starting 100.x) differs from the IP a “what is my IP” site shows you. Your options are to ask the ISP for a static or non-CGNAT IP (some offer it free or for a small monthly fee, as of August 2026), use a tunnelling tool such as playit.gg or a VPN with port forwarding, or move the server somewhere with a real public IP — which is exactly what a hosting company provides.
Should you self-host or rent a server?
Both are legitimate. The honest trade-offs:
| Self-hosting at home | Rented server | |
|---|---|---|
| Up-front cost | Free if you have the hardware | A few pounds per month |
| Running cost | Electricity for a PC left on (a gaming PC running 24/7 adds a noticeable amount to a UK electricity bill) | Flat monthly price |
| Availability | Only online while your PC is on | Online 24/7 — friends play while you're out |
| Networking | Port forwarding, dynamic IP, possible CGNAT wall | Public address included, nothing to configure |
| Performance | Shares CPU/RAM with your game if it's the same PC | Dedicated resources for the server |
| Control | Total — it's your machine | Panel access, console, file manager, mod installers |
The pattern we see: self-hosting is brilliant for LAN parties, weekend-only worlds, and learning how servers work. Groups that want a world that is always there — where someone can hop on at lunchtime while the usual host is at work — end up renting, because the always-on electricity cost and the networking friction outweigh a small monthly fee.
Keeping your server healthy
- Back up the world folder regularly — a copy of the
worlddirectory (plusworld_netherandworld_the_endon Paper) is a complete backup. Do it before every Minecraft version upgrade, without exception: worlds upgrade forwards but never backwards. - Keep the whitelist on. Open servers get found by scanners within hours, and griefers follow.
- Restart daily if you can — a scheduled restart clears entity build-up and memory fragmentation on long-running worlds.
- Upgrade deliberately — wait for your plugins or mods to support a new Minecraft version before jumping on it.
The bottom line
Making the server is easy: Java 21, server jar, accept the EULA, run. Getting friends in from outside is the real decision point. If your ISP gives you a proper public IP and you don't mind leaving a machine on, port forwarding costs nothing and works well. If you hit the CGNAT wall, or you want the world online around the clock, rent a small hosted server, start with 4GB (see our RAM requirements guide), whitelist your friends, and spend your evening playing instead of staring at router settings.
