
Hosting a modded Minecraft server is not the same as hosting a plain one. A single wrong version, a missing dependency or a client-only mod in the wrong folder is enough to make the server refuse to start, or let players join and crash a minute later. The good news is that nearly every modded-server failure comes from the same short list of causes. If you follow the steps in order, you can avoid almost all of them.
This guide covers modded Java servers using Forge, NeoForge or Fabric: how to match versions, which Java you need, how to use a server pack, how to size memory, and how to read the logs when something breaks.
A working modded server depends on three versions lining up. Write them down before you upload anything.
| Minecraft version | Java you need |
|---|---|
| 1.17 | Java 16 |
| 1.18 to 1.20.4 | Java 17 |
| 1.20.5 and newer | Java 21 |
| 1.16 and older | Usually Java 8 |
If you see an UnsupportedClassVersionError in the console, the Java version is almost always the reason. Choose the right Java in your panel's startup settings and try again.
Not sure which loader fits your plan? Our comparison of Paper, Fabric, Forge and Vanilla explains how they differ. A short summary: use Fabric or Forge/NeoForge for mods, and use Paper for plugin-based servers.
An existing modpack is the easier route. Popular modpacks are published on platforms like CurseForge and Modrinth, and most provide a server pack, a download prepared for servers.
Your own mod list gives you control, but you take on version matching yourself. If you are new, start with an existing modpack and customise later.
This is the single most common mistake. The normal modpack download is made for the player's game. It can contain client-only mods such as shaders, minimaps and UI mods that do not belong on a server and can crash it.
In your game panel:
mods folder. Do not mix Forge and Fabric mods in the same folder.eula=false to eula=true in eula.txt.The first start of a modded server is much slower than a vanilla one, because the loader processes every mod and generates the world. Be patient and watch the console until it reports the server is done.
Modded servers use more memory than vanilla, and the amount depends heavily on the pack. As a rough starting point, not a rule:
Two practical points:
Our RAM guide goes deeper on sizing. Heavy modpacks are also demanding on the processor, so read why CPU performance matters before choosing a plan. Larger packs often fit better on the Premium plans with stronger processors, while a small modded SMP can start on a Budget plan.
Your players must run the same modpack and version as the server. Give them the exact name and version, plus the server address and port from your panel.
If a player cannot join, the error usually says what is missing or different. Common messages:
Keep online-mode=true and turn on the whitelist while you test. Our setup guide explains these server.properties settings.
Do not guess. The answer is almost always in the logs.
logs/latest.log shows what happened during the last run, including mod loading errors.crash-reports/ contains a detailed report if the server crashed.When the server fails to start, scroll to the first error, not the last. The first error is usually the root cause and the rest are consequences. Typical findings:
mods folder.If you change several mods at once, you will not know which one fixed or broke things. Make one change, restart, and check.
Modded worlds are fragile. Removing a mod can delete the blocks and items it added, and updating a mod can change how its data is saved.
Large modpacks add heavy machinery, farms and entities. Once the server runs, watch performance. Pre-generate the area around spawn with a pre-generation mod or plugin, set a world border, and use a profiler to find slow mods. We explain the whole process in how to find and fix Minecraft server lag with spark.
latest.log.It depends on the pack. Small mod lists can run on around 4 to 6 GB, while larger packs often need 8 GB or more. Check the pack's recommendation and watch memory use in your panel.
The most common causes are the wrong Java version, a missing dependency, two conflicting mods, or a client-only mod on the server. Read the first error in logs/latest.log to see which one it is.
Not on plain Forge or Fabric. Plugins run on Bukkit-based servers like Paper, and mods run on loaders like Forge or Fabric. Some hybrid projects try to combine them, but they can be less stable. For a stable setup, choose one approach.
Often yes, if the mods are client-only and the server allows them, but anything that changes gameplay must match the server. Check the modpack's rules.
Modpacks are usually heavier on both memory and CPU than a plain server, so a bigger or Premium plan often makes sense for large packs. Start with what the pack recommends and adjust using real usage.
Back up the world, update on a test copy first, confirm it starts and loads, then update the live server. Tell players the new version so their clients match.
Choose a plan with enough memory and CPU for your pack, upload the server files, and follow the steps above. You can start small and move up as the world and player count grow. See the current Minecraft hosting plans, or read our best Minecraft hosting in India guide for a wider comparison.
Recommended for this article
Monday, July 13, 2026