How to Set Up a Modpack Server for Minecraft Forge or Fabric (September 2026)

Running a modded Minecraft world alone is fun, but playing with friends takes it to another level. I built my first modpack server back in 2019, watched it crash twice, and learned that a clean setup saves hours of headache. In this guide, I will walk you through how to set up a modpack server for Minecraft Forge or Fabric, from choosing a loader to inviting your friends in.

You will learn what a modpack server actually is, how Forge and Fabric differ, which files to download, how to upload them to your host, and how to fix the errors that always seem to appear at launch.

What Is a Modpack Server and Why You Need One?

A modpack server is a Minecraft Java Edition server running a mod loader that lets multiple players join the same world with identical mods installed. The server holds the world data, the player list, and the game logic. Each player only needs the matching mods on their own client to connect.

You need a server because your friends cannot just join your singleplayer world. Multiplayer requires a central machine that everyone connects to. That machine can be your home PC, but most people rent a small VPS or use a Minecraft hosting provider because home connections have poor upload speeds and tend to go offline when you close your laptop.

A modpack, by the way, is a curated bundle of mods that work together. Sites like CurseForge and Modrinth host thousands of them, ranging from lightweight quality-of-life packs to 200+ mod kitchen-sink adventures.

Forge vs Fabric vs NeoForge: Which Loader Should You Pick

The mod loader is the software that hooks into Minecraft and lets mods talk to the game. Picking the wrong one is the most common mistake I see on Reddit. Here is the short version:

Forge has the largest mod library and has existed since 2011. If you want big tech mods like Create, Mekanism, or Applied Energistics, Forge is where they live. Most older modpacks still target Forge.

Fabric is newer, lightweight, and updates to new Minecraft versions within hours. It shines for performance mods (Sodium, Lithium, Iris) and smaller focused packs. The mod count is lower but the quality is consistently high.

NeoForge is a community fork of Forge that split off in 2023 after a disagreement between maintainers. Many newer Forge mods are actually NeoForge-only now. If a modpack tells you it needs NeoForge, do not try to use plain Forge; it will not work.

The rule of thumb is simple. Pick the loader that matches the modpack you want to play. Do not pick the loader first and hunt for mods after.

What You Need Before Setting Up a Modpack Server?

Before you touch any files, gather these items. Skipping this step is why most setups fail.

• A Minecraft Java Edition account. Bedrock accounts do not work with modded Java servers.

• A server host or self-host machine. For 2 to 5 players, 4 GB of RAM is enough for most modpacks. For larger groups or heavy modpacks, plan 6 to 10 GB.

• The matching modpack’s server pack. This is different from the regular modpack. Look for a button labeled “Server Pack” or “Download Server Files” on CurseForge or Modrinth.

• An FTP client. FileZilla is free and works on every operating system. Most hosting control panels also have a built-in file manager.

• Java 17 or newer. Minecraft 1.18 and above requires Java 17+. Minecraft 1.20.5 and above need Java 21. If you self-host, install the right version before anything else.

Pro tip: write down your Minecraft version, your loader version, and your modpack version on a sticky note. Mismatched versions are the number one cause of “failed to connect” errors.

How to Set Up a Modpack Server for Minecraft Forge or Fabric: The Quick Answer

To set up a modpack server, download the server pack from CurseForge or Modrinth, upload the contents to your host via FTP, set the server type to Forge or Fabric in your control panel, allocate at least 4 GB of RAM, then start the server and accept the EULA. Each player installs the same modpack on their client and connects using your server IP.

How to Set Up a Forge Modpack Server (Step-by-Step)

This method works for every major Forge modpack, including FTB packs, RLCraft, SkyFactory, and Create-based packs. I tested it with a popular 180-mod kitchen-sink pack on a shared host.

Step 1: Download the server pack. Open the CurseForge launcher, go to Minecraft, then Browse Modpacks. Find your modpack and click the three dots next to Install. Choose “Download Server Pack.” If the modpack is on Modrinth, go to the version page and look for the “Server” download link.

Step 2: Extract the archive. You will get a ZIP file. Extract it on your computer. Inside, you should see a mods folder, a libraries folder, a config folder, and either a forge.jar or a server.jar.

Step 3: Connect to your server via FTP. Open FileZilla and log in using the credentials your host gave you (usually hostname, username, password, port 21 or 22). Navigate to the root directory of your Minecraft server.

Step 4: Upload the server pack files. Drag the contents of your extracted folder (not the folder itself) into the server root. If your host asks whether to overwrite, choose “Overwrite if newer.” Uploading 200+ mods takes 5 to 15 minutes depending on your connection.

Step 5: Set the server type. In your control panel, find the server type or version selector. Pick “Forge” and choose the matching Forge version (for example, 1.20.1 – 47.2.0). If your modpack requires NeoForge, select NeoForge instead and pick the matching NeoForge build.

Step 6: Allocate RAM. Set minimum and maximum RAM to the same value to avoid garbage collection lag. For most modpacks, 4 GB works for a small group, 6 GB handles medium packs, and 8 GB covers heavy 200+ mod packs.

Step 7: Start the server and accept the EULA. Hit Start. The server will shut down and tell you to edit eula.txt. Change eula=false to eula=true, save, and start again.

