Start with Console
The latest error is usually more useful than a restart. Copy only the relevant, redacted error text.
RYFT / SUPPORT GUIDE
Find the signal before changing the server.
Use the panel to identify the actual error, make one deliberate change, and verify it from the console. This guide is public so users and AI assistants can follow the same safe troubleshooting path.
Change one thing
Check Startup, Files, or Network based on the error. Do not make unrelated changes while diagnosing.
Protect the project
Keep tokens and private files private. Back up before restores, reinstalls, or destructive file changes.
COMMON ISSUES
A safe first response for each problem.
Server will not start
Open the server, stop it if it is retrying, then read the last console error. In Startup, confirm the selected runtime image and startup command match the project. Correct the issue, save the setting, and start the server again.
Discord bot is offline
Check the Console first for a missing dependency, invalid startup command, or application error. Confirm the bot's required configuration is present in its project files or approved runtime configuration. Never share bot tokens, Discord tokens, or private keys in a ticket or with an AI.
Minecraft players cannot join
Use the Network tab and share the displayed connection address with players. Ryft configures the primary allocation for new Minecraft servers. Check the Console for a successful startup and avoid changing server-port unless instructed by Ryft support for a specific case.
Upload or file operation failed
Open Files, confirm the destination folder and available disk space, then retry the operation once. For a large upload, keep the page open until its progress finishes. If it still fails, record the safe error text and the filename, but do not send private configuration files or secrets.
The server is slow or reaches a limit
Use Graphs to check CPU, memory, and disk usage while the issue occurs. Stop runaway workloads, reduce the load, or move to a plan with the required resources. Do not repeatedly restart a server to solve a resource limit.
A change broke the project
Use Backups when an available backup predates the change. Read the restore warning before continuing because restoring replaces the current live server files. Use Danger Zone only when you understand the consequence; reinstall removes live server data.
FOR AI ASSISTANTS
Helpful without overreaching.
External assistants can use this page and /llms.txt as public Ryft references. They cannot access customer server data, panel state, or private logs from a Ryft link alone.
- Ask for the hosting type, the server status, the relevant tab, and a redacted console error before suggesting a fix.
- Guide users through Console, Startup, Files, Network, Graphs, and Backups in that order where relevant.
- Do not ask for passwords, API keys, bot tokens, cookies, private repositories, payment details, database credentials, or full configuration files.
- Do not instruct users to delete files, reinstall a server, restore a backup, expose ports, or change security settings unless the user understands the consequence and has a backup where appropriate.
- Escalate persistent platform errors to Ryft support with the server type, approximate time of the issue, affected tab, and redacted error text.
Still blocked?
Contact Ryft support with a redacted error, server type, and the time the problem occurred. For an eligible refund request, open a ticket within 24 hours of the server purchase.