A Forge or NeoForge server that stops straight after Start with this line in the Console cannot find its loader files:
Error: could not open `libraries/net/neoforged/neoforge/21.1.267/unix_args.txt'On Forge the path starts with libraries/net/minecraftforge/forge/, and the version number is the one your server was installed with. The console then reports a crash with exit code 1 and Out of memory: false. Your world, mods and configs are fine. Only the loader's own files are missing, and a reinstall puts them back.
Checked against our Minecraft installer on Forge and NeoForge, November 2026.
Why it happens
NeoForge, and Forge on newer Minecraft versions, start through a list of Java arguments kept in a file called unix_args.txt inside the libraries folder. When the loader is installed, the panel writes start.sh to read that file. If the file is gone, Java stops before Minecraft even loads.
The usual causes:
- The
librariesfolder was deleted in the File Manager. It is large and looks like clutter, but the server cannot start without it. - Files copied from a PC or another host replaced the server's own, bringing a
librariesfolder for a different version, or none. - A Forge or NeoForge installer
.jarwas uploaded instead of reinstalling. The panel does not run uploaded installers, so the files the installer would make never appear, andstart.shstill points at the old version.
Fix it on a server without a modpack
Use this when you picked Forge or NeoForge yourself, with or without mods you added.
- Open the Backups tab and press Create backup. A reinstall can overwrite files, so keep a copy first. How to create and restore backups has the steps.
- Open the Settings tab. Under Danger zone, press Reinstall, then hold Reinstall in the popup.
- Watch the Console. The install downloads the loader, writes
start.shagain and ends with "Minecraft is installed. Press Start whenever you are ready." - Press Start.
The reinstall keeps your world, the mods and config folders, server.properties and your player lists. It installs the newest Forge or NeoForge build for your Minecraft version, which may be newer than the build you had.
Fix it on a modpack server
If the server runs a pack you installed from the Modpacks tab, do not use Reinstall in Settings: on a pack server it removes the pack and asks what to install in its place. Install the pack again instead, and the pack brings back the exact loader build it needs.
- Open the Backups tab and press Create backup.
- Open the Modpacks tab and find the same pack and version. For a pack you uploaded yourself, use Install your own pack and pick the same
.mrpackor server-pack.zipfile. - Tick Keep my world, settings and player lists.
- Confirm the install and watch the Console until it says Minecraft is installed.
- Press Start.
The pack's own mods and configs come back as the pack ships them. Mods you added on top of the pack and changes to its config files are not kept, so download copies of them from the File Manager first. How to install a Minecraft modpack covers the install in more detail.
The libraries folder holds the loader and Minecraft's own code. When you tidy your files, leave libraries, start.sh and run.sh where they are.
If the server still crashes after the reinstall, the error is a different one. Find Minecraft server logs and crash reports shows where to read it.
Related guides

Fix ticking entity crashes on modded Minecraft servers
A Ticking entity crash report in Minecraft means one entity keeps failing. Read the report, then update the mod, let Forge drop it, or delete it from the world.
Updated 21 Nov 20265 min read
Overworld settings missing after leaving Paper
Switched from Paper to Fabric, Forge or a modpack and the world won't load? Paper saves world settings elsewhere. Switch back and again to move them.
Updated 8 Nov 20263 min read
Fix No key dimensions in MapLike (level.dat)
We broke level.dat on purpose to test this: rename level.dat_old to get the world back in under a minute, or restore a backup if both are bad.
Updated 21 Nov 20267 min read
