Categories
Server Won't Start or Keeps Going Offline
Minecraft Server Management
·
17 views
·
Updated 1 hour ago
## Common Causes and Solutions
If your server shows "Starting" then immediately goes back to "Offline", work through these checks in order.
## 1. Check the Console Output
The most important step. Go to the **Console** tab and read the error message. The error tells you exactly what is wrong. Common errors and their meanings:
- **"Unable to access jarfile server.jar"** — The server file is missing. Go to Settings → Reinstall, or use the Version Changer to re-download it
- **"EULA not accepted"** — Open in the Files tab and change to
- **"OutOfMemoryError"** — Your server is running out of RAM. See Step 4 below
- **"Failed to bind to port"** — Another process is using the port, or the port is misconfigured. Try restarting the server. If it persists, contact support
- **"Mod/plugin error" or stack trace mentioning a specific mod** — A mod or plugin is crashing the server. See Step 3
## 2. Check Your Server Version and Type
- Make sure your server type and version are set correctly in the Version Changer
- If you recently changed versions, ensure your mods and plugins are compatible with the new version
- When in doubt, try setting the version to **latest** and reinstalling
## 3. Remove Recently Added Mods or Plugins
If the server was working before and stopped after adding something new:
- Remove the last mod or plugin you added
- Restart the server
- If it starts, the removed file was the problem. Check for a compatible version or alternative
- If it still doesn't start, continue removing recent additions one by one
## 4. Check Resource Usage
- If your server runs out of RAM, it will crash on startup — especially with many mods or plugins
- Remove mods and plugins you don't need to free up resources
- Review your configuration — large view distances, excessive entity spawning, and chunk loaders consume significant resources
- Only consider upgrading your plan if you've already cleaned up your configuration and the issue persists
## 5. Check Disk Space
Check your disk usage in the panel header. If you're at the limit:
- Delete old backups, unused worlds, or large log files
- Clear the folder of old log files
## 6. Restore from Backup
If you cannot identify the problem and the server was working before:
- Go to the **Backups** tab
- Restore the most recent working backup
- Start the server
## Still Not Working?
Copy the full error from your server console and open a support ticket. The error message helps us diagnose the issue much faster.
If your server shows "Starting" then immediately goes back to "Offline", work through these checks in order.
## 1. Check the Console Output
The most important step. Go to the **Console** tab and read the error message. The error tells you exactly what is wrong. Common errors and their meanings:
- **"Unable to access jarfile server.jar"** — The server file is missing. Go to Settings → Reinstall, or use the Version Changer to re-download it
- **"EULA not accepted"** — Open in the Files tab and change to
- **"OutOfMemoryError"** — Your server is running out of RAM. See Step 4 below
- **"Failed to bind to port"** — Another process is using the port, or the port is misconfigured. Try restarting the server. If it persists, contact support
- **"Mod/plugin error" or stack trace mentioning a specific mod** — A mod or plugin is crashing the server. See Step 3
## 2. Check Your Server Version and Type
- Make sure your server type and version are set correctly in the Version Changer
- If you recently changed versions, ensure your mods and plugins are compatible with the new version
- When in doubt, try setting the version to **latest** and reinstalling
## 3. Remove Recently Added Mods or Plugins
If the server was working before and stopped after adding something new:
- Remove the last mod or plugin you added
- Restart the server
- If it starts, the removed file was the problem. Check for a compatible version or alternative
- If it still doesn't start, continue removing recent additions one by one
## 4. Check Resource Usage
- If your server runs out of RAM, it will crash on startup — especially with many mods or plugins
- Remove mods and plugins you don't need to free up resources
- Review your configuration — large view distances, excessive entity spawning, and chunk loaders consume significant resources
- Only consider upgrading your plan if you've already cleaned up your configuration and the issue persists
## 5. Check Disk Space
Check your disk usage in the panel header. If you're at the limit:
- Delete old backups, unused worlds, or large log files
- Clear the folder of old log files
## 6. Restore from Backup
If you cannot identify the problem and the server was working before:
- Go to the **Backups** tab
- Restore the most recent working backup
- Start the server
## Still Not Working?
Copy the full error from your server console and open a support ticket. The error message helps us diagnose the issue much faster.
Still need help?
Create a Support Ticket