How to Control Your Volyx Server: Complete Panel Guide
The Volyx panel gives you the core tools required to manage your server from one place. You can control power, monitor the console, edit files, change startup settings, manage networking and create backups without directly accessing the host operating system.
The Volyx panel gives you the core tools required to manage your server from one place. You can control power, monitor the console, edit files, change startup settings, manage networking and create backups without directly accessing the host operating system.
1. Open the server you want to manage
After signing in to Volyx, open My Servers and select the server you want to manage. This opens the server workspace containing the console, files, databases, backups, networking and other management tools.
Always confirm that you are managing the correct server before restarting it, changing files or deleting anything.
2. Using the Console
The Console is the main place for observing what your server is doing. It displays startup output, application messages, warnings and errors while the server runs.
You can also send commands to the server from the same page. Available commands depend on the software you are running, such as Minecraft, Node.js or Python.
If the server suddenly stops, the Console should be the first place you check because the final output often reveals the cause.
3. Start, Restart, Stop and Kill
Power buttons do not all perform the same action. Using the correct one reduces the chance of lost or corrupted data.
Starts the server when it is offline.
Stops and starts the server again. Useful after configuration changes.
Requests a normal shutdown and allows the application to save its data.
Forces the process to terminate. Use it only when the server is frozen and does not respond to Stop.
Kill can terminate a process while it is saving or writing files. Always try Stop first.
4. Managing server files
The Files section lets you browse server folders, edit text files, upload or download files, create folders and rename files.
Before changing an important configuration file, keep a copy or create a backup. A small JSON, YAML or configuration syntax error can prevent the server from starting.
- Do not delete files unless you understand their purpose.
- Check the file type before editing it.
- Some configuration changes require a restart.
- Keep a backup before major changes.
5. Startup settings
Startup controls how the application launches. Depending on the server type, this can include the Java or Node.js version, startup file and other variables.
Avoid changing the startup command or variables randomly. If the server already works, only change values when you understand their effect.
Example: Runtime: Java 21 Startup File: server.jar Memory: managed by Volyx Server Port: assigned automatically6. Networking, address and port
The Network section shows the allocation assigned to your server, including its address and port. Applications use this allocation to receive connections.
A subdomain or custom domain can point to the server when DNS is configured correctly. Do not change the application port to a value different from its assigned allocation unless you know exactly why.
7. Creating and restoring backups
Backups protect against failed upgrades, human mistakes and damaged files. Create one before major updates, installing important mods or plugins, or changing sensitive configuration.
After creating a backup, make sure it completed successfully. An incomplete backup will not help when something goes wrong.
8. Databases
Some applications need MySQL or another database to store user or plugin data. The Databases section lets you create a database and view the credentials required by your application.
Never expose database passwords or connection credentials in public channels or screenshots.
9. Using Schedules
Schedules let you automate tasks at specific times, such as regular restarts or sending a command to the server.
Avoid unnecessary frequent restarts. Schedule tasks only when they solve a real operational need.
10. Users and permissions
If someone else needs to help manage the server, use Users or Subusers instead of sharing your personal account.
Give each person only the permissions they need. For example, someone who only needs console access should not automatically receive permission to delete backups or modify startup settings.
11. Reviewing Activity
Activity helps you understand what changed on the server and who performed the action. Review it when unexpected changes occur or when you need to trace an operation.
12. Server Settings
Settings contains general server information and configuration. Depending on the server type, additional options may be available for configuration, domains or platform-specific features.
What should you do when the server will not start?
Do not immediately delete files or reinstall the server. Troubleshoot in a predictable order.
Open Console and read the final error output.
Review the most recent file, plugin or setting you changed.
Verify Startup settings and the required runtime version.
If necessary, restore a known-good backup.
Need instructions for a specific panel feature?
Continue to Volyx Documentation for feature-specific instructions covering files, backups, networking, Startup, settings and other panel tools.
Frequently Asked Questions
What is the difference between Stop and Kill?
Stop allows the application to shut down and save normally, while Kill terminates the process forcefully.
When should I restart?
Restart when configuration or software changes require the application to reload.
Should I share my account with another administrator?
Prefer not to. Create a subuser and assign only the permissions that person needs.
When should I create a backup?
Create backups regularly and before major upgrades or important configuration changes.