Troubleshooting and performance

Avancé tab (Advanced), Commande de démarrage card: pick one of the three presets. The Java setting is already sized to your plan's memory.

1. Avancé tab, Commande de démarrage card (startup command): Réglage actuel shows the current preset.

2. Pick Optimisé (optimized) for a vanilla or plugin server, Modpack for a heavy modded server.

3. Restart the server from the Console: the change applies at the next startup.

The command can't be edited by hand: no need to touch the memory, it follows your plan.

The console almost always shows the cause right before the server stops: read the last lines before looking any further.

1. Console tab (the panel is in French): restart the server and read the last lines before it stops.

   

2. An Exception or Error naming a mod or plugin: see the server crashes because of a mod.

3. A memory-related message (OutOfMemoryError, java.lang.OutOfMemoryError): see out of memory.

4. You need to agree to the EULA: in the Fichiers (Files) tab, open eula.txt, replace false with true, save and restart.

5. The server stops right after a version change: make a backup, then run the install again from the Version tab with Formater le serveur (format the server) checked. Careful: this box deletes all the server's files.

6. If nothing is clear, back up (see backups) then contact support with the last lines of the console attached.

The console names the mod or plugin responsible right before the server stops: remove it and restart to confirm.

1. Console tab: find the name of the mod or plugin mentioned in the error (right before the server stops).

2. Fichiers (Files) tab: rename its .jar file in mods or plugins (for example, add .disabled at the end) to exclude it without losing it.

3. Restart. If the server starts, the mod or plugin you removed was indeed the cause.

4. Check its version: it must exactly match your server version and the loader you have installed (Fabric, Forge, NeoForge).

An OutOfMemoryError message, or a server that becomes unplayable for no clear reason, points to memory that's too tight for what you've installed.

1. Cut down whatever uses the most: number of mods or plugins installed, render distance, number of players online at once.

2. On a modded server, pick the Modpack preset in the startup command: the Java setting is already sized to your plan's memory.

3. If the server is still at its limit once everything is well tuned (a big modpack, lots of players), move up to the next plan: more RAM fixes this directly.

4. If the problem persists after these checks, contact support.

Lower the render distance and simulation distance in the Paramètres tab, then find what's using resources with a profiler if the lag continues.

1. Paramètres tab (Settings): reduce Distance de rendu (render distance, view-distance) and Distance de simulation (simulation-distance), for example to 8 and 6, then Enregistrer (save).

2. On Paper, Spigot, or Purpur: install the Spark plugin, run /spark profiler start, let it run for a few minutes while playing, then /spark profiler stop to see what's using the most resources (a plugin, an entity, a structure).

3. Remove or reconfigure whatever the profile flags as expensive.

4. If the world is heavily explored and keeps generating new chunks, see the server maxes out the CPU.

Lower the render and simulation distance, pre-generate the world with Chunky to avoid on-the-fly generation, and remove client-only mods from the mods folder.

1. Paramètres tab (Settings): set Distance de rendu to 10 and Distance de simulation to 8, a good compromise on a modded server, then Enregistrer.

2. Install the Chunky mod (compatible with your loader), then in console or in game:

   consoleCopier

   > chunky radius 3000> chunky start

3. Let pre-generation finish outside of play hours: it stops the CPU from generating new chunks in the middle of a session.

4. Fichiers tab, mods folder: remove client-only mods (Sodium, Iris, entityculling, and other visual optimization mods) if a modpack included them on the server by mistake. See add mods manually.

Mode Expert (Expert Mode) and SFTP have their own password, different from your account password. A refused login almost always comes from that.

1. The password is set on your account's Paramètres page (not the server's), Mode Expert card.

2. Forgot it? Click Changer ce mot de passe (change this password) and pick a new one: see forgot your Expert Mode password.

3. For SFTP, copy the host, port and username again from the Avancé tab, Accès SFTP card > Voir les identifiants (view credentials): they may differ from an old note.

4. Still stuck: contact support and say which tool you use (Mode Expert, FileZilla, WinSCP).

The status shows "Installation..." then, if it fails, "Installation échouée" (installation failed). A big modpack can stay on "Installation..." for several minutes, that's normal.

1. A lingering Installation... status is normal for a big modpack (several hundred mods): give it a few minutes before worrying.

2. If the status changes to Installation échouée: go back to the Modpacks tab, pick the pack and its version again, then click Installer le modpack (install the modpack).

3. Still failing: check that the modpack version you picked actually exists for that loader, some packs don't publish a server version for every client version.

4. Still stuck, contact support with the exact name and version of the modpack.