SucksHosting

Help center

Start with the console.

Nine out of ten "my server is broken" messages are answered by the last twenty lines of the console. Here are the three failures we see most on a 1.5 GB server.

Free tier support is by email, answered by a human

The server stops right after start

Usually java.lang.OutOfMemoryError or a JVM exit with no message. On 1.5 GB there is very little headroom — a modpack plus a view distance of 12 will do it every time.

  • Lower view-distance to 6 and simulation-distance to 4.
  • Remove or trim datapacks and plugins you aren't using.
  • Don't raise the memory flags above what the panel allocates; the process gets killed.

"Unsupported class file major version"

The server jar and the Java runtime don't match. Newer Minecraft versions need a newer Java. In the panel's startup tab, pick a runtime that matches your server version — then start the server once without any custom flags to see whether it comes up.

Can't connect, but the panel says online

  • Wait for Done ( in the console — "online" in the panel only means the container is running.
  • Check the port: Bedrock needs address and port, unlike Java.
  • If you changed server-port manually, revert it; the panel assigns the port.
  • Client and server versions must match on Java.

The world is gone after a reinstall

Reinstalling an edition replaces the server directory. Backups are not deleted, so open the backup tab and restore the most recent one — then download a copy before trying again.

Before you email

Include the server address, the edition, and the last 20 lines of the console. That's usually enough for a first answer without a round trip.

Still stuck?

Email hello@suckshosting.example. One person reads it; expect a reply within a couple of days, not minutes. For account or security issues, see security.

The full reference is in the docs — including limits, loaders and backups.