Skip to main content
The Minecraft app installs Crafty Controller — a web admin panel for creating, configuring, starting and backing up Minecraft servers. Create a game server in Crafty after installing the panel. This guide covers configuring it on Suji. Check the version and release notes shown in the marketplace before installing or upgrading. Crafty Controller is maintained upstream; Suji provides the marketplace packaging.

​
Before you install

There’s nothing to prepare — no API keys or tokens. Crafty generates its own admin credentials on first boot. A couple of things to know up front:
  • The admin panel and the game run on two different addresses. The Crafty panel is a public HTTPS endpoint protected by Crafty login; the Minecraft server itself is reachable by players on the VM’s public IP at port 25565.
  • Review and accept the applicable Minecraft EULA when creating a server in Crafty; the game server cannot run without the required acceptance.

​
Install

Dashboard → Apps → Minecraft → Install: There are no secrets to fill in — Crafty bootstraps its own admin account. Choose a VM with headroom for Crafty and the game process. The template declares 4 GiB minimum and 6 GiB recommended memory; Medium (8 GB) is a practical starting point. The Crafty container has a 4 GiB limit shared by the servers it starts. See Recommended size. Click Deploy. Follow deployment progress until the install is running. Startup time varies with image downloads, initialization and VM capacity. You’ll see a panel URL like https://minecraft-<random>.suji.fr — that’s the Crafty admin panel (served over HTTPS on port 8443 behind the tunnel).

​
First login — find your admin password

Crafty creates an admin user on first boot and writes the initial credentials to its configuration volume. The current image does not print this password in the application logs.
  1. Open the instance’s Files tab and choose the Minecraft install’s crafty-config volume.
  2. Open default-creds.txt (container path /crafty/app/config/default-creds.txt).
  3. Use the credentials in that file to sign in at the panel URL shown by Suji.
  4. Change the password in Crafty’s user settings and delete the initial credentials file.
If the file is not visible in Files, use the per-app Terminal to read that container path. Follow Crafty’s first-login guide for recovery options.
The public https://…suji.fr panel uses the tunnel’s browser-facing certificate. Crafty’s internal self-signed certificate is not passed through to the browser. A certificate warning on the public URL is unexpected: check the hostname and report the problem instead of bypassing it.

​
Create and launch a server

Inside the Crafty panel:
  1. Click Create New Server.
  2. Choose the Minecraft type and version (e.g. Java vanilla, the version you want).
  3. Set the server name and any options (memory, world settings).
  4. Accept the Mojang EULA when prompted — required before a server will start.
  5. Click Create. Crafty downloads the server jar.
  6. From the server’s page, click Start (the play button).
Wait for the console to show the server has finished loading (Done!).

​
Connect from your Minecraft client

The game server listens on port 25565 on the VM’s public IP — this is separate from the panel URL.
  1. On the install detail page, find the Connect (Minecraft) section — it shows the public game address with a copy button.
  2. In your Minecraft Java client → Multiplayer → Add Server.
  3. Paste the address (the VM’s public IP, port 25565 is the default so you can usually omit it).
  4. Join.
Give players that same address to connect.
The current template publishes TCP 25565 for the game. It does not publish extra game ports or Bedrock UDP ports. Only one install can reserve the same public TCP port on a VPS; use a separate VPS for another server needing that port.

​
Day-to-day management

​
Troubleshooting

Read default-creds.txt from the crafty-config volume, at container path /crafty/app/config/default-creds.txt. The current image does not print it in Logs. If you’ve already changed the password and forgotten it, reset it from Crafty’s user management (with another admin account), or from the Crafty container via the Terminal.
Use the exact public HTTPS panel URL shown in Suji. Its browser-facing certificate should be valid. The internal Crafty certificate does not explain a warning on that public hostname; check DNS and the URL, then contact Suji support if it persists.
Check, in order:
  • The server is started in Crafty (green/running), not just created.
  • You accepted the EULA — a server won’t start without it.
  • Players are using the public game address (VM IP, port 25565) from the install’s Connect (Minecraft) section — not the *.suji.fr panel URL.
  • The server finished loading — the Crafty console shows Done!.
Minecraft is memory-bound. A busy server with many chunks loaded can exhaust available RAM and get OOM-killed. Check the 4 GiB container limit as well as VM memory. Reduce view-distance, simulation-distance or server allocations; moving to a larger VM alone does not raise the container limit.

​
Where things live

Uninstalling deletes these volumes by default. Choose keep data during uninstall to preserve your worlds.
  • The template declares 4 GiB minimum and 6 GiB recommended memory. Medium (8 GB) gives host headroom, while the current container remains capped at 4 GiB. A VM resize does not automatically increase that container limit.
  • Minecraft holds the active world in memory and runs the simulation tick locally — CPU and memory demand depend on the game configuration. Player count, view distance, and mods all push memory, so size up for bigger worlds.
  • If you run other apps on the same VM, remember the VM’s total CPU/memory is shared — size up accordingly.

​
Reporting issues