Everything you need to boot one world.

Getting started

A free server is created in three steps: enter your email, choose Java or Bedrock, and finish the account at SucksHosting ID (our external identity provider — your password never touches this site). You'll land back here with the server address and panel login waiting.

• While the node has spare capacity, servers are provisioned by hand — usually the same day.
• You'll get the address, the panel URL and a one-time panel password by email.
• Nothing is charged and no card is stored, because there is nothing to charge.

Java edition

Use the address shown in the panel in the Minecraft Java multiplayer screen. If the server hasn't finished its first boot, the connection is refused until you see "Done" in the console.

Bedrock edition

Bedrock servers run on the same node with their own port and address. In the Bedrock client, choose Add Server and paste the address and port exactly as shown — the port is required on Bedrock, unlike Java.

Java and Bedrock are separate servers. Pick one at claim time; if you want the other later, reinstall from the panel and download your world first.

Server loaders

Every server starts on Paper by default. You can switch loaders from the panel's startup tab:

Modpacks

On a 1.5 GB server, treat modpacks as an experiment rather than a plan. A small kitchen-sink pack will boot; anything with a hundred mods wants more memory than the free tier can give it. Paid tiers are being sized for exactly this.

• Upload a pack through the file manager or SFTP into a fresh directory, then point the startup jar at it.
• Do not edit user_jvm_args.txt to allocate more RAM than the panel allows — the server will be killed on boot.
• Keep a backup from *before* the first modpack boot. You will want it.

Control panel

The panel is where the server lives: live console, resource graphs, a startup command editor, scheduled tasks and backups. There is no "premium" panel tier — everything above is included on the free server.

• Console — type commands directly, or watch the crash log where it happens.
• Startup — switch jars, set the version and edit the launch flags.
• Schedules — restart nightly and run a backup before each restart.

SFTP & files

The file manager handles most edits, but for plugin folders and modpacks SFTP is faster. Use the host, port, username and password from the panel's SFTP tab — not your account email.

• Host and port are shown in the panel; the default is 2022.
• Always stop the server before replacing world folders.
• File permissions matter: the server runs as its own user, not as root.

World backups

The free tier includes one backup slot. A backup is a compressed copy of the whole server directory, not just world/, so configs and plugins come along.

• Take a backup before every update or modpack change.
• Download it to your own machine for anything you can't afford to lose.
• Restoring replaces the live directory — the server must be stopped first.

Limits