If your server stops while starting, check Console before changing anything. The useful error is often a few lines above the final message saying the server is offline.
Find the error
- Open the server’s Console page. If it is stopped, press Start once and watch the output.
- Copy the first relevant error and the lines around it. A final exit code alone usually does not explain the cause.
- Think about what changed before the problem began, such as a mod, plugin, world upload, or Startup value.
- Check the server’s memory and disk usage. Record the values if the server stops while starting.
Check the most common causes
Missing file: check the path and filename in Files. Look for an extra folder created during extraction or an upload that did not finish.
Invalid settings: undo your last edit and keep the file’s original quotes, commas, and section headings. Check Startup too if it controls that setting.
Mod or plugin error: check that it supports your game version and server software. Temporarily undo the last installation, then start again. Keep the original files so you can put them back.
Memory or storage error: look for a message saying memory was exhausted or there is no space left. Check the panel’s usage before removing files or changing the plan. An exit code by itself is not proof that you need more RAM.
If you still need help
Send support the server name, error text, time of the failed start, and what you changed. Remove passwords, tokens, and private addresses from screenshots. If Console cannot connect at all, check service status and tell support.
Related guides: editing files, freeing disk space, and restoring a backup.
References: Pterodactyl console output and resource usage display.
Your feedback helps us improve our guides.
