Use the same modpack release on the server and each player’s launcher. Matching only the Minecraft version is not enough.
Prepare the server
- Stop the server and make a full backup. Keep the current world, pack files and custom changes together.
- Check the new pack’s memory, Java and server setup requirements.
- Use a clean installation for a different pack rather than mixing it with old mods and configuration.
Install through Modpacks
- Open Modpacks and search for the exact pack.
- Choose Select version, select the release everyone will use and review the confirmation.
- Wait for installation to finish. Set the Java version the pack requires; ask support if that image is unavailable.
- Start the server and check Console. If an EULA prompt appears, read it and accept only if you agree.
- Install the same release in your launcher and test joining.
If the pack is not listed
If the pack is not listed in Modpacks, contact Konnect support with its name, release and a link to the author’s server pack. A client launcher manifest is not a ready server installation.
For NeoForge packs, see the NeoForge server setup guide.
If it does not start or allow joining
Check Console for an incorrect Java version, missing dependency or failed download. If startup succeeds, compare the installed client and server pack releases. Keep the error and release name when contacting support.
Troubleshooting checks
| What you see | What to check |
|---|---|
| Pack name matches but joining fails | Compare the pack release, loader and game versions. The same pack name can have incompatible releases. |
| The server crashes after changing packs | Check for files left from the old pack; keep its backup separate from the new installation. |
Related: Change Java · Install individual mods.
Was this article helpful?
Thanks for the feedback!Your feedback helps us improve our guides.
Written by Konnect HostingUpdated 2 min read
