Q5.How to Upgrade Kilolink Server Pro 12/30/2025 / 1388 Problem Background The upgrade of Kilolink Server Pro is basically the same as the deployment method, and supports quick upgrades. Common Troubleshooting Approaches 1. Core principles for upgrading Kilolink Server Pro During the upgrade process, it is possible to reinstall the server while keeping the original port and IP address unchanged, while also supporting the retention of historical device data (such as registration information and configuration parameters) without the need to re register the device. The following process applies to upgrading from an old version of Kilolink Server Pro, or lossless upgrading from Kilolink Server Free/Bonding to Pro version. 2. Preparation work before upgrading Confirm current version: Log in to the server webpage interface, check the version information in the "System Status" at the bottom, and confirm whether an upgrade is needed (the target version needs to be higher than the current version, such as upgrading to 1.00.0020 or above). Backup historical data (key steps): (1) If upgrading from Kilolink Server Free: its data is compatible with Pro and can be directly accessed (default storage path is/data) without the need for additional backups; (2) If upgrading from an old version of Pro, the data is stored in the installation path by default (such as/root/kilolink server). It is recommended to use the cp rf installation path/data-back command to backup to the/data-back directory to avoid data loss due to upgrade failure. Record the original port and IP: Confirm the current server's IP address (such as 192.168.1.100) and web access port (default 5000, if modified, record custom port), and ensure consistency after upgrading. 3. Upgrade steps: Reinstall the server and keep the original port and IP unchanged Log in to the server and obtain administrator privileges Log in to the server through SSH tools (such as Xshell, PuTTY), enter sudo su - to obtain root privileges, and ensure sufficient operational permissions. Execute the upgrade installation command Run the following command to download and start the upgrade program, which will automatically detect the current version and overwrite the installation of the latest version: /bin/bash <( curl -fsSL https://github.com/kiloview/klnk-server/raw/main/install.sh ) Maintain the original installation path, port, and IP configuration Installation path setting: When prompted "Where do you want to install KiloLink Server", enter the original installation path (such as default/root/Kilolink server or custom path) to ensure that the data can be retrieved by the new program. Keep port and IP: During installation, the original configuration will be automatically read without modifying the port (default 5000) and IP address. If the system prompts "Do you want to use the default port", select "Y" to keep the original port unchanged. Clean up remnants of old versions (such as upgrading from Free/Bonding) If Kilolink Server Free or Bonding has been installed before, the program will prompt "Do you want to delete the old version container?" Select "Y" to confirm the deletion and ensure that the new program runs normally (Pro will automatically be compatible with Free's historical data, and Bonding data needs to be reconfigured). Verify the upgrade results Login verification: After the upgrade is completed, log in to the web interface through the original IP and port (such as http://original IP: 5000) to confirm that the version has been updated to the target version (such as 1.00.0012). Data check: Enter "Device Management" to confirm whether the historical devices are online (if upgrading from Free, the devices will automatically connect); If upgrading from Bonding, a new device needs to be added. Port and IP confirmation: Enter ifconfig on the server terminal to check if the IP remains unchanged, and use Netstat - tunlp to confirm that the original port (such as 5000) is listening normally. 4. Common problem handling after upgrading Login still shows old version (such as Free): Reason: Due to browser caching. Solution: Clean up browser cache (e.g. Chrome: Settings → Privacy&Security → Clear historical data), or log in using incognito mode. The device cannot connect to the server: Reason: The upgraded device data is not synchronized, or the original authorization code is invalid. Solution: Restore the device to factory settings and re register with the original authorization code; If the problem persists, contact technical support( [email protected] ). Port or IP unexpected change: Reason: Incorrect configuration modification during installation. Solution: Run the installation command again, enter the original IP and port in the path setting step, or manually modify the server configuration file (refer to "System Settings → Network Configuration"). 5. Summary The upgrade of Kilolink Server Pro can be achieved by reinstalling through overlay installation, while keeping the original port and IP unchanged. The core steps are: backup data → execute upgrade commands → keep the original path/port configuration → verify device connection. Upgrading from Free can preserve device data, while upgrading from Bonding requires reconfiguring the aggregation device. If there are any abnormalities after upgrading, they can be resolved by clearing the cache or restoring the device. Previous:Q4.The difference between Kilolink Server Pro, Kilolink Server Bonding, and Kilolink Server Free Next:Q6.Difference Between Restarting Network Stream and Restarting Decoding in Kilolink Station