Setup, mods, files, networking, performance, backups, billing, legal and more — curated for speed.
Provision, access, reinstall — start strong in minutes.
1) Order a plan in the Client Area. 2) In the Panel → **Create Server** → choose type, location and version. 3) Click **Create**; watch the live console. 4) Start the server, accept any EULA prompts, and connect using the shown hostname/IP.
Panel → your server → **SFTP** tab. Copy host, port, username and password (or generate an app-specific password). Use FileZilla/WinSCP. Large uploads are faster via SFTP than the browser.
Panel → **Reinstall** (or **Reimage** for dedicated/VPS). Pick OS/variant, confirm wipe. Backups are not deleted unless you choose to remove them — verify before confirming.
Yes. Open a ticket for a **node/location migration**. We can live-sync data or schedule downtime depending on size and urgency.
Panel → **Startup** → Java runtime selector. Choose the version recommended by your game/modpack. Restart to apply.
Yes for VPS/Dedicated. Select a Windows image (license may apply) or mount a custom ISO. For game panels, Linux is recommended for performance.
Console, users, roles, two‑factor and API access.
Panel → server → **Users** → Invite → choose role or granular permissions (Console, Files, SFTP, Schedules, Backups). You can revoke at any time.
Yes. Create **API Keys** in the Client Area or Panel (scoped). Use them for CI/CD deploys, scheduled restarts or backup exports. Keep keys secret; rotate regularly.
Panel → **Schedules**. Add timed tasks (restart, run command, backup). Use off-peak times. Enable notifications on failure.
The live console shows CPU/RAM/Disk/I/O graphs. For deeper metrics, enable the **Agent** to push to Prometheus/Grafana (on dedicated/VPS).
Enable **Two‑Factor Auth** in your account. Avoid shared logins; use user invites with scoped permissions. Review active sessions and revoke unknown ones.
From Paper/Spigot to Fabric/Forge — install safely.
Yes. Use **1‑Click Modpacks** (where available) or upload the ZIP via SFTP. Unarchive in root, choose the correct **server JAR** in Startup, then restart.
**Paper/Spigot** → plugins & performance. **Fabric** → lightweight mod loader; great modern mods. **Forge** → huge legacy mod ecosystem; heavier. Pick based on your content.
Ensure client and server use the exact same mod versions and loader. Check the console for which dependency is missing; upload it to /mods and restart.
Yes. Upload the JAR to root (or /jar), set it as **Server Jar** in Startup. Ensure Java version matches.
Plugins → /plugins. Forge/Fabric mods → /mods. Worlds → /world (and nether/end folders). Restart afterward.
Upload, backup, move data safely (and quickly).
Zip the world folder → upload via SFTP to root → **Unarchive** → set `level-name` in server.properties to the folder name → restart.
SFTP is faster and more reliable for large files than browser uploads. Use multi‑segment clients (WinSCP, FileZilla).
Use UTF‑8 filenames. If a ZIP fails, try 7‑Zip/BetterZip and re‑archive. Ensure no nested duplicate folders after unpack.
Stop server → delete current world folder(s) or set a new world name → set `level-seed` in server.properties → start to generate a fresh world.
Backups live on protected storage. Manage in **Backups** tab. For critical data, keep an off‑site copy (object storage).
High TPS, low latency — practical, safe tweaks.
Rule of thumb (Paper/Vanilla): 2–4 GB → 1–10 players; 4–8 GB → 10–40; 8–12 GB → 40–100. Modpacks often need +50–100% RAM. High single‑core boost helps for redstone/automation.
Use modern flags (G1GC; ZGC on newer Java). Example G1GC: `-XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=100 -XX:+AlwaysPreTouch …` Set heap to ~60–70% of total RAM.
Use timings/spark to profile. Look for heavy tick events, large hoppers/farms, misbehaving plugins. Consider per‑chunk entity limits and view‑distance tuning.
Ryzen/i9 → max per‑thread clocks for game ticks. EPYC/Xeon → more cores, ECC, virtualization and multiple worlds/containers. See our CPU guidance page.
Prefer EU region nearest to your players. Keep plugins updated; avoid packet‑spam mods. Use 10G uplink configs for heavy traffic or proxies.
IPv4/IPv6, SRV records, proxies and port‑forwarding.
Panel → server → Overview shows hostname/IP and the primary port. Some games allocate additional service ports automatically.
Yes. IPv6 is available on all VPS/dedicated plans. rDNS can be set from the client area or via ticket.
Create an **SRV** record pointing your domain to the hostname/IP and port. For web panels, use **A/AAAA** and enable SSL in the panel.
Use a proxy (e.g., BungeeCord/Velocity) or haproxy/NGINX on a dedicated/VPS, with distinct backend ports.
Stop conflicting service or pick a free port. Rebooting can free orphaned listeners. Check `lsof -i :PORT` on dedicated/VPS.
DDoS, backups, access control and safe practices.
Yes. Always‑on network‑level mitigation tuned for game and realtime traffic. If you expect targeted attacks, tell us to fine‑tune rules.
Use strong unique passwords, enable 2FA, never share logins. Prefer SFTP over FTP. Revoke users you no longer need.
We don’t alter your files, but we may quarantine abusive processes/traffic per ToS. Keep plugins from trusted sources only.
Choose a region that matches your compliance needs. Data resides in the chosen location; off‑site backups follow your selections.
We contact you with details and a remediation window. Severe abuse may trigger immediate null‑routing/suspension per ToS.
Automate, restore, and test your recovery plan.
Use **Schedules** → Add backup job (daily/weekly). Keep at least 3 rotations. Heavier worlds: nightly plus on‑demand before updates.
Panel → **Backups** → choose backup → Restore (overwrite) or Download. Confirm downtime if files are large.
Snapshots are fast point‑in‑time copies on the same storage class; backups can live on separate storage and are safer for disasters.
Available on request (object storage/S3). We can wire rclone jobs for you on dedicated/VPS.
1) Take a manual backup. 2) Note versions of mods/plugins. 3) Announce maintenance. 4) Test on a staging server if possible.
Move from another host with minimal disruption.
Yes. Open a ticket with access details and a maintenance window. We’ll sync files and test before switching DNS.
Stop the old server → zip worlds/configs → download → upload to new server via SFTP → unarchive → set correct server jar → start and test.
Set low TTL on DNS/SRV 24–48h before the move, pre‑sync files, freeze writes (whitelist) during final cutover.
Different panels store configs differently. Focus on worlds, plugins/mods, and essential configs; recreate the rest.
MySQL/PostgreSQL/Redis — managed or self‑hosted.
Yes; request from the Client Area or run your own MariaDB/PostgreSQL on a VPS/dedicated for full control.
Whitelist your server IP and use TLS if available. Use a non‑default port and strong credentials.
Great for caching, queues and some plugins. Bind to localhost or protect with a firewall rule + password.
Automate dumps (mysqldump/pg_dump) to files, include them in your backup schedule, and test restores monthly.
Straightforward terms and credits when we miss targets.
Monthly or yearly (discount). Cancel anytime from the Client Area. Proration may apply on mid‑cycle upgrades.
You can scale CPU/RAM/Storage depending on plan. Some changes are instant; large storage moves may need a window.
Target **99.9%** monthly uptime. Excludes scheduled maintenance/upstream incidents. Open a ticket for credit review with timestamps.
If something breaks on our side and we can’t resolve reasonably, talk to us — we’ll do right by you within policy.
Cards, PayPal and regional options where supported. Invoices are available in the Client Area.
What’s allowed, what triggers action, how to appeal.
Malware, DDoS, illegal content, mass scanning/spam, or anything violating applicable laws. See ToS/AUP for full list.
We forward valid notices with details and a resolution window. Repeated or severe cases can lead to suspension.
We handle your data per Privacy Policy and GDPR where applicable. Logs are retained for security and billing compliance.
We require valid legal process and review requests narrowly. You will be notified unless prohibited by law.
Pick the right foundation for your workload.
Great for moderate workloads, staging, proxies, small game worlds. Fast to scale; snapshots included.
Highest consistent performance, full control, 10G/25G options, ECC memory. Best for busy communities and fleets.
Ryzen/i9 → max per‑thread; EPYC/Xeon → many cores, ECC, virtualization. See CPU guidance on the Dedicated page.
OS images, licensing, and quality‑of‑life tips.
Some Windows images include licensing costs. BYOL is possible on certain dedicated tiers — ask support.
Ubuntu LTS is a safe default. Debian is lean. Alma/Rocky for RHEL‑like environments. Use what your tooling supports.
For Windows, enable RDP with strong credentials + firewall rules. For Linux, prefer SSH keys and disable password auth.
We recommend unattended security updates on VPS/dedicated (with reboots scheduled). Pin major versions for predictability.
NVMe best practices, RAID levels and growth.
RAID1 → simple mirroring. RAID10 → performance + redundancy. RAID0 → not recommended for critical data. Always keep backups.
Ext4 is a safe default. XFS scales well for large files. ZFS adds snapshots/checksums but mind RAM needs.
Possible on many tiers. May require downtime for RAID reshape or filesystem growth. We’ll help plan it.
Avoid excessive write‑amplifying logs; rotate/compress. Keep 10–20% free for wear‑leveling.
Know before players do — alerts, health checks, status.
Yes, enable panel alerts or install our agent on VPS/dedicated to send metrics to your Prometheus/Grafana.
Panel → Audit/Activity logs show who did what and when. Use per‑user invites for accountability.
Schedules and events can hit webhooks (Discord/Slack) for restarts, backups and incident pings.
How to get fastest help and what to include.
Open a ticket with logs, timestamps, server ID, recent changes, and steps to reproduce. Mark severity if it’s an outage.
For service‑wide incidents see Status page. For dedicated outages with SLA, open a **Priority** ticket with details.
Restore the latest backup, or ask us to roll back. We can stage a safe test server to validate changes.
We handle tickets in English and German; other languages best‑effort via translation.