Step 8: Verify it works. Open your Minecraft launcher, install the exact same modpack version on your client, click Multiplayer, add the server using the IP and port your host gave you, and join. If you see a custom main menu or modded blocks, the setup worked.

How to Set Up a Fabric Modpack Server (Step-by-Step)

Fabric modpacks are easier to set up because the loader is a single small file. I run a 70-mod Fabric pack with friends, and the whole process takes about 10 minutes.

Step 1: Download the Fabric server launcher. Go to fabricmc.net and download the universal server JAR. This is the small installer you run on your server to set up everything.

Step 2: Download your modpack’s server pack. Just like Forge, grab the server pack from CurseForge or Modrinth. Fabric server packs contain a mods folder with the loader jar plus all mods, plus a config folder.

Step 3: Upload to your host. FTP the contents into your server root. Make sure the fabric-server-launch.jar (or similarly named file) and the mods folder are at the same level as server.properties.

Step 4: Set the server type to Fabric. In your control panel, change the server type to Fabric. Some panels list it as “Paper-Fabric” hybrid, but for modpacks you want plain Fabric.

Step 5: Add Fabric API if needed. Many Fabric mods depend on Fabric API. If your modpack’s mods folder does not already include it, download Fabric API from Modrinth and drop it in.

Step 6: Allocate RAM and start. RAM allocation rules are the same as Forge: 4 GB minimum for small packs, 6 to 8 GB for larger ones. Start the server, accept the EULA, restart, and join from your client.

One warning: Fabric mods update fast. If your server mods are on version 0.15.2 but the client modpack is on 0.15.3, the connection will fail. Always match the exact version.

RAM Requirements for a Modpack Server

RAM is the single most common bottleneck. Too little and the server freezes; too much and the Java garbage collector slows everything down.

Here is the breakdown based on my testing and community reports:

• Vanilla server: 2 GB handles 5 to 10 players easily.

• Light modpack (under 50 mods): 3 to 4 GB.

• Medium modpack (50 to 150 mods): 4 to 6 GB.

• Heavy modpack (150 to 250 mods): 6 to 10 GB.

• Kitchen-sink or expert packs (250+ mods): 10 GB or more. Some packs like All The Mods 10 recommend 12 GB.

Always set the same value for -Xms and -Xmx. Splitting them forces the JVM to constantly resize memory, which causes lag spikes every few minutes.

Do not over-allocate. If your host gives you 16 GB but your pack needs 6 GB, capping at 6 GB leaves more CPU time for the garbage collector and improves performance.

Connecting Your Minecraft Client to the Modpack Server

Most guides stop once the server is running, but the client-side setup is where 30% of users get stuck. Here is how to make sure your friends can join.

Step 1: Install the exact same modpack version on your client. Use CurseForge, Modrinth, or the ATLauncher. The version number, loader version, and mod list must match the server exactly.

Step 2: Launch the modpack profile. Make sure you see the custom main menu or a modded item in your inventory. That confirms the mods loaded.

Step 3: Add the server. In Minecraft, click Multiplayer, then Add Server. Paste the IP and port your host gave you. The port is usually 25565 unless your host changed it.

Step 4: Share the connection info. Send your friends the IP, port, and a link to the same modpack version. I usually pin both in a Discord channel.

Step 5: Troubleshoot any version mismatches. If a friend gets “IncompatibleFmlToClientModList” or similar errors, their client mod versions do not match the server. Have them reinstall the same modpack version you are running.

Troubleshooting Common Modpack Server Issues

Even with a perfect setup, things go wrong. These are the six errors I see most often on r/admincraft and r/feedthebeast.

“Failed to bind to port”: Another process is using port 25565, or you have two servers running. Stop other instances or change the port in server.properties.

“Incompatible mod list”: Client and server mod versions do not match. Everyone needs the same modpack version installed, including the same version of Fabric API or Forge itself.

“Could not find or load main class”: The Java version is wrong. Minecraft 1.20.5+ requires Java 21. Install the correct JDK from Adoptium.

“World corruption” or region file damage: The server crashed mid-save. Stop the server, restore your most recent backup, and remove any mod that causes repeated crashes.

“Connection refused”: Your server is offline, the IP is wrong, or the port is blocked. Most hosts provide an external IP and internal IP; use the external one.

OutOfMemoryError: Allocate more RAM, but first check whether a single mod is leaking memory. Remove mods one at a time until the error stops.

If you hit something not on this list, the server log file (logs/latest.log) usually names the offending mod. Paste the error into Google with your modpack name; chances are someone has already solved it.

FAQs

Wrap-Up: Your Modpack Server Is Ready

You now have a complete roadmap for how to set up a modpack server for Minecraft Forge or Fabric. Pick your loader based on the modpack you actually want to play, download the server pack, upload it via FTP, allocate enough RAM, accept the EULA, and connect with your friends.

Start with a smaller modpack if this is your first time. Something like FTB Stoneblock or Better Minecraft has under 200 mods, runs smoothly on 4 GB, and has a friendly community if you get stuck. Once you are comfortable, branch out into heavier packs like All The Mods or RLCraft.

For 2026, the modding scene is bigger than ever, and a working modpack server is one of the best ways to enjoy Minecraft with friends. Take it one step at a time, keep your versions in sync, and you will be playing in under an hour.