A server that refuses to start can be frustrating, but the cause is usually identifiable through the console output or logs. Here are the most common reasons and how to resolve them.
Game Servers (Pterodactyl)
Insufficient Resources
If your server runs out of its allocated RAM or disk space, Pterodactyl will prevent it from starting or kill the process immediately. Check your resource usage on the server’s main page in the panel. If you are at or near your limits, consider removing unnecessary files, reducing your configuration’s memory allocation, or upgrading your plan.
Corrupted Configuration Files
A syntax error in a configuration file (such as server.properties for Minecraft or server.cfg for FiveM) can prevent the server from booting. Review recent changes to your config files. Look for missing quotes, brackets, or invalid values. If you are unsure what went wrong, restore the config from a backup or regenerate a default one.
Port Conflicts
If another process is using the port assigned to your server, it will fail to bind and cannot start. This is rare on Pterodactyl-managed servers, but can happen if you have manually configured additional services. Check the console for "address already in use" errors.
Missing or Corrupt Files
If critical server files have been deleted or corrupted (for example, the server JAR for Minecraft or core resources for FiveM), the server will fail to start. Check the console output for "file not found" errors and re-upload or reinstall the missing files.
VPS / Dedicated Servers
If your VPS or Dedicated Server does not respond after a reboot, use the console access in your Client Dashboard to check for boot errors. Common causes include a full disk (the system cannot write temporary files needed to boot), a misconfigured firewall that is blocking all traffic (the server is running but unreachable), and a broken package update that has corrupted a critical service. If you cannot resolve the issue, our support team can help.