Server Offline
Troubleshoot when your Cafora Minecraft server is offline or not starting.
Illustrated procedure
Screenshots show the current application with demonstration data. Use your own service details; click an image to inspect it at full size.
Check the console
Open Essentials → Console. Check the current state, startup output and errors before making changes. Wait for Done or your software’s ready message before joining.

Locate the file log
Under Files, double-click logs and locate latest.log. Check modification times. Preserve the relevant file before a restart replaces or rotates it.

Read the complete error context
Open the log in the editor and inspect the earliest relevant error and surrounding lines. Remove tokens, passwords and private player details before sharing. Do not diagnose from the last line alone.

Describe the request to support
Open a support ticket with the service or invoice ID and the requested action. For connection issues include time, error and MTR evidence. Never include passwords, tokens or card details.

Quick Checks
- Check the Pterodactyl Panel for server status
- Look for any error messages in the dashboard
- Check if your billing is current (see Renewals)
- Verify your internet connection
Common Causes
Server Crashed
Check the console log for crash reports. Common causes:
- Out of memory (OOM) error
- Incompatible or broken plugin/mod
- Corrupted world data
- Invalid configuration
Insufficient Resources
If your server exceeds its RAM allocation, it may fail to start. Check resource usage.
JVM Configuration
Invalid JVM flags can prevent startup. Verify startup parameters.
Port Conflict
Another process using the same port can prevent binding. Check ports.
Steps to Resolve
View the server console for error messages.
Check the latest log file in the File Manager.
If a plugin is causing issues, temporarily disable it via the File Manager.
Try starting the server with a default configuration to isolate the problem.
If the issue persists, contact Cafora Support.
Activated, but offline after the first start
Confirm that the Store service matches the server in Panel, then read the output immediately before it exited. If it asks for EULA acceptance, follow the first-start guide, read the terms and decide whether to accept before starting again. Wait for an in-progress installation to finish. If the service is Suspended, ask support to check billing or the suspension reason.
An ordinary Offline status does not mean the server will wake when a player joins. Unless an automatic start mechanism has explicitly been configured, start it manually in Panel. Do not place duplicate orders, reinstall or delete worlds to resolve an unexplained offline state.