We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Minecraft server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!
Minecraft guide

How to Set Up a Modded Minecraft Server: Forge, NeoForge, Fabric

By the ChicagoServers team · Updated · 6 min read

To run mods on a Minecraft Java server, install a mod loader (NeoForge, Forge or Fabric) that matches your Minecraft version, then put the mod .jar files in the server's mods folder. Every mod has to be built for that same loader and that same Minecraft version, and players need the same loader, version and, for content mods, the same mods on their side. On ChicagoServers, the Mods tab changes the server software and Java and installs mods and modpacks, so you do not run an installer yourself.

This guide covers choosing a loader, setting it up from the panel, which mods belong on the server, running modpacks and reading a crash. It was checked against the loaders' own documentation in November 2026.

Quick answer
  • One loader per server. Mods built for Fabric will not run on NeoForge or Forge, and the reverse.
  • Match the mod's Minecraft version exactly. A mod for 1.21.8 may not work on 1.21.11.
  • Most Fabric mods also need Fabric API in the mods folder.
  • Remove client-only mods (shaders, minimaps and other visual mods) from the server.
  • For a modpack, use the Mods tab's modpack install, or the pack's server pack file if it has one. Crashes are explained in crash-reports/ and logs/latest.log (both on the Files tab), and the Troubleshoot tab lists likely causes.
On this page
  1. Pick the loader your mods need
  2. Install a NeoForge, Forge or Fabric server on ChicagoServers
  3. Loader notes: NeoForge, Forge and Fabric
  4. Which mods go on the server
  5. Running a modpack
  6. Troubleshooting a crash
  7. Frequently asked questions

Pick the loader your mods need

You do not choose a loader in the abstract; you choose it because the mods or modpack you want are built for it. Check the mod pages first.

  • NeoForge is the loader used by current large packs. For example, All the Mods 10 is a NeoForge pack for Minecraft 1.21.1 on CurseForge. NeoForge publishes builds for 1.21.1 and for the 26.x releases.
  • Forge still publishes builds for current versions; its download page lists builds up to 26.3.
  • Fabric describes itself as a modular, lightweight mod loader, and its project says it officially supports Minecraft from 1.14 onward. Most Fabric mods depend on Fabric API.

