Why Your Server Says "Starting" or Is Stuck Offline

When your server hangs on Starting or drops back to Offline, the reason is almost always written in plain text in the Console log, and reading it is the fastest way to fix things.

3 min read · Updated Sep 24, 2026 · By GuavaHost Team

When your server hangs on Starting or drops back to Offline, the reason is almost always written in plain text in the Console log, and reading it is the fastest way to fix things.

The coloured status at the top of your server page moves through a few states: Offline when nothing is running, Starting while the game boots, Online when it is up and joinable, and Stopping as it shuts down. A healthy start passes through Starting and settles on Online within a minute or so. When it gets stuck, the log tells you why. You may also see Installing (the game files are still being set up) or Setup failed (the install did not finish, so contact support).

How to read the console

Do not keep pressing Start. Instead, open the Console tab and scroll to the last several lines before it froze or crashed. Type a word such as ERROR into the search box above the log to show only the lines that contain it. Server logs are wordy, but the useful part is usually near the very bottom and often contains the word ERROR, FAILED, Exception or a message about what it could not do. That one line is your clue.

Common causes and fixes

• It is still installing. The first ever boot, or the first after a reinstall, downloads files and can sit on Starting longer than usual. Give it a few minutes and watch the log keep moving.
• A licence or agreement needs accepting. Some games refuse to start until you accept terms, the classic being Minecraft's eula.txt. Set the value to true (on the Files tab or in Startup settings on the Settings tab) and start again.
• Wrong or missing version. If the log complains about a version mismatch or a file it cannot find, check Startup settings on the Settings tab (or Version for Minecraft) and confirm the version and server type are set correctly.
• Out of memory. A log that mentions running out of memory, or one that crashes just as the world loads, often means the plan needs more RAM. You can add RAM any time with Manage plan in the server menu, and billing is prorated.
• A bad plugin, mod or config. If the crash started right after you added something, that something is the suspect. Remove or rename the offending file on the Files tab and try again. The log frequently names the exact file.
• A corrupted world or save. If the server crashes at the moment it loads the world, the save may be damaged. Restore a healthy backup from the Backups page, remembering that a restore overwrites current files.

A calm troubleshooting routine

1. Read the last 10 to 20 lines of the Console and look for the first error, not the last one.
2. Change one thing based on what it says, for example accept the licence, fix a version, or remove a plugin.
3. Press Start and watch the log again.
4. If it now gets further before failing, you are making progress; read the new error and repeat.

When to reinstall or restore

If the errors point to broken core files rather than your own content, Reinstall server on the Settings tab rebuilds the base install; take a backup first. If the errors point to your world or configs, a restore from the Backups page is the better tool.

If you have read the log and still cannot tell what it means, copy the error lines (the copy button above the log copies what is on screen) and bring them to us. Half the battle is having that text ready.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• troubleshooting
• console
• offline
• startup

Still need help? Our team is online 24/7 to answer questions.

Contact support