"My AndroHost server is offline, what now?"

You opened the panel. Your server says Offline. Or worse, the panel itself won't load. This article walks through the order of things to check, fastest to slowest.

In probably 9 out of 10 cases, you can self-resolve in under two minutes. The other 1 in 10 needs us, and you'll know it's us in about 30 seconds of looking at the right page.

First check (10 seconds): is it just our infrastructure?

Visit our status page: status.androhost.com.

• All green → it's something specific to your server.
• One or more red → it's us. We're already working on it. Refresh in a few minutes; if it stays red beyond what's posted, drop a note in our Discord.

The status page is honest. If something's broken on our end, you'll see it.

Second check (30 seconds): is your server "offline" or "crashed"?

Open the panel. Look at the status badge next to your server name.

• Offline (grey/idle): the server is stopped, but the host is fine. Just click Start. If a couple of seconds later it's running, you're done.
• Stopping (orange): mid-shutdown. Wait 30 seconds, then start. Force-stop if it's stuck.
• Starting (blue): mid-startup. Wait. Most servers boot in 10-60 seconds; modded servers can take 2-5 minutes.
• Crashed (red): the server failed during startup or while running. See the next section.
• Offline but Start does nothing: the host node is having trouble. Check the status page; if green, open a ticket.

If "crashed": read the console (1 minute)

Console tab → scroll to the bottom. The error is usually in the last 20 lines above the "process exited" message.

Common patterns and fixes:

java.lang.OutOfMemoryError: Java heap space

You've run out of RAM. Solutions:

• Reduce world load: lower view-distance in server.properties (8 → 6), reduce simulation distance, prune giant chunk areas.
• Remove a memory-hungry mod or plugin: check logs/latest.log for which mod triggered the OOM.
• Upgrade your plan: if your server has grown past 4 GB of comfortable use, you need more RAM. See when to upgrade.

Address already in use / port already bound

Something else is on the port. Usually because a previous instance didn't fully shut down:

• Panel → Power → Kill (force-stop, not the normal Stop).
• Wait 10 seconds.
• Start.

java.lang.UnsupportedClassVersionError / wrong Java version

The mod or plugin requires a newer Java than the server's running. Solutions:

• Check the egg in the panel sidebar (the Startup tab might show Java version).
• If a recent mod update requires Java 21 but your egg is on 17, contact us to switch eggs.

mods/ is empty but server expects mods

Something deleted your mod files. Check Files tab → mods/. If empty, restore the latest backup.

Forge/Fabric: "Mod X requires Mod Y version Z but found A"

Version mismatch. See Mod version mismatches. The fix is usually updating the offending mod or the modpack version.

Terraria-specific: world corruption errors

Worlds occasionally get corrupted. Try restoring from a recent backup. If your backups also fail, see Save-game corruption.

No error visible, server just exits

Some games (Valheim, occasionally Vintage Story) print very little on a clean shutdown. If the server cleanly exited with no error, it might have been scheduled to stop (Schedules tab) or you may have shut it down without realizing.

If the panel itself won't load

You can't even see the status badge because panel.androhost.com isn't loading at all.

• Check the status page from a different network if possible (mobile data instead of home WiFi). Some ISP outages or DNS issues are local to you.
• Try in an incognito tab — a broken browser session can make the panel seem dead.
• Check downdetector for "androhost" or our parent infrastructure to see if other people report the same.
• If none of the above show issues but you still can't reach the panel, post in our Discord. We can confirm whether it's us or your network.

If players are saying they can't join but the panel shows "Running"

The server is up but something between the player and the server is broken. Order of things to try:

• Have one player run a connection test like mcsrvstat.us for Minecraft Java. Plug in your server address and see what the third party reports. If they see the server: it's the specific player's network. If they don't see the server: there's a routing or firewall issue.
• Check the SRV record if you set up a custom domain. SRV records that misresolve are a top-3 cause. See Custom domains for game servers.
• Check player versions match your server. Mod versions, snapshot vs release, etc. Players on Minecraft 1.21.1 can't join a 1.21.4 server.

Player can't join but everyone else can goes deeper.

When to open a ticket (vs keep self-diagnosing)

Open a ticket if:

• You've tried the above and the server still won't start.
• The status page shows green but multiple of your servers are all offline.
• You see your data disappearing or being modified you didn't do.
• A console error mentions our hostname or internal paths in a confusing way.

When you open the ticket, include:

1. Server name (helps us look it up fast).
2. Last few lines of the console (paste, not screenshot, ideally).
3. What you'd already tried.

A good ticket gets a real answer in 5-15 minutes. A vague "my server is broken" with no details adds 30 minutes while we ask follow-up questions.

Things you should never do

• Hard-reset the server repeatedly. If a server is crashing during startup, restarting it 20 times in a row won't fix it. Read the console.
• Reinstall the server. "Reinstall" wipes your world. Almost no problem is solved by reinstall, and it definitely loses data.
• Edit the wrong file via SFTP while the server is running. Stop the server first, then edit, then start.

In summary

The fastest tickets to resolve are the ones where you've already done these checks. The fastest servers to recover are the ones where the owner read the console error before panicking.