Getting started
Order, log in and start your first server in a few minutes.
You can go from order to a running server in a few minutes. This guide walks you through it.
1. Choose a plan
Use the plan finder if you are not sure how much RAM you need, or read How much RAM do I need?. You can upgrade later without losing your world.
2. Order and pay
Create an account in the client area and pay your first invoice. Your server is created automatically as soon as the payment is confirmed. You will receive an email when it is ready.
3. Log in to the panel
- Open the control panel with the link in your welcome email or in the client area.
- Log in with the email address and password of your panel account.
- Select your server from the list.
4. Start your server
Press Start in the panel. The console shows the startup progress. When you see Done, your server is ready.
5. Join
Open Minecraft, choose Multiplayer and add your server address. See Connect to your server for the details.
Need a hand?: Ask in our Discord and we help you get started.
A tour of the panel
What every tab in the game panel does.
The panel is where you control your server. The exact tabs can differ a little per server type, but these are the main ones.
Console
Shows live server output and lets you type commands. The buttons above it start, restart, stop or kill the server. The cards next to it show CPU, memory, disk and network usage.
Files
A file manager in your browser. Edit text files, upload, unzip, rename and delete. For large uploads use SFTP.
Schedules
Run commands or power actions automatically, for example a daily restart. See Scheduled tasks.
Users
Give friends or staff access to your server with the permissions you choose. See Add friends and staff.
Backups
Create, download and restore backups. See Backups.
Network
Shows the address and port of your server.
Startup
Settings that decide how the server starts, such as the server version. See Server type and version.
Settings
Server name, SFTP details and a reinstall button. Reinstalling can overwrite files, so create a backup first.
Tip: you do not need to click through everything. The Console, Files and Backups tabs cover most daily use.
How much RAM do I need?
A rough guide for choosing a plan, for plugin and modded servers.
There is no exact number, because it depends on your players, plugins, mods and world. Use this as a starting point, or try the plan finder.
Plugin servers (Paper, Spigot, Purpur)
- Small survival server for you and a few friends: about 2 GB.
- Around 10 to 25 players and a handful of plugins: about 4 GB.
- A community of 25 to 60 players with many plugins: about 8 GB.
- Large servers and networks: 16 GB or more.
Modded servers
Mods use much more memory, even with few players.
- Small modpacks: 4 GB is often the minimum.
- Medium and large modpacks: 6 to 8 GB.
- Very heavy packs with many players: 12 GB or more.
What makes a server need more
- More players online at the same time
- A large view distance and a big, explored world
- Many plugins, mods or big farms and redstone machines
- Large builds and many loaded entities (animals, villagers, items)
Good to know: you can upgrade at any time from the client area. If you are unsure, start smaller and watch the Memory card in the panel. See
Memory and CPU explained.
Connect to your server
Find your server address and join with Minecraft Java or Bedrock.
Find your address
Open your server in the panel. The address and port are shown on the Console and Network tab. It looks like an address plus a port, for example play.example.com:25565.
Join with Minecraft Java Edition
- Start Minecraft and choose Multiplayer.
- Choose Add Server and paste your address.
- Press Done and double-click the server.
If the port is 25565 you can leave it out. For any other port, add it after a colon.
Join with Minecraft Bedrock Edition
Bedrock players cannot join a Java server directly. See Let Bedrock players join.
Use your own domain
You can let players join with a nicer name such as play.yourname.com. See Use a custom domain.
Console and useful commands
Start, stop and run commands, and the commands you will use most.
Power buttons
- Start: starts the server.
- Restart: stops and starts the server again.
- Stop: saves the world and shuts down safely.
- Kill: forces the server to stop immediately. Only use it if the server is stuck, because unsaved progress can be lost.
Running a command
Type the command in the console field at the bottom of the console and press Enter. In the console you do not need the leading /.
Commands you will use often
list shows who is online.op PlayerName and deop PlayerName give or remove operator rights.whitelist add PlayerName lets a player join when the whitelist is on.kick PlayerName and ban PlayerName remove a player.gamemode creative PlayerName changes the game mode.time set day and weather clear change the time and weather.gamerule keepInventory true lets players keep their items after dying.save-all saves the world right now.stop shuts the server down safely.
Tip: commands from plugins, such as /spark or /lp, work the same way. Plugin commands are listed on the plugin page.
Server settings (server.properties)
What the most important settings in server.properties do.
The server.properties file holds the main settings of your server. Open it in the Files tab, change a value and restart the server to apply it.
Common settings
motd: the text shown under your server name in the server list.max-players: how many players can be online at once.difficulty: peaceful, easy, normal or hard.gamemode: the default mode for new players, for example survival or creative.pvp: set to false to disable fighting between players.view-distance: how many chunks players see. Lower this to reduce lag.simulation-distance: how far from players the world is active. Lower values help performance.white-list: set to true to only allow whitelisted players. Use together with enforce-whitelist.level-seed: the seed used when a new world is generated.spawn-protection: radius around spawn that only operators can change.
Settings you should not change
server-port: the port is set by the panel. Changing it can stop players from joining.online-mode: keep this true. It checks that players own the game. Only set it to false behind a proxy that handles logins (such as Velocity), otherwise anyone can join with any name, including as an operator.
Good to know: a wrong value can stop the server from starting. If that happens, check the console for the line that names the setting, or restore a
backup.
Whitelist, operators and bans
Control who can join and who can use admin commands.
Make your server private with a whitelist
- Run
whitelist on in the console. - Add every player with
whitelist add PlayerName. - Check the list with
whitelist list.
Players who are not on the list see a message that they are not whitelisted.
Operators (admins)
op PlayerName gives full admin rights. Be careful who you give this to.deop PlayerName removes it.
For finer control, such as moderators who can kick but not use all commands, use a permissions plugin like LuckPerms. See Recommended plugins.
Bans and kicks
kick PlayerName reason removes a player for now.ban PlayerName reason bans a player. Use pardon PlayerName to unban.ban-ip and pardon-ip work on IP addresses.
Tip: the lists are stored in the files whitelist.json, ops.json and banned-players.json. Stop the server before you edit these by hand.
Server type and version
Change between Vanilla, Paper, Fabric and others, and update your Minecraft version.
What is the difference?
- Vanilla: the normal server from Mojang, without plugins or mods.
- Paper, Spigot, Purpur: plugin servers. Paper is the most popular choice and runs faster than Vanilla.
- Fabric, Forge, NeoForge: mod loaders. Players need the same mods on their own computer.
Change the version
- Create a backup first.
- Stop the server.
- Open the Startup tab. Depending on your server type you can choose the Minecraft version or the server file there.
- Save the change and start the server.
If you cannot find the option you need, ask in our Discord and we help you.
Java version
Newer Minecraft versions need a newer Java. If the console says the Java version is too old or too new, check the Java option on the Startup tab, or ask us.
Important: a world that was opened in a newer version cannot go back to an older version. Always keep a backup before you update, and update your plugins and mods to the same version.
Scheduled tasks
Restart or run commands automatically, for example a daily restart or backup.
Schedules run actions on a timer, even when you are away.
Create a daily restart
- Open the Schedules tab and press Create Schedule.
- Give it a name such as
Daily restart and set the time. The time uses a cron format, for example minute 0 and hour 4 for 04:00. - Open the schedule and add the tasks below, in this order.
- Make sure the schedule is active.
Tasks for a friendly restart
- Send command:
say Restarting in 1 minute! - Wait: 60 seconds.
- Send power action: Restart.
More ideas
- Create a backup every night.
- Send a message to players every hour.
- Run a command at a fixed time, for example to reset a minigame.
Tip: a regular restart keeps the server fast. Restarting once a day, at a quiet time, is plenty for most servers.
Add friends and staff
Give other people access to your server without sharing your password.
You can invite other people to manage your server, without sharing your own login.
Invite someone
- Open the Users tab and press New User.
- Enter their email address.
- Choose the permissions. For example, allow the console and files but not backups or settings.
- Press Invite. They receive an email and log in with their own account.
Remove access
Open the Users tab, choose the person and press Delete.
Never share your password.: Our staff will never ask you for it either.
Start a new world
Reset your world or generate a new one with a different seed.
Backup first.: Resetting deletes your world. Create a
backup if you might want it back.
Reset the world
- Stop the server.
- Open the Files tab.
- Delete the world folders. On Paper these are
world, world_nether and world_the_end. On Vanilla and Fabric the Nether and End are inside the world folder. - Optional: set a new
level-seed in server.properties, or leave it empty for a random seed. - Start the server. A new world is generated.
The world folder name is set by level-name in server.properties. If you changed it, delete that folder instead.
Tip: to keep your player data and inventories, delete only the world folders and leave the playerdata folder alone, or restore it from your backup.
Upload or download a world
Move a world to or from your server, for example from singleplayer.
Upload a world (Java Edition)
- On your computer, find the world folder. For singleplayer it is in the
saves folder of your .minecraft directory. The folder contains a file called level.dat. - Compress the folder as a zip file. The
level.dat file must be directly inside the folder you upload, not in an extra sub folder. - Stop the server.
- Upload the zip in the Files tab (or use SFTP for large worlds) and choose Unarchive.
- Rename the folder to match
level-name in server.properties (default world), or change level-name to the folder name. Remove or rename the old world folder first. - Start the server.
Download your world
- Stop the server so no files change.
- Create a backup and download it, or download the world folder with SFTP.
Note: Java worlds only work on Java servers, and Bedrock worlds only on Bedrock servers.
Mods and plugins
The difference between plugins and mods, and how to install them.
Plugins add features to servers such as Paper. Mods change the game itself and need Forge, Fabric or a similar loader.
Plugins
- Download the plugin
.jar file for your Minecraft version, from a trusted site such as Modrinth, Hangar or SpigotMC. - Upload it to the
plugins folder with the panel file manager or SFTP. - Restart the server and check the console for errors.
Mods
- Make sure the server runs the same loader and version as the mods you want.
- Upload the mod files to the
mods folder. - Restart the server. Players need the same mods installed on their own computer.
Good habits
- Only download from official pages. Files from random sites can contain malware.
- Install one thing at a time, so you know what caused a problem.
- Create a backup before you add or update many files.
Install a modpack
Run a CurseForge or Modrinth modpack on your server.
Modpacks are a ready-made collection of mods. The steps depend on the pack, so always read the server instructions on the modpack page too.
Steps
- On the modpack page, download the server pack (not the normal client download). If there is none, the author usually explains how to build one.
- Check which Minecraft version and loader (Forge, NeoForge or Fabric) the pack needs.
- Make sure your server uses that loader and version. See Server type and version.
- Stop the server, delete old files you do not need and upload the server pack to the Files tab. Use Unarchive for zip files.
- Accept the EULA if the panel asks, and start the server.
The first start can take several minutes while files are prepared. Wait until the console shows Done.
Let players join
Players need the same modpack and version on their own computer. Share the modpack name and version with them.
Memory: most modpacks need
6 GB or more. If the server crashes while loading, see
Mod problems.
Recommended plugins
Popular, trusted plugins for Paper servers.
These plugins are widely used and well maintained. Check that you download the version for your Minecraft version.
- EssentialsX: basic commands such as homes, warps and teleporting.
- LuckPerms: permissions and ranks. Needed to give people exactly the rights you want.
- WorldEdit: builds large structures quickly with commands.
- CoreProtect: logs every block change and lets you roll back griefing.
- Spark: a profiler that shows what causes lag. See Reduce lag.
- Chunky: pre-generates your world so exploring does not cause lag.
- Geyser and Floodgate: let Bedrock players join. See Let Bedrock players join.
- ViaVersion: lets players with a newer Minecraft version join. See Let more versions join.
Tip: more plugins is not better. Every plugin uses a bit of CPU and memory, so only install what you need.
Let Bedrock players join
Let players on Bedrock Edition (console, phone, Windows 10/11) join your Java server.
Bedrock Edition and Java Edition use different protocols. With the Geyser plugin, Bedrock players can join a Java server.
Install
- Use a Paper server. See Server type and version.
- Download Geyser-Spigot and Floodgate from the official Geyser website.
- Upload both to the
plugins folder and restart the server. - Bedrock players join with your server address and the Bedrock port (default
19132, UDP).
Floodgate lets Bedrock players join without a Java account.
Good to know
- Geyser needs its own UDP port. If you need an extra port, open a ticket and we look at the options.
- Some Java-only plugins and mods do not work for Bedrock players.
- Consoles can only add a server through special tricks or a friends feature. Search for guides for your console.
Note: keep Geyser and Floodgate updated, and read the setup guide of the plugin for the newest steps.
Let more versions join
Allow players with a newer or older Minecraft version to join.
By default players must use the same Minecraft version as the server. When a new version is released, many players update at once, and your plugins may not be ready yet.
Use ViaVersion
- Download ViaVersion (for newer clients) and optionally ViaBackwards (for older clients) from their official pages.
- Upload them to the
plugins folder and restart.
Players with a different version can then join. Some blocks and items may look different for them.
Tip: this is meant to ease the transition. For the best experience everyone should use the version your server runs.
Connect with SFTP
Upload and download files with WinSCP or FileZilla.
SFTP lets you upload and download files with a program such as WinSCP or FileZilla. It is the easiest way to move large worlds or many mods.
Find your connection details
- Open your server in the panel.
- Go to Settings and look for the SFTP details.
- Copy the address, the port and your username.
Connect
- Open WinSCP or FileZilla and create a new connection.
- Choose SFTP as the protocol (not FTP).
- Fill in the address, port and username from the panel.
- Use your panel password as the password.
Tip: stop the server before you replace a world folder, so the files are not in use while you upload.
Backups
Create, download and restore backups of your server.
Backups protect your world against mistakes, broken plugins and corrupted files.
Automatic backups
Your server is backed up automatically every day. You can see the backups in the Backups tab of the panel.
Create a backup yourself
Press Create backup before you install new plugins, update your server version or change large parts of your world.
Restore or download
- Open the Backups tab.
- Choose the backup you want.
- Select Restore to put it back on your server, or Download to keep a copy on your own computer.
Lock a backup
Lock an important backup so it is not removed when old backups are cleaned up.
Good to know: restoring replaces your current files, so create a fresh backup first if you want to keep the current state. The number of backups you can keep is limited, so remove old ones you no longer need.
Reduce lag
Find and fix lag, and what the 'Can't keep up!' message means.
Lag usually means the server cannot finish its work in time. A healthy server does 20 ticks per second (TPS).
What does "Can't keep up!" mean?
The console shows this when a tick took longer than expected. Seeing it once at startup is normal. If it keeps coming back, something is overloading the server.
Find the cause with Spark
- Install the Spark plugin. See Recommended plugins.
- Run
spark profiler start --timeout 120 while the lag happens. - Open the link it prints. It shows which plugin or action uses the most time.
Quick fixes
- Lower
view-distance to about 6 to 8 and simulation-distance to about 4 to 6. See Server settings. - Pre-generate the world with Chunky, so players exploring does not cause lag.
- Use Paper instead of Vanilla.
- Remove plugins you do not use and update the rest.
- Limit large animal farms, villager halls and huge item or redstone machines.
- Restart the server regularly. See Scheduled tasks.
Memory and CPU explained
What the usage cards mean and when you need a bigger plan.
Memory
Java uses the memory it has available, so the Memory card often looks quite full, even on a quiet server. That is normal.
You only have a problem if:
- the console shows
OutOfMemoryError, - the server crashes or restarts by itself, or
- the server gets slower the longer it runs.
Then remove heavy plugins or mods, or upgrade your plan.
CPU
Minecraft mostly uses one core for the main game loop. It is normal to see high CPU while the server starts, while exploring new chunks, or while many players are online. A constant high CPU on a quiet server points to a plugin or farm. Use Spark to find it, see Reduce lag.
Disk
The Disk card shows how much of your storage is used. Worlds grow as players explore. Remove old backups and unused world folders if the disk is almost full.
Use a custom domain
Let players join with play.yourdomain.com instead of an address with a port.
If you own a domain, you can create a nicer address for your server. This is done with DNS records at the company where you bought your domain.
If your server uses the standard port 25565
Create a CNAME record that points to your server address:
- Name:
play - Type:
CNAME - Value: the address shown in your panel, without the port
Players then join with play.yourdomain.com.
If your server uses another port
Use an SRV record next to the CNAME or A record:
- Service:
_minecraft - Protocol:
_tcp - Name:
play - Priority:
0, Weight: 5 - Port: the port of your server
- Target: the address shown in your panel
Some DNS panels ask for one name instead, in the form _minecraft._tcp.play.
Cloudflare: set the record to DNS only (grey cloud). Minecraft traffic cannot go through the proxy. DNS changes can take a few minutes to an hour to work everywhere.
The server does not start
Common reasons a server stays offline or stops right after starting.
Most problems show up in the console. Read the last lines first.
Common causes
- EULA: accept it when the panel asks, or set
eula=true in eula.txt. - Memory: if it mentions memory, remove heavy plugins or upgrade your plan.
- Wrong Java version: a newer Minecraft needs a newer Java. See Server type and version.
- Plugin or mod error: the console names the file. Remove it from the
plugins or mods folder and start again. - Wrong setting: a typo in
server.properties or another config file. The console names the line. - Port in use: do not change
server-port. It is set by the panel.
How to find the problem
- Read the first error line in the console, not only the last one.
- Look at
logs/latest.log in the Files tab. - Undo the last change you made, or restore a backup.
Still stuck?: Open a ticket and include the last lines of your console. See
Contact support.
Read a crash report
Find out why your server crashed and share the right information.
When a server crashes, Minecraft writes details to files.
Where to look
logs/latest.log: the log of the current or last run.crash-reports/: a text file for each crash, named with the date and time.
How to read it
- Open the newest file.
- Look for a line that starts with
Caused by: or Description:. It often names the plugin or mod that failed. - Remove or update that plugin or mod and start again.
Share it for help
Upload the log to a paste site such as mclo.gs and share the link with us. That is easier to read than a screenshot.
Tip: never share files that contain passwords or private keys. Server logs normally do not, but check before you post them publicly.
Players cannot connect
What the common connection errors mean and how to fix them.
Check the basics
- The server must show as Online in the panel.
- Check the address and port. See Connect to your server.
- Everyone must use the same Minecraft version as the server, or use ViaVersion.
Common messages
- Connection refused / timed out: the server is offline, still starting, or the address is wrong.
- Outdated client / outdated server: the Minecraft versions do not match.
- You are not whitelisted: the player is not on the whitelist. See Whitelist, operators and bans.
- Failed to verify username / Invalid session: the player's login with Mojang failed. Restart the game and launcher, and make sure they own the game. If it happens to everyone, Mojang's login servers may be down.
- Disconnected: mod mismatch: the player does not have the same mods as the server. See Install a modpack.
- Server full: raise
max-players in server.properties or upgrade your plan.
Tip: if only one player has problems, ask them to restart their game and check their internet or firewall. If nobody can join, check the console.
Mod problems
Fix crashes and errors caused by mods and modpacks.
Missing dependency
The console says a mod needs another mod. Fabric mods often need Fabric API. Download the missing mod for the same version and loader and upload it to mods.
Wrong version or loader
A mod made for Forge does not work on Fabric, and the other way around. Mods also need to match your Minecraft version. Check the download page of each mod.
Client-only mods
Some mods (such as shaders and minimaps) only belong on the player's computer. If the server crashes with a message about the client, remove that mod from the server mods folder.
Find the broken mod
- Read the first
Caused by line in the crash report. See Read a crash report. - If it does not name a mod, remove half the mods and test, then repeat with the group that causes the crash.
Lost items or griefing
Restore a build, roll back changes or get items back.
Restore a backup
For big problems, restore a backup. Everything after the backup is lost, so create a fresh backup of the current state first if you want to keep it.
Roll back only part of the world
Install CoreProtect. It logs block changes and lets you undo them for a place and a time, without a full restore:
/co inspect shows who changed a block./co rollback user:PlayerName time:2h radius:20 undoes what that player did in the last two hours around you.
Prevent it
- Use a whitelist or a protection plugin for claims.
- Give staff only the permissions they need. See Whitelist, operators and bans.
- Keep regular backups.
Billing and renewals
Invoices, payment methods and how renewals work.
Everything about paying for your server.
Invoices and payment
You find all invoices in the client area. The available payment methods are shown at checkout and on the invoice page.
Renewals
Before each renewal you receive an invoice by email. Pay it before the due date to keep your server online. If a plan offers longer billing periods, you can pick one at checkout.
Payment problems
See Failed or late payments.
Upgrade your plan
Get more RAM and CPU without losing your world.
Upgrade
You can upgrade to a bigger plan at any time. Use the upgrade option on your service page in the client area, or open a ticket. Your world and files stay as they are.
Move to a smaller plan
Open a ticket and tell us which plan you want. Make sure your server fits in the smaller plan, for example the disk space and memory your plugins and mods need.
Failed or late payments
What happens when a payment fails or an invoice is not paid on time.
Payment failed
If a payment does not go through, you receive an email. Open the invoice in the client area and try again, or choose another payment method.
Invoice not paid on time
- After the due date an unpaid server is suspended. It stays offline until you pay.
- Pay the invoice to reactivate the server.
- If an invoice stays unpaid for too long, the server can be removed together with its data. The exact terms are in our Terms of Service.
Having trouble paying?: Open a ticket before the due date and we will help you.
Invoices and company details
Download an invoice and make sure it has the right details.
Download an invoice
- Log in to the client area and open Invoices.
- Choose the invoice.
- Download the PDF. Each invoice is also attached to the email we send you.
Correct details
Update your name and address in your account details before you pay. If you need company details on an invoice, add them to your account first, or contact us before you pay.
Cancel your server
How to cancel, and what happens to your server and data.
How to cancel
- Log in to the client area and open your service.
- Use the cancel option, or open a ticket and tell us which server you want to cancel and from when.
If you cancel at the end of the period you paid for, your server stays active until then.
Your data
After a server ends, its files are removed. Download your world and files first. See Upload or download a world.
Refunds
Refunds follow our Terms of Service.
Keep your account safe
Protect your client area and panel account.
- Use a strong, unique password and never reuse it on other sites.
- Turn on two-factor authentication for your account when the option is available, in the client area and in the panel.
- Never share your password. Give friends access with Users instead.
- We will never ask for your password. Be careful with emails or messages that ask you to log in through a link. Check that the address is really ours.
- Only install plugins and mods from trusted sources. See Mods and plugins.
Think your account is compromised?: Change your password right away and open a ticket.
Contact support
How to reach us and what to include so we can help quickly.
Where to ask
- Ticket: log in to the client area and open a ticket under Support. Best for account, billing and server problems.
- Discord: quick questions and talking to other server owners. Join through the link on our website.
What to include
- The name of your server.
- What you expected and what happened instead.
- The time it happened.
- The last lines of your console, or a link to the log or crash report. See Read a crash report.
- What you changed just before the problem started.
The more details, the faster we can solve it.