01
How do I create my first game server?
1)Order your server here https://cp.cloudzor.ch access the panel, and get started.
PanelCreateGameserver

Game servers, web hosting, mods, files, performance, backups, and more — everything you need to know.
Order your server, access the panel, and get started.
1)Order your server here https://cp.cloudzor.ch access the panel, and get started.
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**. Pick game type/version, confirm wipe. Backups are not deleted unless you choose to remove them — verify before confirming.
Yes. Open a ticket for a **location migration**. We can sync data or schedule downtime depending on size and urgency.
Panel → **Startup** → Java runtime selector. Choose the version recommended by your game/modpack (Java 8, 11, 17, 21). Restart to apply.
We support Minecraft (Java/Bedrock), Counter-Strike 2, Rust, ARK, Palworld, Valheim, Discord bots, Node.js apps, and many more. Check our games list or ask support.
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/Network graphs in real-time. Monitor your server performance directly from the panel.
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 files via SFTP to root or specific folders. Set the correct startup file in the panel. Ensure dependencies match.
Plugins → /plugins. Forge/Fabric mods → /mods. Worlds → /world (and nether/end folders for Minecraft). 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 folders 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. Download backups anytime for off-site 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.
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.
Check the crash reports in /crash-reports or logs in /logs. Common causes: outdated mods, incompatible plugins, insufficient RAM. Share logs with support for help.
Choose a server location nearest to your players. Keep game versions and plugins updated. Avoid packet-heavy mods.
IP addresses, custom domains, and connectivity.
Panel → server → Overview shows hostname/IP and the primary port. Use this to connect to your game server.
Create an **SRV** record pointing your domain to the hostname/IP and port. For Minecraft: _minecraft._tcp.yourdomain.com → yourserver.host:25565
Use a proxy like BungeeCord, Velocity (Minecraft) or configure a reverse proxy for other games with distinct backend ports.
Stop conflicting service or pick a free port in the panel settings. Restart the server to apply changes.
Yes. Point an A record or SRV record to your server IP. For web hosting, add an A record to your server IP and configure SSL.
DDoS protection, access control and safe practices.
Yes. Always-on network-level mitigation tuned for game traffic. If you expect targeted attacks, let us know to fine-tune rules.
Use strong unique passwords, enable 2FA, never share logins. Prefer SFTP over FTP. Revoke users you no longer need.
We monitor for abusive processes/traffic per ToS. Keep plugins from trusted sources only (Spigot, Modrinth, CurseForge).
Enable whitelist in server.properties or use /whitelist on command. Add players via /whitelist add player. Great for private servers.
Use protection plugins like WorldGuard, GriefPrevention, or CoreProtect. Enable whitelist for small private servers. Regular backups are essential.
Automate, restore, and protect your data.
Use **Schedules** → Add backup job (daily/weekly). Keep at least 3 rotations. For important servers: nightly backups plus manual before updates.
Panel → **Backups** → choose backup → Restore (overwrite) or Download. Server will restart during restoration.
Depends on your rotation settings. We recommend keeping 3-7 days of backups. You can download and store backups externally for longer retention.
Yes. Panel → Backups → Download. Keep important backups stored locally or in cloud storage (Google Drive, Dropbox) for safety.
1) Take a manual backup. 2) Note versions of mods/plugins. 3) Announce maintenance window. 4) Test on a test server if possible.
Websites, databases, SSL and email.
Use SFTP or the File Manager in the panel. Upload to /public_html or /htdocs. Set correct permissions (755 for folders, 644 for files).
Yes. Free Let's Encrypt SSL certificates via the panel. Auto-renewal included. For custom SSL, upload via the SSL/TLS section.
Panel → Databases → Create. Note the credentials. Use phpMyAdmin for management or connect remotely with the provided host/port.
Create email accounts in Panel → Email. Configure IMAP/SMTP in your mail client. SPF/DKIM records are auto-configured.
Use 1-click installer if available, or upload WordPress files via SFTP, create a MySQL database, and run the installer at yourdomain.com/wp-admin/install.php
Create an A record pointing to your server IP. Wait for DNS propagation (up to 24h). Then add the domain in the panel.
MySQL, PostgreSQL — setup and optimization.
Panel → Databases → Create → enter name and password. Use phpMyAdmin for MySQL or pgAdmin for PostgreSQL.
Whitelist your IP in the database settings. Use the provided host and port. Enable SSL/TLS if available. Use strong passwords.
Use phpMyAdmin to export (mysqldump). Download regularly. To restore, import the .sql file via phpMyAdmin or command line.
Install database plugin (e.g., MySQL for Minecraft). Configure connection in plugin config with host, port, database name, username and password.
Payment, scaling, and refunds.
Monthly or yearly (discount). Automatic renewal via your payment method. Cancel anytime from the Client Area.
Client Area → Services → Upgrade/Downgrade. Choose new plan. Pro-rated billing applies. Some upgrades are instant; large changes may need brief downtime.
We offer refunds within the first 7 days if you are not satisfied. After that, we will work with you to resolve any issues per our policy.
Credit/debit cards, PayPal, and regional options. Invoices are available in the Client Area for download.
Service is suspended after grace period. Data is kept for 7 days, then deleted. Renew to restore access. Set up auto-renewal to avoid interruption.
What is allowed, copyright, and privacy.
Malware, DDoS attacks, illegal content, mass spam, or anything violating applicable laws. See ToS/AUP for full list.
We forward valid DMCA notices with details and a resolution window. Repeated or severe cases can lead to suspension.
We handle your data per Privacy Policy and GDPR compliance. Data stays in your chosen region. We do not sell your data.
No. We require legitimate game licenses. Hosting cracked servers violates ToS and game publishers rights.
How to get help fast.
Open a ticket with logs, server ID, recent changes, and steps to reproduce. Include crash reports or error messages. More details = faster resolution.
For urgent outages, open a **Priority** ticket with details. Check Status page for service-wide incidents.
Restore the latest backup from Panel → Backups. Or ask support to help roll back. We can recover most configuration mistakes.
Yes. Open a ticket with your old host details and access. We will migrate your server and files with minimal downtime.
We handle tickets in English and German. Other languages are supported best-effort via translation.