ไธญๆๆๆกฃ | English
Self-Deployed Lightweight Cloud is a lightweight KVM remote cloud platform tailored for individuals and small businesses. This project is developed based on rttys, specifically designed for users managing fewer than 50 KVM devices.
- ๐ Device Management - Online device list monitoring
- ๐ Script Deployment - Convenient script-based device addition
- ๐ฅ๏ธ Remote SSH - Web SSH remote connections
- ๐ฎ Remote Control - Web remote desktop control
- โก Batch Operations - Batch command execution capabilities
- ๐ Rapid Deployment - Quick self-deployment with simple operations
- ๐ Data Security - Private deployment with full data control
- ๐ฏ Lightweight Design - Optimized for small businesses and individual users
The following mainstream operating systems have been tested and verified
- Ubuntu 18.04 / 20.04 / 22.04 / 24.04
- Debian 11 / 12
- AlmaLinux 8 / 9
- Rocky Linux 8 / 9
- CentOS Stream 9
Component | Minimum Requirement |
---|---|
CPU | 1 cores or above |
Memory | โฅ 1 GB |
Storage | โฅ 40 GB |
KVM Device Firmware | โฅ v1.5.0 |
If your server provider uses a cloud security group (e.g., AWS, Aliyun, etc.), please make sure the following ports are open:
Port | Protocol | Purpose |
---|---|---|
443 | TCP | Web UI access |
10443 | TCP | WebSocket proxy |
5912 | TCP | Device connection |
3478 | TCP/UDP | TURN server for WebRTC support |
Run the following command as root to install GLKVM Cloud:
( command -v curl >/dev/null 2>&1 && curl -fsSL https://kvm-cloud.gl-inet.com/selfhost/install.sh || wget -qO- https://kvm-cloud.gl-inet.com/selfhost/install.sh ) | sudo bash
Once the installation is complete, access the platform via:
https://<your_server_public_ip>
The default login password for the Web UI will be displayed in the installation script output:
๐ Please check the installation console for your web login password.
- Copy script
- Run the script in the device terminal
- Devices connected to the cloud
If you just want to quickly try out GLKVM Cloud and donโt mind the browserโs certificate warning, you can skip configuring a custom domain and SSL certificate, and still access the platform via the serverโs public IP with HTTPS.
For production use, or if you need to access multiple KVM devices via subdomains, it is strongly recommended to configure your own wildcard SSL certificate (see below).
To enable full domain-based access, configure the following DNS records for your domain:
โโโโโโโโโโโโโโฌโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ Hostname โ Type โ Value โ Purpose โ
โโโโโโโโโโโโโโผโโโโโโโผโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ www โ A โ Your public IP โ Web access to the platform โ
โ * โ A โ Your public IP โ Remote access to KVMs โ
โโโโโโโโโโโโโโดโโโโโโโดโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
To avoid browser warnings, replace the default certificates with your own wildcard SSL certificate that supports both:
*.your-domain.com
(for device access)www.your-domain.com
(for platform access)
Replace the following files in:
~/glkvm_cloud/certificate
glkvm.cer
glkvm.key
After replacing the certificates, restart the GLKVM Cloud services to apply the changes:
cd ~/glkvm_cloud
docker-compose down && docker-compose up -d
Or, on systems with the Docker CLI plugin:
docker compose down && docker compose up -d
Once everything is configured, you can access the platform via your domain:
https://www.your-domain.com