Skip to content
Rynox HostingRynox.
Sign inCreate account
Panelpanel.rynoxhosting.onlinePowered by FeatherPanel

Self-service

Knowledge Base

The problems that come up most, and the shortest route through them. If your issue is not here, open a ticket and quote the heading.

Before you open a ticket

Restarting the server, checking resource usage and reading the console resolves most issues in under two minutes.

Open panelAsk on Discord

Monitoring commands

On a VPS, these are the four you will use most.

  • htopLive process list — what is eating your CPU
  • nethogsPer-process network usage
  • df -hDisk space on every mount
  • free -hMemory and swap

Common issues

Server is offline

Players cannot connect and the panel shows the server stopped.

  1. Open your server in the panel and press Start. Auto-restarts can be disabled if a crash loop is in progress.
  2. Confirm the allocation still points where you think: Settings → Allocations.
  3. Check your node is healthy — if the whole node is down, the panel will say so on the server list.
  4. If it will not start, read the install or boot log at the top of the console view.

High CPU or RAM

Tick rate drops, players report lag, or the panel warns about limits.

  1. On a VPS, run htop and sort by %CPU to find the culprit. On a Minecraft server, the console shows current MSPT.
  2. Reduce render distance and simulation distance in server.properties — this is usually the single biggest win.
  3. Check for a runaway process: a stuck world, a runaway farm, or a chunk-generating task.
  4. If you are consistently at the limit, add a resource increment rather than waiting for a crash.

Cannot connect

Correct IP and port, but the connection times out.

  1. Verify the port in your allocation matches the port in server.properties (default 25565 for Java).
  2. Check the firewall on a VPS: ufw status, and confirm nothing else holds that port.
  3. Test from outside: nc -vz your_ip your_port.
  4. On a VPS, run ping google.com to confirm outbound networking works at all.

Minecraft will not install or boot

Install fails, or the server exits immediately after start.

  1. Confirm the egg or image supports your plan. Mega Builder is tested for RLCraft, Pixelmon and Create.
  2. Check the install log for an out-of-memory error — you may need more RAM than the default image assumes.
  3. Very large modpacks need both more disk and more RAM than a vanilla server. Mega Builder and above exist for this reason.
  4. Reinstall once to reset the environment, then re-upload your files.

Backups and restore

You want a copy, or you need one.

  1. Automatic backups run on the plans that include them. Take a manual one from the server → Backups view at any time.
  2. Download a backup from the same view; the link is time-limited.
  3. Restoring replaces current files. Stop the server first, or the write will race the game process.
  4. Off-server copies: tar -czf backup.tar.gz /data, then scp it to your own machine.

Using a custom JAR or plugin

You want something other than the default server.

  1. Minecraft: use 1-click mods and plugins, or upload your own jar to the file manager and point startup at it.
  2. VPS: install Java 21, drop the jar in, and run it under a service so it restarts on crash.
  3. Under Linux, use PM2 or a systemd unit rather than running the bot in a screen you can lose.

Getting started

First-time setup on a VPS. Over SSH:

ssh root@your_server_ip

apt update && apt upgrade -y        # patch the OS first
ufw allow 22/tcp                    # keep SSH reachable
ufw enable                          # then lock the rest down
ufw allow <your game ports>
fail2ban-client install fail2ban    # blunt brute-force protection

Change the root password, or better, add an SSH key and disable password login entirely.

Deploying a game server

Minecraft (Java)

  1. Install a supported Java version — Java 21 for 1.20.5 and above.
  2. Drop the server jar into the root directory.
  3. Set the startup command to java -Xms1G -Xmx<your limit> -jar server.jar nogui.
  4. Accept the EULA in eula.txt, then start.

FiveM

  1. Install the FXServer build for your artifact version.
  2. Upload your resources and server.cfg.
  3. Add your licence key from the Cfx.re dashboard.
  4. Launch with +exec server.cfg +sv_licenseKey <key>.

Discord bot

  1. Install Node.js 20 or later.
  2. Upload your bot files.
  3. Install dependencies with npm ci --omit=dev for a clean production tree.
  4. Run it under PM2 so it restarts on crash and survives a reboot.

If something goes wrong

Suspected compromise

Act now
  1. Stop the server immediately.
  2. Open a ticket — do not keep working on a compromised box.
  3. Restore the most recent known-good backup.
  4. Rotate every credential that was on the server.

Data loss

  1. Stop the server so nothing overwrites what is left.
  2. Check automatic backups in the panel first.
  3. Open a ticket with the backup and the date range you need.
  4. Do not attempt a restore on your own without asking us.

Full legal terms are in the Terms of Service, and support targets in the SLA.