Installing Forge on a server is a one-time setup that takes a few minutes, and it is the same basic process whether you are installing it for the first time or setting up a fresh modpack.
What you need first
- A confirmed Minecraft version, since the Forge installer is version-specific and you need the matching build for the modpack or mods you plan to run.
- A recent Java runtime installed, matching what that Minecraft version requires (Java 17 for 1.18–1.20.4, Java 21 for 1.20.5 and later).
- An empty folder dedicated to the server, separate from any existing world you want to keep safe.
Step 1: Download the installer
Go to the official Forge downloads page and pick the version matching your target Minecraft release. Download the installer jar (not the "installer-win" launcher variant, which is for the client) into your empty server folder.
Step 2: Run the installer in server mode
Open a terminal in that folder and run:
java -jar forge-<version>-installer.jar --installServer
This downloads the required libraries and generates a run.sh (Linux/macOS) or run.bat (Windows) startup script, along with a libraries folder. The first run can take a couple of minutes since it is downloading and verifying files, this is normal.
Step 3: Accept the EULA
Launch the server once using the generated run script. It will fail immediately and create an eula.txt file. Open it and change:
eula=false
to:
eula=true
Step 4: Start the server
Run the startup script again. Forge will finish initializing (this first real launch is also slower than normal) and generate your world along with a server.properties file. A server.properties generator is a faster way to configure it than editing every line by hand.
Step 5: Add mods
Once the server is running, drop compatible mod .jar files into the mods folder it created, then restart. Every mod needs to match both the Minecraft version and Forge (not NeoForge or Fabric) specifically, mismatches are the most common cause of a server that won't start after adding mods.
If the server won't start
Check the console output and the logs/latest.log file first, Forge is generally clear about which mod or library caused a crash. Missing dependency errors and version mismatches account for the large majority of first-time Forge server failures.
Skipping the manual steps
A hosting panel with a Forge installer built in handles the installer command, the EULA file, and the startup script automatically, so the whole process above becomes a version dropdown instead of a terminal session. Tick Hosting's panel installs Forge with one click on every plan, including the free tier. Get started on Tick Hosting's plans page.