VOLYX DOCUMENTATION
Volyx Server Hosting Documentation
Official documentation for using Volyx hosting and server management tools. Learn how to control servers, manage files, configure startup settings, create backups, work with databases, manage networking and troubleshoot common hosting problems.
Server Control
Use the Volyx server workspace to start, stop, restart and monitor your server. Console output is the first place to check when an application fails to start or exits unexpectedly.
Console and Logs
The Console displays application output, startup logs, warnings and errors. Reading the first meaningful error helps identify problems with runtime versions, dependencies, startup files and configuration.
Files and Configuration
The file manager allows users to browse directories, upload and download files, edit configuration files and organize project data. Important changes should be made carefully and backed up when necessary.
Backups and Recovery
Backups provide recovery points before software updates, plugin changes, configuration changes and other important operations. Always confirm that a backup completed successfully before relying on it.
Startup and Runtime
Startup settings define how the application launches. Depending on the workload, this may include Java, Node.js or Python versions, startup files, environment variables and application-specific parameters.
Network and Ports
Network settings control server allocations, addresses and ports. Applications must listen on the correct allocation to accept connections from users and other services.
Databases
Applications can use databases to store structured data. Database host, port, username, password and database name should be stored securely and never exposed publicly.
Domains and DNS
Custom domains and subdomains use DNS records to point traffic toward the correct service. DNS changes can take time to propagate and should be verified together with the application address and port.
Troubleshooting
When a server does not work, start with the Console, identify the first meaningful error, review the most recent change and verify runtime, startup and resource requirements before reinstalling or changing multiple settings at once.