2.9 KiB
🔄 XC_VM Update Guide
This document describes the process of updating XC_VM via the web control panel. Follow these steps to safely update the system and avoid errors.
⚙️ Before You Start
Make sure all necessary resources are ready before updating. This helps prevent issues and data loss.
- 🔑 Administrator access to the control panel.
- 🌐 Stable internet connection.
- 💾 Server data backup (strongly recommended before starting).
⚠️ Important: Do not interrupt the update process to avoid system corruption.
🪜 Step-by-Step Instructions
Follow these steps to update via the panel. Each step is illustrated with a screenshot for convenience.
1️⃣ Go to the “Servers” Section
2️⃣ Select “Manage Servers”
3️⃣ Open the “Actions” Menu
-
Locate the server you want to update.
-
Click the Actions button — usually a dropdown menu or an icon next to the server.
4️⃣ Go to “Server Tools”
5️⃣ Run “Update Server”
-
In Server Tools, click Update Server.
-
Confirm the action if prompted (password may be required).
-
Wait for the update to complete — do not interrupt the process to avoid errors.
💻 Update via CLI
If the web panel is unavailable or you prefer the command line, the update can be triggered directly via SSH.
Connect and Run
- Connect to the server via SSH.
- If needed, make the console script executable:
sudo chmod +x /home/xc_vm/console.php
- Run the command:
sudo -u xc_vm /home/xc_vm/console.php update update
⚠️ Important: The command must run as the
xc_vmuser. Do not run it asrootdirectly.
What Happens
- The system checks GitHub for a new version.
- The update archive is downloaded and its checksum (MD5) is verified.
- The system update script stops services, applies files, and runs post-update tasks.
🧠 Notes and Recommendations
🕒 Update Duration Depends on server size and internet speed. Usually takes from a few minutes up to an hour.
✅ Post-Update Check After completion, verify server status, restart services, and ensure everything is working correctly.
⚠️ Update Errors If errors occur, check server logs (e.g., in
/home/xc_vm/update.log). If the problem persists, create an issue in the repository.




