Support Hub
Real humans who run Minecraft servers. Fast responses. No runaround.
Technical issues, billing questions, migrations
Community help, live updates, early access
Prefer email? We check constantly
Self-service guides for common tasks. Can't find what you need? Use the support options above.
Guides for Paper, Spigot, Fabric, Forge, and vanilla Java deployments.
Getting Started on Java
Spin up your first server, choose the right plan, and connect through the Rivix panel.
Uploading Worlds & Modpacks
Use SFTP or the drop-in console to upload custom worlds, mods, and JAR files.
Managing Plugins
Install, update, and roll back Paper/Spigot plugins without downtime.
Backups & Restores
Trigger on-demand snapshots and restore them safely to production.
How to run Bedrock worlds, configure cross-play, and manage add-ons.
Launching a Bedrock World
Provision Bedrock, configure your server properties, and share the IP with console and mobile players.
Connecting Console Players
Allow Xbox, PlayStation, and Switch players to join with custom DNS or alternative services.
Uploading Add-ons & Behavior Packs
Upload .mcaddon files or manual pack folders using the drop-in console and SFTP.
Bedrock Troubleshooting
Resolve common Bedrock issues: stuck world loads, missing packs, and outdated client warnings.
Create a server from the Rivix panel, pick your Java plan, and click deploy. You will receive panel credentials within a minute.
Select your preferred Minecraft version or upload a custom JAR through the console. Restart the server to apply changes.
Share the server address shown in the panel (hostname:port) with your community.
Use the drop-in console upload to send ZIP archives under 1 GB directly. Larger packs should be uploaded via SFTP.
After uploading, stop the server, replace the world or jar directories, and start the server again.
Keep a local copy of your pack so you can revert if needed.
Install Paper or Spigot builds for the best plugin ecosystem.
Upload .jar plugin files into the plugins folder via SFTP or the console, then restart or use /reload carefully.
Check plugin compatibility for your version before deploying to avoid crashes.
Rivix runs automatic daily snapshots. Trigger manual backups in the panel before big changes.
To restore, select the snapshot you want and click restore. The panel will confirm once the world is ready again.
Download backups locally if you prefer off-site redundancy.
Deploy a Bedrock plan from the panel. Bedrock includes the correct port configuration by default.
Edit server properties (server-name, max-players, whitelist) from the panel or config file.
Share the server address (IP:Port) with your Bedrock players.
Console players require DNS redirection or third-party services (like BedrockConnect). Document your chosen method for them.
Provide your players with step-by-step instructions so they can join without frustration.
We are evaluating in-panel tools to simplify this process—feedback is welcome.
Upload .mcaddon archives via the drop-in console. The panel will unpack them into the correct folders.
For manual uploads, connect over SFTP and copy behavior and resource packs into the minecraftbe/ folders.
Restart Bedrock to load your new content.
If the world fails to start, check your latest.log for errors about missing packs or outdated versions.
Ensure console players are using the current client version. Bedrock often requires matching minor versions.
Reach out through support@rivixservers.com if you hit a blocker—we respond quickly.
Our support team handles migrations, diagnoses weird issues, and helps you scale. No question is too small.