Your modded Minecraft server will not start or let you join

Start with the failure, not the final message

• The server stops before it is ready: read its startup log and crash report. Check loader, Java and dependencies.
• The world starts but your client crashes: inspect the client log and the instance you launched.
• You get a mod mismatch when joining: compare the required client/server releases.
• You get a timeout: first confirm the server is actually ready, then check address and connection. A timeout alone does not prove a broken mod.

Record the last change and its time. Preserve a backup before changing server files. If you need to test by removing a mod that adds blocks, entities or dimensions, use a disposable copy of the world. Loading and saving the original without that mod can damage its content.

A client pack is not always a server pack

A launcher instance can include graphics, interface and other client-only mods. Copying its entire folder into a dedicated server can cause startup errors. Prefer the pack author's server pack and setup instructions when available. If no server instructions exist, check every project's supported environment before building your own installation.

A .mrpack is a pack format containing a manifest and potentially overrides. It is not a plugin JAR to drop into a plugins folder. The Modrinth format documentation describes client/server environment flags. An import feature in a launcher does not establish an import feature in your hosting panel.

ChunkArc's Fabric catalogue guide covers compatible individual server mods. It does not guarantee automatic full-pack installation, arbitrary uploads or support for every Forge/NeoForge pack.

Compare a small version checklist

1. Confirm the same Minecraft release on the server and the player's instance.
2. Confirm the required loader family: Fabric, Forge and NeoForge are distinct choices. Use versions the pack author supports.
3. Compare releases of mods required on both sides. Similar names are not enough.
4. Check required libraries on each side, including Fabric API when the project requires it.
5. Keep client-only files off the dedicated server, and follow the instructions for server-only utilities.

Do not assume every file must exist on both sides. A rendering mod and a content mod can have different requirements. The Fabric installation guide explains compatibility checks. For missing Fabric dependencies, read Fabric Loader vs Fabric API.

Find the first useful error

Keep the complete startup log, then find the first relevant dependency error or exception. A final exit code or “server offline” line describes the result, not necessarily its cause. A crash report is usually in crash-reports under the affected game or server directory when one was generated. Not every failure creates one.

Look for the named project, required version and the first meaningful “Caused by” section. A client class mentioned on the dedicated server suggests an environment problem; an unsupported Java class version suggests a runtime mismatch. Verify those clues against the project's documentation before changing anything.

Use Fabric's crash report guide and log sharing instructions. Remove credentials, tokens and personal details before sharing logs. Do not post private server configuration publicly.

Check memory without guessing a mod limit

If the log reports an out-of-memory error or the process is killed, inspect the available host/panel evidence. A stopped process alone is not proof of a memory problem. World generation, entities, view distance and the particular mods affect demand; mod count alone cannot tell you the RAM required.

ChunkArc Free Beta provides 2 GB RAM and 5 GB storage. Treat it as a starting point for a modest setup, not a guarantee for a full pack. Do not choose a pack because a forum user ran a different one on 2 GB. See the RAM planning guide before committing a world to a pack.

Recover with one controlled change

In Manage, stop the world before changing server mods. Keep the previous compatible release and backup available, change one suspected dependency or release, then review the next startup log. Avoid removing several unrelated files at once: you lose the comparison that helps identify the cause.

Send support the server software, Minecraft and loader versions, exact pack/mod releases, first error, and whether the same setup worked before. Say whether the failure is startup, client crash or join rejection. Do not share passwords. For a ready server with a connection problem rather than a mod error, use the connection checklist.