Check the Java requirement too. Minecraft 26.1 and later needs Java 25 (NeoForge's docs say JDK 25), while Minecraft 1.20.5 through 1.21.11 uses Java 21. Java is chosen on the Mods tab.

Install a NeoForge, Forge or Fabric server on ChicagoServers

The loader, the Minecraft version and Java are all set from the panel. Replace the example choices with whatever your mods require.

  1. Back up first

    Open your server in the panel, then the Backups tab. Under Back up now, choose World and settings and click Back up now. Changing server software on an existing world is easier to undo with a restore point.

  2. Choose the server software and version

    Open the Mods tab and choose the server software your mods need (Forge, Fabric and the other options listed there) and the Minecraft version your mods are built for. If the loader you need is not listed, contact support.

  3. Choose the Java version

    On the same tab, choose the Java version your Minecraft version needs (see above). The wrong Java is one of the most common startup failures.

  4. Add mods

    Install mods from the Mods tab, or upload the .jar files into the mods folder on the Files tab (or over SFTP for many files). Most Fabric mods also need Fabric API in the same folder.

  5. Start and check the console

    Click Restart at the top of the page and watch the Console tab. The first start of a new loader generates files and can take longer than usual.

Loader notes: NeoForge, Forge and Fabric

  • NeoForge and Forge: both create a mods folder and write their config and logs in the server folder. Forge's installer follows the same general pattern as NeoForge's for modern versions; confirm details on the loader's own download page for your version.
  • Fabric: Fabric's wiki describes a server launcher jar that downloads any missing Fabric Loader and Minecraft files before it starts. Place mods in the mods folder along with Fabric API, which most mods require.
  • If you change the Minecraft version of an existing Fabric server and see class-loading errors, Fabric's wiki says to delete the old .fabric folder. Stop the server first, then delete it on the Files tab.
  • You do not edit JVM argument files or start scripts on ChicagoServers. Memory is part of your plan, and extra launch options are staff-only, so contact support if you need a flag changed.

Which mods go on the server

A dedicated server does not render anything, so mods that only change the client can crash it or do nothing. NeoForge's documentation says client-side mods should be removed from the server, notes that shader and visual-only mods are typical examples, and admits that identifying them often takes trial and error.

  • Needed on both sides: mods that add blocks, items, mobs or dimensions. Players must have them too.
  • Server-only: some utility or optimization mods, which players do not need to install. The mod page normally says so.
  • Client-only: shaders, minimaps, UI tweaks and similar. Leave them off the server.

Download from sources you trust. NeoForge's docs recommend CurseForge or Modrinth. Always match the loader and Minecraft version shown on the download page, and read the dependencies list. To remove a client-only mod, delete it from the mods folder on the Files tab (or remove it from the Mods tab), then Restart.

Running a modpack

The Mods tab installs modpacks, so start there. If you use a pack's own files instead, use its server pack whenever it exists. The All the Mods 10 page on CurseForge, for instance, ships a separate server pack file. If a pack has none, NeoForge's docs describe installing the normal pack in a launcher, copying its contents into the server folder, and then removing client-side mods. Upload large packs over SFTP: copy Host, Port and Username from the blue SFTP bar, and use your panel password.

  • Set the server software and version the pack uses first, then add the pack's files.
  • Don't interrupt the first start; ATM's guide warns it generates files and that canceling can force you to start over. Let it finish before you use Stop or Restart.
  • Check the Java version the pack requires and choose it on the Mods tab. The wrong Java is one of the most common startup failures.
  • Leave server-ip and server-port alone, as ATM's guide advises. On ChicagoServers the port is assigned by the panel.

Hosting with ChicagoServers? The Minecraft server hosting page lists what is included, such as one-click mod and modpack installs, free server backups and SFTP file access.

Troubleshooting a crash

When a modded server fails to start or crashes, open the Troubleshoot tab first: it lists what the checks found, plus crashes and failed starts from the last 14 days with the likely cause. Then read these in order on the Files tab and Console tab:

  1. crash-reports/ in the server folder (Files tab). Fabric's documentation says to start with the summary section and the first mod named in the stack trace, though if several mods appear, the first may not be the real cause.
  2. logs/latest.log (or the last lines on the Console tab) for the lines just before the failure, such as a missing dependency or a mod that requires a different loader version.
  3. The mod list in the crash report, to spot duplicates or mods that don't belong.
SymptomLikely cause
Crash on startup naming a modWrong Minecraft version or loader for that mod, or a missing dependency (often Fabric API)
Server won't start at allWrong Java version, a mismatched loader or Minecraft version, or too little memory
Works until a player joinsMissing mod on the client, or a client-only mod on the server
Duplicate or version conflict messagesTwo copies of the same mod, or mods that require different versions of a library

If you can't find it, undo the last mod you added, or remove half the mods and test, then narrow down. A backup from before the problem can be put back on the Backups tab with Restore. Share a crash report through a paste site when asking an author for help rather than posting it as raw text.

Frequently asked questions

Can I mix Forge, NeoForge and Fabric mods on one server?

No. Each loader needs mods built for it, so a server runs one loader. Use the loader your mods or modpack are built for.

Do players need to install the same mods as the server?

For mods that add content such as blocks, items and dimensions, yes. Some server-only mods don't need installing on the client, and the mod page usually says which.

Why does my modded server crash on startup?

The usual causes are a mod built for a different Minecraft version or loader, a missing dependency such as Fabric API, a client-only mod, the wrong Java version, or too little memory. The Troubleshoot tab lists likely causes.

Where do I put mods on a Minecraft server?

In the mods folder in the server's main directory. On ChicagoServers, install them from the Mods tab or upload them to that folder on the Files tab. Fabric, Forge and NeoForge all use the same folder name.

We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Minecraft server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

We offer quality support, a detailed knowledgebase, video tutorials on most topics, and even live support in case you prefer a live human.

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!