From an error report to a useful next test
Your world stops loading, a plugin stays disabled or the console reports an unfamiliar error. Copy the related log section into the analyser. It searches for known signatures and displays relevant guidance. That interpretation still needs the context of the complete sequence of events.
Copie l’extrait pertinent depuis ton latest.log ou le dossier crash-reports de ton serveur — plus il y a de contexte, plus l’analyse sera précise.
Le texte que tu colles n’est pas enregistré — nous comptons seulement de façon anonyme quel modèle d’erreur a été détecté.
Ton texte est trop long pour l'analyse — réduis-le aux lignes pertinentes (maximum 100 000 caractères).
Résultat de l’analyse
Diagnostic des mods dans ton log
- Mod concerné
- Manquant
- Requiert
Mods suspectés par Forge
- Version
Aucun modèle d’erreur connu trouvé
Nous n’avons reconnu aucun modèle de crash connu dans le texte que tu as collé. Si ton serveur s’est arrêté brusquement sans message d’erreur, la cause est souvent une pression mémoire — un crash dû à un manque de mémoire ne laisse parfois aucune ligne d’erreur. Un coup d’œil au calculateur de RAM peut donc quand même valoir le coup.
Ça ressemble à des problèmes de mémoire
L'analyse indique un manque de mémoire vive. Avec notre calculateur de RAM, tu découvres en quelques secondes de combien de RAM ton serveur a vraiment besoin.
Aller au calculateur de RAMPrêt pour un serveur plus stable ?
Choisis le serveur de jeu adapté et vérifie les ressources, les paramètres ainsi que le prix mensuel final avant de commander.
Voir les serveurs de jeuChoose the relevant excerpt
Begin with the error block around the failure. In latest.log or a crash report, more specific causes often follow the first message. Include related subsequent lines, especially entries with Caused by. Remove names and private addresses before pasting. Passwords and access keys should never go into the input field.
A match describes a pattern
The analyser compares text with a catalogue. It does not inspect your running server. A detected memory error, for example, does not yet explain whether your chosen resources are insufficient or an extension uses an unexpected amount. Consider the latest change and the time of the problem when choosing your next test.
Turn an assumption into a comparison
Keep the original report and back up your game state before changing anything. Then test one understandable relationship, such as the latest extension or unusual world activity. Reproduce the trigger and check whether that exact message and the observed problem disappear. Conversely, an empty results area does not establish an error-free server.
What happens to the pasted text
Your excerpt is transmitted to the analysis endpoint and processed there. The pasted report is not stored as complete raw text. The service records limited counters for recognised patterns; these do not form a personal error archive. Keep a cleaned excerpt yourself if you may need it for support later.
Look up the reported line directly
Choose the signature from your log. Each detail page leads from that specific clue to a relevant check.
- Minecraft Java heap full: reduce the right load Critique
- Minecraft spends its time collecting memory Critique
- Watchdog shutdown: find the blocked Minecraft tick Critique
- Minecraft falls behind its tick schedule Avertissement
- Tick loop exception: read through to the cause Critique
- Full disk: protect Minecraft data before clearing files Critique
- Minecraft waits for your EULA agreement Critique
- A datapack blocks world loading: isolate the package Critique
- Mixin failure: check the mod and its target version Avertissement
- Minecraft cannot save world data Critique
- Occupied port: check Minecraft's network binding Critique
- Java does not match the loaded server file Critique
- Missing Java class: resolve the dependency Avertissement
- Plugin JAR rejected: inspect the file Critique
- Plugin loaded but failed to enable Critique
- Satisfactory reports its own certificate Inoffensif
- Satisfactory: assess a TLS handshake warning Inoffensif
- Satisfactory discards an HTTP connection Inoffensif
- Segmentation fault: isolate a native server failure Critique
- Login plugin conflicts with online mode Critique
- SteamCMD ends an update with an App state error Critique
- CS2 bots stand still: check map navigation Information
- Invalid Minecraft session when joining Avertissement
- World no longer knows a block: preserve content first Avertissement
- Paper cannot remap a plugin Avertissement
- A plugin cannot connect to its dependency Avertissement
- Minecraft cannot reach account verification Avertissement
- Minecraft skips an unknown recipe entry Information
- World generation places a block too far away Information
- Async TPS warning: identify the query source Inoffensif
Questions fréquentes sur l’analyseur de Crash Report
Continue on your server
Open your server dashboard if needed. Confirm changes to settings and worlds there yourself.