How to Upgrade to CloudGen Access Virtual Appliance v1.1.1
This guide explains how to upgrade your CloudGen Access Virtual Appliance from v1.1.0 to v1.1.1.
Note: CentOS images are deprecated and no longer recommended. If you are still hosting a CentOS image, it is strongly recommended to migrate to Ubuntu. Download and deploy the Ubuntu 22.04.5 images from How to Deploy CloudGen Access on a Virtual Appliance.
What's New in v1.1.1
v1.1.1 is a security hardening release that includes:
Unique SSH Host Keys – Each virtual appliance generates unique SSH keys on first boot.
Brute-Force Protection – Automatic blocking of IP addresses after failed login attempts.
Security Patch CVE-2026-31431 – Kernel crypto module vulnerability fixed.
Hardened SSH Configuration – Reduced authentication attempts to prevent attacks.
Important: v1.1.1 is fully compatible with v1.1.0. All CGA Proxy and Connector services work identically.
System Requirements
Before starting, confirm your environment meets these requirements.
Minimum:
CPU: 1 vCPU
RAM: 1024 MB
Disk: 20 GB
Network: 1 interface
Recommended:
CPU: 2 vCPU
RAM: 2048 MB
Supported Hypervisors:
VirtualBox 6.1+
VMware Fusion Pro
VMware Workstation Pro
VMware ESXi 6.7+
Hyper-V (requires VHD format conversion)
Upgrade Options
Option 1: Deploy a New v1.1.1 Virtual Appliance (Recommended)
This is the recommended approach. It ensures all security features are properly configured from the start.
Phase 1. Download and Deploy
Download the v1.1.1 OVA for your hypervisor:
Verify the download (optional but recommended):
#macOS/Linux: shasum -a 256 zts-virtual-appliance-*.ova #Windows PowerShell: Get-FileHash zts-virtual-appliance-*.ova -Algorithm SHA256Expected checksums:
Import the OVA (a portable virtual machine file) into your hypervisor:
VirtualBox: File > Import Appliance > Select OVA
VMware: File > Import > Select OVA
Accept the default settings (1 CPU, 1024 MB RAM) or adjust as needed.
Configure the network:
Recommended: Bridged networking (the VM gets its own IP on your network)
Alternative: NAT (the VM shares your host's IP)
Start the VM and log in:
Default credentials:
admin/adminYou will be required to change the password on first login.
The password must be at least 12 characters with uppercase, lowercase, numbers, and special characters.
Phase 2. Configure and Enroll
Configure network settings:
The CLI menu appears automatically after login.
Select option 1 (Configure Network).
Use the network configuration tool
nmtuito set a static IP or DHCP.
Apply system updates:
sudo apt-get update sudo apt-get upgrade -y # Check if a reboot is needed if [ -f /var/run/reboot-required ]; then sudo reboot fiRe-enroll CloudGen Access services:
Generate new enrollment tokens in the CloudGen Access Console.
Use the CLI menu to enroll Proxy and/or Connector.
The enrollment process is identical to v1.1.0.
Test services:
Verify Proxy and Connector are operational.
Check the CloudGen Access Console to confirm status.