Installing modpacks

Check the pack’s recommended server RAM and round up — modded servers crash on out-of-memory long before they run slowly. Sizing guidance lives on the modded hosting page. Take a backup if the server already has a world you care about.

Stop the server, open Startup in the panel, and set the pack variables: the CurseForge or Modrinth project ID (or slug) and the version. Start the server — the egg downloads the server pack, installs the mod loader, and generates configs on first boot. First start on a large pack can take several minutes; watch the console rather than restarting.

Download the server pack from the pack page (not the client zip). Connect over SFTP with the credentials shown in your panel, upload the zip to the server root, then unarchive it from the file manager. Set the startup jar to the loader jar the pack ships (for example run.sh, forge-*-server.jar, or fabric-server-launch.jar) and start.

Leave roughly 1 GB of your allocation outside the heap for the JVM itself. Aikar’s flags are a sensible default for Forge and Fabric packs; avoid setting a heap larger than your plan’s RAM, which triggers an immediate kill by the container.

Back up first. Bump the pack version in Startup and restart for published packs, or upload the new server pack over the old files while keeping world and any configs you customised. Expect to re-apply config edits after major pack updates.

Exit code 1 on boot usually means a missing or mismatched mod — read the last 40 console lines for the mod name. Out of memory / exit code 137 means the pack needs more RAM; upgrade the plan. Client cannot connect after a pack update almost always means the client and server pack versions differ. Mixin apply failed points at two incompatible performance mods — remove one.

Managed technician help ($2.00/GB tier) includes pack installation, conflict resolution, and tuning. Open a ticket with the pack name and version and we will handle it.