Your modpack server is running but your friends can't get on? It is almost always one of these causes.
"Timed out" or "Read timed out" while joining
Big modpacks load a lot of data when joining (blocks, recipes, textures). If the player's PC needs longer than about 30 seconds for that, the connection drops – even though the server is fine.
- Simply connect again. On the second try a lot is already cached and it usually works.
- Give Minecraft more memory in the launcher. For big packs, 6–8 GB in the launcher (CurseForge app, Modrinth app or Prism) makes sense – that is memory on the player's PC, not on the server.
- Close other programs that use a lot of memory.
"Mod mismatch", "Mismatched mod list" or missing mods
The player doesn't have exactly the same mods as the server.
- Everyone needs the same version of the pack as the server. You can see which one on your invite page.
- Easiest: send your friends your invite page – it shows the address and the matching modpack download.
- If you added mods to the server yourself, your friends need them too.
"Incompatible client" or wrong Minecraft version
The player starts plain Minecraft instead of the modpack. They have to launch Minecraft through the modpack profile (CurseForge app, Modrinth app or Prism), not through the normal Minecraft launcher.
Server unreachable or "Connection refused"
- Check on the server page that the server is running – big packs need a few minutes after starting before they are ready. You can follow it in the Console (ready at "Done").
- Check the address including the port (e.g.
1.2.3.4:25565). The correct value is shown at the top of the server page.
"You are not white-listed on this server"
The whitelist is switched on. Add your friends in the Players tab or switch the whitelist off there.
Still stuck?
If the console shows errors or the server keeps restarting, open a ticket – we'll look at the log together with you.