| Error code | Interface message | Brief description | Possible solutions |
|---|---|---|---|
Unknown Error | An error has occurred that cannot be determined by the platform. | Study the logs of the service that was accessed when the error occurred. Contact the technical support. | |
| 401 | You are not authorized, or your session has expired, please try to re-authenticate | User is not authorized. | Repeat the authorization procedure. |
| 403 | Not enough rights to perform the request | The user lacks rights to perform the request. | Contact your program administrator. |
| 404 | The page you requested was not found | Request for a non-existent interface page. | Return to the previous page using browser tools. |
| 501 | An internal server error has occurred | Internal server error. | Repeat the request. |
| 503 | Service temporarily unavailable. Please try sending the request again later | Problem with service operation. | Repeat the request. |
| 504 | Service is not responding. Please try sending the request later | Problem with service operation. | Repeat the request. |
A socket descriptor is in use | Error of the gomon monitoring service on the cluster node. | Restart the gomon service on the cluster nodes. | |
Unexpected Error | An error has occurred that cannot be detected by the platform. | Study the logs of the service that was accessed when the error occurred. Contact the technical support. | |
Platform movement already in progress | The platform migration to the virtual machine is already running. | Wait for the platform to be migrated to the virtual machine. | |
Platform not moved to VM: Supported OS is not available in the selected cluster | Failed to move the platform to the VM. There is no suitable OS template in the selected cluster. |
| |
Unauthorized | The request was executed without authorization. | Make sure that the request is executed under the authorized user name. | |
User not found | User not found. | Select an existing user. | |
Template not found | The requested OS template is missing. | Select an existing OS template. | |
| 3005 | Access denied | The user does not have permission to perform the operation. |
|
Bad request | Error in forming or processing a request. | If the request is executed via API, check the format of the request. | |
Forbidden | No permissions to execute the request. | Check the permission level of the user executing the request. | |
Error response from telegram-srv: Bad request: chat not found | No Telegram chat found to send notification. | Check the notification settings for Telegram. Add chat for notifications if necessary. | |
| 3023 | Invalid Telegram chat_id | Missing or invalid Telegram chat id passed. | Verify the chat_id passed in the parameters. |
| 5006 | IP address unknown | A non-existent IP address is specified. | Specify an existing IP address. |
| 5007 | Cluster id unknown | A non-existent cluster is specified. | Specify an existing cluster. |
| 5008 | Mac id unknown | A non-existent MAC address is specified. | Specify an existing MAC address. |
| 5009 | Network id unknown | A non-existent network is specified. | Specify an existing network. |
Os id unknown | API request contains the id of the operating system, information about which is not in the platform database. | Check if the operating system with this id is contained in the platform database. | |
| 5011 | Repository id unknown | A non-existent repository is specified. | Specify an existing repository. |
| 5012 | Disk id unknown | A non-existent disk is specified. | Specify an existing disk. |
| 5014 | Can not find proper task table record | Unable to find a suitable task in the task table. | Clarify search conditions and repeat the task search. |
| 5016 | Recipe id unknown | A non-existent script for a VM is specified. | Specify an existing script. |
| 5017 | Preset id unknown | A non-existent configuration is specified. | Specify an existing configuration. |
| 5018 | Network storage unknown | A non-existent network storage is specified. | Specify an existing network storage. |
| 5019 | Storage tag unknown | A non-existent storage tag is specified. | Specify an existing storage tag. |
| 5020 | Storage unknown | A non-existent local storage is specified. | Specify an existing local storage. |
| 5021 | Host id unknown | A non-existent VM is specified. | Specify an existing VM. |
| 5022 | Account id unknown | A non-existent account is specified. | Specify an existing account. |
| 5023 | Image id unknown | A non-existent image is specified. | Specify an existing image. |
| 5024 | Ip pool id unknown | A non-existent IP address pool is specified. | Specify an existing IP address pool. |
| 5025 | Node id unknown | A non-existent cluster node is specified. | Specify an existing cluster node. |
| 5026 | Ssh key id unknown | A non-existent SSH key is specified. | Specify an existing SSH key. |
| 5027 | Os Group unknown | A non-existent OS family is specified. | Specify an existing OS family. |
| 5028 | Hetzner ip id unknown | A non-existent IP address in a cluster with the "Routing" setting type is specified. | Specify an existing IP address. |
| 5029 | Hetzner subnet id unknown | A non-existent IP address subnet in a cluster with the "Routing" setting type is specified. | Specify an existing subnet. |
| 5030 | Virt pool id unknown | A non-existent IP address pool is specified. | Specify an existing pool. |
| 5031 | Inconsistent params of ippools connect | Incorrect IP address pool parameters. | Check pool parameters. |
| 5032 | Bad interface index | Incorrect network interface index. | Check the network interface index. |
| 5033 | Different number of interfaces | The number of network interfaces differs from the required number. | Check the number of network interfaces. |
| 5034 | Must set interfaces | Incorrect network interface parameters. | Check network interface parameters. |
| 5035 | Too many interfaces | The number of network interfaces exceeds the maximum allowed. | Reduce the number of network interfaces. |
| 5036 | Two interfaces no support ipv6 | This configuration does not support IPv6 addressing. | Change the configuration or switch the addressing type to IPv4. |
| 5037 | Host interface unknown | A non-existent VM interface is specified. | Specify an existing VM interface. |
| 5038 | Node script unknown | Incorrect script specified for execution on the node. | Specify correct values in the request. |
| 5039 | Backup location unknown | A non-existent VM backup storage is specified. | Specify an existing storage. |
| 5040 | Schedule unknown | A non-existent VM backup schedule is specified. | Specify an existing schedule. |
| 5041 | Platform backup schedule unknown | A non-existent platform backup schedule is specified. | Specify an existing schedule. |
| 5042 | Platform backup storage unknown | A non-existent platform backup storage is specified. | Specify an existing storage. |
| 5043 | Platform backup unknown | A non-existent platform backup is specified. | Specify an existing copy. |
| 5046 | Storage to cluster unknown | A non-existent cluster storage is specified. | Specify an existing storage. |
| 5047 | Storage unknown | A non-existent storage is specified. | Specify an existing storage. |
| 5048 | Script variable unknown | A non-existent script variable is specified. | Specify an existing script variable. |
| 5049 | Recipe param unknown | A non-existent script parameter is specified. | Specify an existing script parameter. |
| 5050 | Ip network id unknown | A non-existent physical network is specified. | Specify an existing network. |
| 5052 | Host interface id unknown | A non-existent VM interface is specified. | Specify an existing VM interface. |
| 5053 | Node interface id unknown | A non-existent virtualization node interface is specified. | Specify an existing virtualization node interface. |
| 5054 | Node bridge id unknown | A non-existent bridge is specified. | Specify an existing bridge. |
| 5055 | Node bond id unknown | A non-existent bond is specified. | Specify an existing bond. |
| 5056 | Ip pool to cluster unknown | A non-existent IP address pool in the cluster is specified. | Specify an existing pool. |
| 5057 | Vxlan id unknown | A non-existent VxLAN is specified. | Specify an existing VxLAN. |
| 5058 | Can not find allocated ip in ipmgr | IP address not found. | Check the correctness of the IP address. |
| 5059 | Disk bus is unknown | A non-existent disk connection type is specified. | Specify an existing connection type. |
| 5060 | IP address unknown | A non-existent IP address is specified. | Specify an existing IP address. |
| 5061 | Disk backup unknown | A non-existent disk backup is specified. | Specify an existing copy. |
| 5063 | Snapshot id unknown | A non-existent VM snapshot is specified. | Specify an existing VM snapshot. |
| 5064 | Tag id unknown | A non-existent tag is specified. | Specify an existing tag. |
| 5065 | Preset disk id unknown | A non-existent disk configuration is specified. | Specify an existing configuration. |
| 5068 | Snapshots not supported | Snapshot creation is supported only in clusters with KVM virtualization and one of the following storage types: file, local LVM, network LVM, NAS. | Choose a supported virtualization or storage type. |
| 5070 | Snapshot limit exceeded | VM snapshot limit exceeded. | Delete unnecessary snapshots or increase the limit in the VM settings ("VM Snapshots" section). |
| 5071 | Snapshot with RAM is forbidden | Creating snapshots with RAM state is forbidden for this VM. | Allow saving RAM state in the VM settings ("VM Snapshots" section). |
Live migration is not available for VMs with Qcow2 format disk snapshots | The live migration of VMs with Qcow2 snapshots is not available. |
| |
| 5073 | Live migration of VMs with network LVM snapshots is not allowed | Live migration of VMs with snapshots in network LVM storage is not available. | Stop the VM or delete snapshots before migration. |
| 5075 | Migration of VMs with snapshots and storage type change is not allowed | Storage type change during migration of VMs with snapshots is not supported. | Delete snapshots or choose another node for migration. |
| 5076 | Migration of VMs with LVM snapshots is not allowed | Migration of VMs with snapshots in LVM storage is not supported. | Delete snapshots before migration. |
| 5077 | Host configuration change is forbidden for hosts with snapshots | VM configuration change is not supported for VMs with snapshots. | Delete snapshots before changing the configuration. |
| 5078 | Wrong snapshot type | Incorrect snapshot type. | Contact support. |
| 5083 | Migration of disks attached to VMs with LVM snapshots is not allowed | Migration of VM disks with snapshots in local and network LVM storage is not supported. | Delete snapshots before migration. |
| 5084 | Migration of disks, attached to VMs with snapshots and storage type change is not allowed | Storage type change during migration of VM disks with snapshots is not supported. | Delete snapshots before migration. |
| 5085 | Selected IP pool cannot be used on this type of host network interface | The selected IP pool does not match the type of the host network interface. For example, the interface belongs to the main network, but the pool is bound to an additional one. | Choose a suitable pool. |
| 5086 | Provided MAC address is already assigned to another host interface | A record exists in the database to which the specified MAC address is bound. | Specify a free MAC address. |
| 5087 | Another interface of the host is already providing connection to the selected VxLAN | The error occurs when, while creating a new interface, the user tries to bind it to a VXLAN segment that is already connected by another interface on the same VM. | Choose another VXLAN or delete the old interface. |
| 5094 | Cannot use DHCP while VM has the anti-spoofing option turned on | DHCP is enabled in the request parameters and anti-spoofing is enabled on the VM. | Disable anti-spoofing. |
| 5095 | Cannot change node bridge as it belongs to different type of network | Switching a VM's network interface to a bridge of a different network type (e.g., from main to additional) is not supported. | Choose a bridge of the same network type. |
| 5096 | Cannot allocate IP address on host interface which has DHCP turned on | Manual IP address allocation for interfaces with DHCP is not supported. | Disable DHCP for the interface. |
| 5100 | Some IP addresses are occupied by a block | Selected IP addresses intersect with an existing block. | Change the range of selected IP addresses. |
| 5101 | Network intersects with an existing one | The settings of the network being created intersect with the settings of an existing one. | Change the settings of the network being created. |
| 5102 | IP address is busy | IP address is busy. | Select another IP address. |
| 5103 | Network cannot be deleted. There is a dependent IP | The network cannot be deleted because there are dependent IP addresses. | Identify dependent IP addresses and release them. Repeat network deletion. |
| 5104 | Invalid IP | Access to an incorrect IP address. | Check IP address settings. |
| 5105 | Invalid IP range | Access to an incorrect IP address range. | Check the IP address range settings. |
| 5106 | Node cannot be deleted. There is a dependent host | The virtualization node cannot be deleted because VMs are located on it. | Delete VMs from the virtualization node, repeat node deletion. |
| 5107 | Cluster cannot be deleted. There is a dependent node | The cluster cannot be deleted, there are dependent nodes. | Delete dependent virtualization nodes, repeat cluster deletion. |
| 5108 | Node cannot be deleted. There is a dependent disk | The node cannot be deleted, because there is a dependent disk. | Delete the dependent disk. |
| 5112 | Not enough rights on object | Insufficient rights to access the object. |
|
| 5113 | There is no node in cluster | The cluster does not contain any nodes. | Add a virtualization node to the cluster. |
| 5114 | Cluster with same name already exists | A cluster with the specified name already exists. | Select a different name for the cluster. |
The VM is blocked | The error can occur if the administrator stopped the user's VM and then the VM was started by non-platform means. |
| |
| 5120 | Bad URL | Invalid URL. | Check the URL input for correctness. |
| 5121 | Source param missed | A parameter for creating a VM is missing, no OS or image. | Check the specified parameters for correctness. |
| 5123 | Cluster cannot be selected automatically | The cluster cannot be selected automatically. | Select the cluster manually. |
| 5124 | OS not available on cluster | OS is not available on the current cluster. | Select a different OS or a different cluster. |
| 5125 | Node check failed | Node cluster check failed. | Check the node server status. |
| 5126 | Host creation blocked on node | VM creation on the node is blocked. | Allow VM creation on the node. |
| 5127 | Can't find source location | Failed to find the node containing the image. | Check the availability of the required image on the nodes. |
| 5128 | Node is not ready | Node is not ready for operation. | Check node operability. |
| 5129 | Image is not available | Image is unavailable. | Check the image status. |
| 5130 | Invalid time zone | Invalid time zone. | Change the time zone. |
| 5131 | OS not available on node | OS is not available on the node. | Check the availability of the required OS on the node. |
| 5132 | Account cannot be deleted. There is a dependent host | The account cannot be deleted, there are dependent VMs. | Delete dependent VMs, repeat account deletion. |
There is no suitable node in cluster | There is no suitable node in the cluster for creating or migrating a VM. | Check if there are enough free resources on the cluster nodes. | |
Node has a bad state | Node is unavailable. | Follow the instructions in the If the cluster node is unavailable article. | |
| 5137 | Cluster doesn't have any pools | IP address pools are not connected to the cluster. | Connect the IP address pool to the cluster. |
| 5138 | Selected pools are not connected to the cluster | The selected IP address pools are not connected to the cluster. | Connect the IP address pools to the cluster. |
| 5140 | Some ips from this subnet are used in vm | The subnet contains busy IP addresses. | Select another subnet. |
| 5141 | Ip is active | IP address is used on VM. | Select another IP address. |
| 5145 | Minimal prefix in hetzner datacenter is 24 | For clusters with the "Routing" configuration type, subnet masks larger than /24 are not supported. | Specify a smaller mask. |
| 5146 | Bad ipv6 subnet prefix | IPv6 prefix value is not supported. | Specify a prefix value from 32 to 96. |
| 5147 | No connected IPv6 subnet on node | There are no IPv6 subnets on the virtualization node. | Create an IPv6 subnet. |
| 5148 | Not enough free IPv6 blocks on the node | There are no free IPv6 blocks on the node. | Release the used IPv6 address block. |
| 5149 | Invalid ssh key | Invalid SSH key. | Check the correctness of the SSH key. |
| 5151 | No disk found for host | No disk found for VM. | Check the correctness of the disk specification. |
| 5152 | No interface found for host | No interface found for VM. | Check the correctness of the interface specification. |
| 5153 | ISO count limit exceeded | The number of ISO images has been exceeded. | Delete some ISO images. |
| 5154 | ISO size is too big | The size of the ISO image exceeds the maximum allowed. |
|
| 5155 | ISO is already mounted to host | An ISO image is already connected to the VM. | Disconnect the connected ISO image. |
| 5156 | ISO check is failed | The ISO image did not pass the check. | Check the integrity of the ISO image. |
| 5159 | Backup location check failed | Failed to check the backup storage. | Check access to the storage. |
| 5160 | Operation is not allowed for remotely stored images | The operation is not supported for images stored remotely. | Select an image in local storage. |
| 5162 | Backup storage connection check failed | Backup storage connection check failed. | Check access to the storage. |
| 5163 | Platform backup schedule have no connected storage | No storage is selected in the platform backup schedule. | Select storage in the schedule settings. |
| 5164 | Failed to open platform backup file | Failed to open the platform backup file. | Check the presence and integrity of the file, if necessary, select another file, repeat the operation. |
| 5165 | Failed to start platform backup process | Failed to start platform recovery from backup. | Check the presence and integrity of the file, if necessary, select another file, repeat the operation. |
| 5166 | Bad cron expression | Cron record error. | Check the cron record format in the schedule settings. |
| 5167 | Request to service ipmgr failed | Failed to execute a request in IPmanager. | If integration with an external IPmanager is configured, check the availability of the external IPmanager. |
CPU cores number on node exceeds license limit | The number of CPU cores available under the license has been exceeded. | Follow the instructions in the article CPU core number exceeded. | |
| 5170 | VM per node limit exceeded | The number of VMs on the node exceeds the limit. | Increase the available number of VMs in the node settings. |
| 5171 | Live migration from newer to older libvirt version not allowed | Live migration with these libvirt versions is not supported. | Perform migration with VM shutdown. |
| 5172 | Host is still creating | VM is still being created. | Wait for VM creation. |
| 5173 | Host is in relocation failed state | VM is still migrating. | Wait for the migration to complete. |
| 5174 | Bridge already paired with the host interface | VM is already connected to the selected bridge. | Select another bridge. |
| 5178 | Node network settings already locked | The node's network configuration is locked for changes. | Wait for the node configuration to change. |
| 5179 | Iface/Bond can't be paired with more than one Vlanless bridge | The interface can only be connected to one bridge without VLAN. | Disconnect the interface from the connected bridge and reconnect to the required bridge. |
| 5181 | Node already have default bridge | The default bridge already exists. | Uncheck the "Default bridge for new VM" option for the default bridge and set it for the desired bridge. |
| 5182 | Invalid slave interface for bridge | The selected interface cannot be included in the bridge. | Select another interface. |
| 5183 | Interface already included to another bond/bridge | The selected interface is already included in a bond or bridge. | Disconnect the interface from the bond/bridge or select another interface. |
| 5184 | Cannot remove the default node bridge | Impossible to delete the default bridge. | Disable the "Default bridge for new VM" option for the default bridge. |
| 5185 | Some iface/bond/bridge has already used this name | The selected interface name is already in use. | Select another interface name. |
| 5190 | Bridge/Bond name matches a reserved pattern | This interface name is reserved and cannot be used. | Select another interface name. |
| 5193 | FreeBSD ip automation type only allows 'none' and 'freebsd' | For a FreeBSD OS, an IP address assignment model different from freebsd_based or none was selected. | Choose the freebsd-based or none type. |
| 5194 | Linux ip automation type cannot be 'freebsd' or 'windows' | The freebsd_based or windows_based IP address assignment model is not supported for this OS. | Choose a valid type. |
| 5195 | Cluster doesn't have any pools | IP address pools are not connected to the cluster. | Connect pools to the cluster. |
| 5196 | Invalid vxlan network | Invalid VxLAN. | Select another VxLAN. |
| 5197 | IP is already allocated in panel | IP address is reserved. | Select another IP address. |
| 5198 | IP address not found | IP address not found. | Check the correctness of the IP address selection. |
| 5199 | Create ptr record failed | Failed to create PTR record. | Check the DNSmanager 6 integration settings and DNS server availability. |
| 5200 | Update ptr record failed | Failed to update PTR record. | Check the DNSmanager 6 integration settings and DNS server availability. |
| 5201 | Delete ptr record failed | Failed to delete PTR record. | Check the DNSmanager 6 integration settings and DNS server availability. |
| 5202 | PTR with the same IP already exists | A PTR record for this IP address exists. | Delete the PTR record in DNSmanager 6. |
| 5203 | Specified disk is not linked with the specified host | The selected disk is not connected to the selected VM. | Connect the disk to the VM. |
| 5205 | Cannot change account of disk linked to host | Cannot change the owner of a disk attached to a VM. | Detach the disk from the VM and change the owner. |
| 5206 | Disk limit for the specified bus type has been reached | The number of disks for the selected connection type has been exceeded. | Select another connection type. |
| 5207 | Cannot unlink last host disk | Impossible to disconnect the only disk from the VM. | Connect an additional disk, make it the main one and disconnect the required disk. |
| 5209 | Specified host is not on the specified node | Cannot change the prefix of the IPv6 address block allocated for VMs, there are used IPv6 addresses. | Release busy IPv6 addresses. |
| 5210 | Cannot remove disk which linked to host | Cannot disconnect a disk that is not connected to the VM. | Check the correctness of the disk selection. |
| 5211 | Cannot unlink main host disk | Impossible to disconnect the main disk from the VM. | Connect an additional disk, make it the main one and disconnect the required disk. |
| 5212 | Disk already linked with host | The disk is already connected to the VM. | Check the correctness of the disk selection. |
| 5213 | Blocked for host with mounted ISO | Unavailable for a VM with a connected ISO image. | Disconnect the ISO image. |
| 5214 | Host and disk have to locate on the same node | VM and disk must be located on the same node. | Select one node for the VM and disk. |
| 5215 | Disk and host have to belong the same account | The VM and disk must have the same owner. | Select one owner for the VM and disk. |
| 5216 | Linked disk cannot migrate between nodes | The connected disk cannot be migrated between nodes. | Disconnect the disk from the VM. |
| 5217 | Migration destination is equal to source | The destination node coincides with the source node. | Select another destination node. |
| 5218 | Node has dependent host backups | The node has dependent VM backups. | Delete dependent backups. |
| 5219 | Node already exists | A node with this name already exists. | Select another node name. |
| 5222 | Disk list must contain an element with boot order equal 1 | The VM's main disk is not specified. | Specify the main disk in the request. |
| 5224 | Suitable storage is not found | No suitable storage found. | Check the status of storages, if necessary, connect additional storage. |
| 5225 | Can not migrate between clusters with different datacenter type | Impossible to migrate VMs between clusters with different network setting types. | Select a cluster with an identical network setting type. |
| 5226 | Can not migrate between clusters with different virtualization type | Migration between clusters with different virtualization types is not supported. | Choose a cluster of the same type. |
| 5227 | Can not migrate host with vxlan between clusters with Full Mesh vxlan mode | Impossible to migrate VM with VxLAN between clusters with full mesh. | Change the cluster configuration or select another cluster. |
| 5228 | Can not migrate host with vxlan between clusters with different vxlan mode | Impossible to migrate VM with VXLAN between clusters with different virtual network types. | Change the cluster configuration or select another cluster. |
| 5230 | The host is protected. It can not be deleted. | The VM is protected from deletion. | Disable VM protection ("VM Protection Settings" menu item). |
| 5231 | Several interfaces are not supported for the datacenter with the routing network model | For the "Routing" network setting type, nodes with two interfaces are not supported. | Use one node interface when connecting. |
| 5233 | Task registration error | The task cannot be registered. | Repeat the operation that caused the error. If the error occurs again, contact technical support. |
| 5236 | Node has libvirt errors | Problems with libvirt daemon on a cluster node. | Check libvirt using the instructions in the Basic diagnostics article. |
| 5237 | Node has LXD errors | LXD errors on the node. | Check the node's status. Collect logs and contact support. |
| 5238 | Task cancellation error | The task was cancelled. | Restart the task. |
| 5241 | The host is protected. No modifications are allowed | The VM is protected from modifications. | Disable VM protection ("VM Protection Settings" menu item). |
Failed to put SSH-key on node. Check your password or ~/.ssh/authorized_keys on node | An error occurs when trying to copy the platform SSH key to a cluster node or Ceph storage. |
| |
| 5245 | You don't have rights to list the snapshots of this host | The user does not have rights to get the list of snapshots for this VM. | Contact the administrator. |
Given IP does not belong to any IP-pool assigned to cluster | An error can occur when:
| Use an IP address from a pool that belongs to the cluster. | |
| 5247 | Anonymization of images is prohibited for a host with an unknown operating system | Cannot create an anonymized image for a VM for which: the OS is unknown; the OS group is unknown; the OS group is no_os or rescue. | When creating an image, disable the "Anonymize image" parameter. |
The specified amount of RAM is less than minimal requirement for this OS | The VM does not have enough RAM to install the selected OS. | Increase the amount of RAM on the VM. | |
| 5250 | ISO size value is invalid | The specified ISO image size is less than zero or exceeds the maximum allowed. | Pass correct parameters or increase the maximum ISO image size in the "Global Settings" section. |
| 5252 | Account ID is not provided | Account id is not passed in the request. | Specify the correct id in the request. |
| 5254 | No ISO currently defined for host | ISO image is not defined for the VM. | Check the specified VM and ISO image parameters. |
| 5257 | ISO is in mounted state already | An ISO image is already attached to the VM. | Detach the ISO image. |
| 5258 | HA is available only in switching network | High availability is not supported in clusters with the "Routing" and IP-fabric configuration types. | Create a cluster with the "Switching" configuration type. |
| 5259 | HA is available only in KVM | High availability is not supported in LXD clusters. | Create a KVM cluster. |
| 5261 | Storage is not attached to any cluster | Storage is not connected to a cluster. | Connect the storage to a cluster. |
| 5262 | One or more ISO from given repository still mounted on cluster VMs | Cannot delete a storage while there are ISO images attached to cluster VMs. | Detach ISO images from VMs. |
| 5263 | ISO is mounted to host | Cannot delete ISO images attached to a VM. | Detach ISO images from the VM. |
| 5267 | Repository already contains ISO with the same name | The repository already contains an ISO image with this name. | Change the name or delete the ISO image. |
| 5269 | VM is not suitable for master, problems: | The VM is not suitable for master-VM. See error text for details. | Choose a suitable VM. |
| 5273 | Overselling limit exceeded for node with master | Overselling on a node with a master-VM must not exceed 1. | Specify a permissible overselling value. |
| 5278 | RAM stick size isn't fit for hot plug | RAM increase is only supported with a step of 1024 MB. | Specify a permissible RAM value. |
Migration of VMs with snapshots between different Network LVM is not allowed. | Migration of VMs with snapshots between different Network LVM is not allowed. | Delete VM snapshots before migration. For more information about migrating VMs with snapshots, see the Snapshots of virtual machines article. | |
| 5299 | Image is not in copyable state | The image status differs from active, in_use, or copying. | Check the image state. |
| 5300 | Image is not found on node | User image not found. | Specify correct parameters. |
| 5301 | Image on node has invalid state | The image is in one of the following states: deleting, in_use, migrating. | Wait for operations to complete. |
| 5302 | Invalid network mask | Invalid network mask. | Check the correctness of the network mask input. |
| 5303 | No suitable network | No suitable network. | Add a network with the required parameters. |
| 5305 | IP busy | IP address is busy. | Select another IP address. |
| 5306 | Not enough free IP in selected pools | No free addresses. | Add an IP address pool. |
License expired | License expired. | Check the license expiration date. If the license is valid, activate it. | |
| 5309 | Empty license | License data is missing. | Check the license status. |
| 5310 | Invalid license | License data is corrupted. | Re-activate the license. |
| 5313 | Not enough free IP on node | Not enough free IP addresses on the node. | Allocate more IP addresses. |
| 5314 | Image Limit Exceeded | The limit on the number of images has been reached. | Delete unused images. |
| 5315 | License file expired | License data has expired. | Check the license status. |
| 5316 | Only admin can share or set account | Only the administrator can work with accounts. | Contact the administrator. |
Nothing to change | The POST request parameters do not change anything. | Check if the POST request is necessary. If the request is necessary, change its parameters. | |
| 5320 | New disk size incorrect | Incorrect new disk size. | Specify the correct disk size. |
Insufficient space in the storage. Clear space or delete the virtual machines that you don't need | There is not enough free space in the storage. | Delete unnecessary files or virtual machines in this storage. | |
| 5322 | Image limit exceeded for host | The number of available images for this VM has been exceeded. | Delete unused images. |
| 5324 | Only FSTEC license can be used with FSTEC platform version | FSTEC VMmanager version requires a corresponding license. | Use the correct license. |
| 5325 | Can't delete immortal repository | Deleting ISPsystem repositories is not supported. | No solution. |
| 5326 | No recipe edit permissions | Insufficient permissions to edit a script. | Contact the administrator. |
| 5327 | Not enough rights for run recipe | Insufficient permissions to run a script. | Contact the administrator. |
Host is crashed | VM is crashed. | Examine the actions that led to the damage to the VM. | |
| 5331 | Limits must be assigned to a role or an account | Limits can only be assigned to a role or an account. | Pass the role or account value in the request. |
| 5332 | Unknown limits level | Limits can only be assigned to a role or an account. | Pass the role or account value in the request. |
| 5338 | Nodes limit exceeded | License limit for the number of nodes exceeded. | Check license restrictions and increase limits if necessary. |
| 5339 | Ippool has used IP | Impossible to delete the pool, there are used IP addresses. | Release used IP addresses. |
| 5342 | Empty params for run recipe | Empty parameters for running the script. | Specify the required parameters to run. |
| 5343 | Not enough CPU in node | Not enough CPU on the node. | Reduce the number of vCPUs consumed by the VM, or delete unused VMs. |
| 5344 | Not enough free RAM in node | Not enough RAM on the node. | Reduce the amount of RAM in VM resources, delete unused VMs or increase the amount of RAM on the node. |
| 5345 | The network exists but the gateway does not match | The network exists, but the gateway does not match. | Specify the correct gateway for the network. |
| 5349 | Can not connect with node | No connection to the virtualization node. | Check access to the virtualization node from the platform server. |
| 5350 | Could not delete running task | Only deferred tasks or those in the queue can be deleted. | Wait for the task to complete. |
No KVM virtualization support on node | The connected cluster node does not support hardware virtualization. | Enable hardware virtualization support in the BIOS/UEFI of the cluster node. | |
| 5353 | KVM virtualization support is disabled in BIOS settings | Hardware virtualization support is disabled in BIOS. | Check virtualization settings in the virtualization node's BIOS/UEFI. |
Сan not get node info | Unable to get cluster node information. | Check the connection to the cluster node via SSH. | |
| 5355 | Such a hostname is already used for another node in the cluster | A node with this name already exists. | Select another node name. |
| 5357 | No host for migrate | No suitable nodes for migration. | Check if nodes meet migration requirements. |
| 5356 | Can not migrate hosts from different clusters | Bulk migration for VMs from different clusters is not possible. | Perform VM migration from each cluster in turn. |
| 5359 | Can not add the node with active SELinux | Impossible to connect a node on which SELinux is running. | Disable the SELinux service on the virtualization node, repeat adding the node. |
| 5360 | Can not add the node with SELinux enabled in /etc/selinux/config | Impossible to connect a node on which SELinux is not disabled in the /etc/selinux/config file. | Disable the SELinux service in the /etc/selinux/config file on the virtualization node, repeat adding the node. |
Release data unavailable | No access to Changelog messages. | Check access to the Changelog files. If the platform uses a proxy server, check its settings. | |
| 5362 | Disk too small for selected OS | Insufficient disk size specified for the selected OS. | Increase the VM disk size. |
| 5363 | Disk too small for selected image | Insufficient disk size specified for the selected VM image. | Increase the VM disk size. |
| 5364 | No email params in license | The license does not contain information about default email settings. | Check the license status. |
Unsupported operating system on node | An unsupported OS is installed on the connecting cluster node. | Install a supported OS and reconnect the node. | |
| 5368 | Ipv6 already enabled | An IPv6 address is already assigned to the VM. | Use the existing IPv6 address or remove the IPv6 address from the VM. |
| 5369 | Ipv6 subnet already exist on node | An IPv6 subnet is already assigned to the node. | Use the existing subnet or delete it before re-creating. |
| 5370 | Only one Ipv6 subnet can exist on node | More than one IPv6 subnet is specified in the node parameters. | Pass only one IPv6 subnet in the request. |
| 5373 | Hdd overselling is only allowed for file storage | Disk space overselling is only supported for file storage, NAS, and ZFS. | Choose a supported storage. |
| 5375 | Week day is not set for weekly schedule | No day of the week is selected to run the schedule. | Select a day of the week. |
| 5376 | Month day is not set for monthly schedule | No day of the month is selected to run the schedule. | Select a day of the month. |
| 5377 | Hosts or clusters are not set for schedule | VMs or clusters are not selected in the schedule. | Select VMs or clusters. |
| 5366 | Connection timeout | Failed to connect to the node. | Check access to the virtualization node from the platform server. |
| 5371 | VM is in rescue mode | VM is in recovery mode. | Disable recovery mode. |
| 5378 | Start time is not set for schedule | No start time is selected in the schedule. | Select a start time. |
| 5379 | VM is unavailable | VM is unavailable. | Check the VM status. |
| 5382 | vCPU number is not set | The number of vCPUs is not specified. | Specify the number of vCPUs. |
| 5383 | RAM is not set | The amount of RAM is not specified. | Specify the amount of RAM. |
| 5384 | Disk size is not set | The disk size is not specified. | Specify the disk size. |
| 5385 | Not enough rights for fine-tuning settings | No rights for fine-tuning parameters. | Contact the administrator. |
| 5386 | IP fabric settings is not set for cluster | Parameters for IP-fabric configuration are not passed. | Pass correct parameters in the request. |
IP fabric cluster doesn't support the OS | An unsupported OS is installed on the connecting IP-fabric cluster node. | Install a supported OS and reconnect the node. | |
| 5388 | Unsupported operating system on cluster | The operating system is not supported by this cluster type. | Choose a suitable OS. |
| 5389 | Invalid resource value | Invalid resource value. | Specify a valid value. |
| 5390 | Domain change is forbidden | Users are forbidden from changing the VM's domain name in this cluster. | Contact the administrator. |
| 5391 | Recipe param must have a value | No value is specified for the script parameter. | Specify the parameter value. |
| 5392 | Unsupported preset of vm on cluster | Unsupported VM configuration in the cluster. | Select a supported configuration. |
| 5393 | This OS is not supported on this license type | This OS is not suitable for this license type. | Use a supported OS. |
| 5394 | No recipient were provided | No recipient of the script execution notification is specified. | Specify the notification recipient. |
| 5395 | Recipient doesn't have language | No language for the script execution notification recipient is specified. | Specify the recipient's language. |
| 5396 | Recipient doesn't have email | No email for the script execution notification recipient is specified. | Specify the recipient's email. |
| 5397 | No template was found for specified language | There is no notification template for the selected language. |
|
| 5403 | LVM is not tuned | LVM software is not installed. | Install LVM software in the cluster storage. |
| 5404 | LVM volume group is not set | LVM volume group not found. | Create a volume group in the LVM software settings. |
| 5405 | Not found suitable LVM volume group in several VGs | No volume group with a suitable name was found. | Specify a name for one of the volume groups that matches the storage settings. |
| 5406 | Not found LVM volume group with suitable name | No volume group with a suitable name was found. | Specify a name for one of the volume groups that matches the storage settings. |
| 5408 | Vm storage path not set | VM storage path not found. | Specify the storage path. |
| 5409 | Volume group name not set | Volume group not specified. | Specify the volume group in the cluster settings. |
| 5410 | OS storage path not set | Storage for OS templates is not specified. | Specify storage for OS templates. |
| 5411 | LXD cluster does not support changes for efi_boot parameter | LXD clusters do not support bootloader type selection. | No solution. |
Editing node network settings is not allowed in a cluster with an IP fabric | Changing the network settings of a node in an IP-fabric cluster is not supported. | The operation is not supported. | |
| 5416 | No suitable IPv6 subnet in selected pools | Unable to find a suitable IPv6 subnet for the virtual machine (VM). |
|
| 5502 | Image creation is not allowed | Image creation is prohibited. | Contact the administrator. |
| 5504 | Cpu overselling set lower then 0.5. Try to increase overselling over 0.5 | CPU overselling is below the allowable level. | Set the overselling value to at least 0.5. |
| 5700 | LXD cluster only supports ZFS storage | Only ZFS storage is supported in LXD clusters. | Use ZFS storage. |
| 5701 | LXD cluster only supports IP-fabric and Switching network configuration type | Only the "Switching" and IP-fabric configuration types are supported in LXD clusters. | Use the "Switching" or IP-fabric configuration type. |
| 5702 | LXD cluster do not support ISO upload | ISO upload is not supported in LXD clusters. | No solution. |
| 5703 | LXD cluster do not support second network interface | A second network interface is not supported in LXD clusters. | No solution. |
| 5706 | KVM cluster do not support ZFS storage | ZFS storage is not supported in KVM clusters. | Choose a supported storage type. |
| 5707 | LXD cluster do not support multiple disks | LXD clusters do not support working with multiple disks. | No solution. |
| 5708 | LXD cluster do not support network interface editing | Network interface editing is not supported in LXD clusters. | No solution. |
| 5709 | At least one cluster node is not active now. HA cannot be turned on | To enable high availability, there must be active nodes in the cluster. | Check node status. |
| 5902 | Storage is already attached to cluster | Storage is already connected to the cluster. | Disconnect the storage from the cluster or use another storage. |
| 5903 | Storage is not empty on cluster | Cannot delete or disconnect storage if it contains VM disks. | Delete VM disks from the storage. |
| 5904 | Main storage not found on cluster | Main storage is not connected to the cluster. | Select one of the storages as the main one. |
| 5905 | Cluster already has nodes connected with main storage. Can not connect new main storage to cluster | The cluster already has nodes connected to the main storage. Cannot connect a new main storage to the cluster. | Use the existing main storage. |
| 5906 | Storage not found on destination node | No storages found on the destination node. | Select another destination node. |
| 5907 | VM storage path is a required parameter for File storage | For file storage, it is necessary to specify the VM storage directory. | Specify the VM storage directory. |
| 5908 | Volume group is a required parameter for LVM storage | For LVM, you need to specify a volume group. | Specify a volume group. |
| 5909 | ZFS pool name is a required parameter for ZFS storage | ZFS pool name is not specified in the ZFS storage settings. | Specify the correct pool name. |
| 5910 | RBD pool name is a required parameter for Ceph storage | For Ceph, you need to specify the RBD pool name. | Specify the RBD pool name. |
| 5911 | RBD user is a required parameter for Ceph storage | For Ceph, you need to specify the RBD user. | Specify the RBD user. |
| 5912 | Storage params is a required parameter for Ceph storage | For Ceph, you need to specify storage settings. | Specify storage settings. |
| 5913 | IP address is a required parameter for Ceph storage | For Ceph, you need to specify an IP address. | Specify the storage IP address. |
| 5914 | SSH port is a required parameter for Ceph storage | For Ceph, you need to specify the SSH port. | Specify the storage SSH port. |
| 5915 | Storage is disabled on cluster | Storage is disabled in the cluster. | Enable storage. |
| 5916 | Main storage is disabled on cluster | Main storage is disabled in the cluster. | Enable main storage. |
| 5917 | Can not delete main storage. Cluster has nodes | Cannot delete main storage while nodes are connected to the cluster. | Disconnect cluster nodes. |
| 5918 | Cluster does not has storages | Storages are not connected to the cluster. | Connect storages to the cluster. |
| 5920 | Storage with same params is already attached to cluster | Storage with these parameters is already connected to the cluster. | Check the parameters of the connecting storage. |
Storage on destination node is not active | The error may occur when selecting a storage with a status other than "Active". | Check the status of the storage. If it is out of service, select another one. | |
| 5922 | Neither ceph nor cephadm utils are not found on the server | Necessary software is not installed in the Ceph storage. | Install the necessary software and configure the storage. |
| 5923 | Repository with the same name already exists | A repository with this name already exists. | Change the name of the connecting repository. |
| 5924 | Repository with the same URL already exists | A repository with this URL already exists. | Change the URL of the connecting repository. |
| 5925 | Failed to get repository metadata | Failed to get repository metadata. | Check the correctness and availability of metadata in the repository. |
Repository metadata validation failed | Incorrect repository description file metadata.json. | Correct the repository description file. | |
| 5927 | Selected OS is marked for delete | The selected OS is marked for deletion and cannot be used. | Wait for deletion and add the OS again. |
| 5929 | Selected OS has unsupported network interface | Incorrect network interface value passed. | Pass a correct value. For example, eth0 or ens33. |
| 5931 | Disk path is a required parameter for Network LVM storage | For Network LVM, you need to specify the disk path. | Specify the disk path. |
| 5932 | Storage type is unknown | Unknown storage type passed. | Pass correct parameters. |
| 5933 | Storage does not support HA cluster | The selected storage type is not supported in an HA cluster. | Select a supported storage type. |
| 5934 | Relocation is only allowed for HA clusters | VM relocation is only available in high availability clusters. | Enable high availability in the cluster. |
| 5936 | HA is disabled on cluster | Failover is disabled in the cluster. | Enable failover in the cluster settings. |
| 5939 | Can not delete node. HA has minimum node count | In an HA cluster, the minimum allowable number of nodes. Impossible to delete a node from an HA cluster.. | Add nodes to the HA cluster before deleting the target node. |
| 5941 | Only IP-fabric cluster supports data center traffic exclusion | Internal traffic exclusion is only supported for IP-fabric clusters. | Specify a cluster with the IP-fabric configuration type in the request. Verify the correctness of the cluster_id and dc_network_id parameters in the request. |
| 5943 | Range contains in network with empty gateway | No gateway is specified for the IP address range. | Specify the gateway. |
| 5944 | IP-pool contains network with empty gateway | No gateway is specified for the IP address pool. | Specify the gateway. |
| 5945 | Default bridge on node not found | Failed to find the default bridge on the node selected to create the VM. | Check if there is a default bridge for the selected network type on the node — primary or secondary. |
| 5947 | Cannot delete vxlan if it has allocated IPs | Impossible to delete VxLAN with used IP addresses. | Release busy IP addresses, repeat VxLAN deletion. |
| 5948 | VxLAN feature disabled on cluster | VxLAN usage is disabled in the cluster. | Set the "Enable virtual networks" option in the cluster settings. |
| 5950 | Vxlan settings cannot be set for IP fabric cluster | VXLAN setting changes for clusters with the IP-fabric configuration type are not supported. | No solution. |
| 5951 | Vxlan settings is not set | VxLAN settings are not specified. | Specify VxLAN settings. |
| 5952 | Vxlan route reflector does not support Bird based IP fabric | Attempt to configure VXLAN Route Reflector in a cluster where IP-Fabric uses BIRD. | Use FRR for BGP in the cluster with Route Reflector. |
| 5954 | Storage should be in active state | Storage is not active. | Check storage state. |
| 5958 | License token not found | License token not found. | Reactivate the license. |
| 5959 | Update license failed | License update failed. | Check the license status, reactivate the license. |
| 5960 | Activate license packet failed | License package activation failed. | Check the license package status, reactivate the package. |
| 5962 | Billing URL is empty | Billing link to BILLmanager is missing. | Contact support. |
| 5963 | License packet is already activated. If activated license packet is not listed in settings, try to update license | The license package is already activated. | Reactivate the license, check the package status, reactivate the package. |
| 5964 | Cannot find node with matching host filter params | Failed to find a node with matching filter parameters. | Change filter parameters. |
IP address busy | Unable to assign an IP address to the virtual machine. | Change the IP address assignment settings: select a different IP address or address pool. If the address is assigned via DHCP, check the DHCP server settings. | |
| 5969 | Disk backup doesn't belong to disk | This backup does not belong to the disk. | Pass correct parameters in the request. |
| 5970 | Add IP to ipmgr failed | Failed to add IP address to IPmanager. | Examine log files. |
| 5972 | Portstart is greater than portend | The start port of the range is greater than the end port. | Change the range settings. |
| 5973 | Filter expression validation failed | The filter value is specified incorrectly. | Specify the correct filter value. |
| 5975 | Host params doesn't match with recipe filters | VM parameters do not match the specified filter. | Change filter conditions. |
| 5976 | Not enough rights to ignore recipe filters | The user does not have enough rights to ignore filters in scripts. | Contact the administrator or disable filter ignoring. |
| 5977 | Forbidden to pass only recipes, pass additionally hosts or host_params | The recipes (script) parameter is passed in the request, but the hosts and host_params parameters are not passed. | Add the necessary parameters to the request. |
| 5980 | Cluster re-import is not available. Cluster is already imported | The cluster is already imported, re-import is not supported. | No solution. |
| 5985 | Migration between Vm5 clusters is not available | Migration between VMmanager 5 clusters is not supported. | No solution. |
| 5986 | Migration from vm6 to Vm5 cluster is not available | Migration from a VMmanager 6 cluster to a VMmanager 5 cluster is not supported. | No solution. |
| 5989 | Migration from VMmgr5 cluster to LXD isn't supported | Migration from VMmanager 5 to an LXD cluster is not supported. | Use a KVM cluster. |
| Ip automation not available | Error can occur when changing the IP address addition model or creating a VM image. |
| |
| Qemu guest agent is not available on host |
|
| |
| 5997 | ISO check timeout is exceeded | ISO image check time exceeded. | Check the integrity of the image file, repeat the download. |
| 5999 | Nodes creation with RedHat and Debian based OS in single cluster is not available | The platform does not support clusters where nodes with Red Hat-based OS and Debian-based OS are used together. | Pass correct parameters. |
| 6000 | SPICE only available on KVM cluster | SPICE is only supported in KVM clusters. | Use a KVM cluster. |
| 6001 | SPICE is disabled on cluster | SPICE is disabled in the cluster. | Allow SPICE connections in the cluster settings. |
| 6002 | SPICE is failed on node | Failed to enable SPICE on the virtualization node. | Check the node status. |
| 6004 | SPICE only available for KVM preset | SPICE is only available for VM configurations in KVM clusters. | Use a KVM cluster. |
| 6005 | SPICE is disabled on host | SPICE is disabled on the VM. | Allow SPICE connections in the VM settings. |
| 6009 | Monitoring of this node is not yet started. Please wait for awhile. | Node monitoring has not started yet. | Wait a while. |
| Operation is blocked. Node is in maintenance mode | Attempting to perform an operation on a node that is in maintenance mode. | Wait for the end of the maintenance mode. | |
| Failed to switch the node to maintenance mode | Failed to switch the node to maintenance mode. | Check if there are restrictions that prevent you from switching the node to maintenance mode. | |
Maintenance is in bad state for this handler | The cluster node cannot enter or exit maintenance mode. | Wait for the end of operations that prevent the node from changing state. | |
| 6015 | Can't initiate maintenance with evacuation when there is one node in cluster | Cannot perform evacuation when there is only one node in the cluster. | Connect an additional node. |
| 6017 | Maintenance mode was already initialized | Maintenance mode has already been initialized. | Disable maintenance mode. |
| 6018 | Maintenance mode is unavailable in HA cluster | Maintenance mode is not available in a high availability cluster. | Disable high availability. |
| 6019 | Not enough resources in cluster for evacuation plan, check logs | Insufficient resources in the cluster for VM evacuation. | Check logs for more detailed information and free up resources. |
| 6020 | Maintenance mode is unsupported on Routing cluster | Maintenance mode is not available for clusters with the "Routing" configuration type. | Use the "Switching" or IP-fabric configuration type. |
| 6021 | Maintenance mode is unsupported on LXD cluster | Maintenance mode is not available for LXD clusters. | No solution. |
| 6022 | Only NAS storage is supported for current operation | The operation will only be available when selecting NAS storage. | Select NAS storage for the operation. |
| 6023 | Only local storage is supported for current operation | Copying and migration are not available for an image created in NAS storage. | Select local storage for copying or migration. |
| 6024 | Only same NAS storage is supported for current operation | The operation will only be available when selecting NAS storage in which the VM image was created.. | Select NAS storage with the VM image. |
| 6025 | Storage params is a required parameter for Nas storage | Storage_params, which are mandatory for NAS storage, were not passed in the request. | Pass the required parameters. |
| 6026 | Nas storage path is a required parameter for Nas storage | The "Path to directory on the nodes" parameter is not specified.. | Specify the parameter value. |
| 6027 | EFI boot can be set only for NoOS | The OS bootloader cannot be started. | Create a VM without an OS to run the bootloader. |
| 6028 | Unsupported migration for this storage type | Migration is not possible for this storage type: Attempt to migrate a disk to NAS not from file storage or NAS. Attempt to migrate a disk from NAS not to file storage or NAS. Attempt to migrate a disk between two NAS storages. | Specify a supported migration type. |
| 6029 | Only unique NAS storage path can use | The value of the "Path to directory on the nodes" field must be unique. | Specify a unique parameter value. |
| 6030 | VM Balancer feature is not supported on LXD cluster | The balancer is not supported in LXD clusters. | Use a KVM cluster. |
| 6031 | VM Balancer feature is not supported on Routing cluster | The balancer is not supported in clusters with the "Routing" configuration type. | Use a KVM cluster. |
| 6032 | Only infrastructure license type is supported | NAS storage is only supported for the Infrastructure license. | Change the license type. |
| 6033 | Inter-cluster migration from or to a high availability cluster is prohibited. | Inter-cluster VM migration in clusters with high availability enabled is prohibited. | Disable high availability. |
| 6036 | No new maintenances in cluster for nodes allowed while existing maintenance with evacuation is not done | There are nodes in the cluster that are in the evacuation process. | Wait for the evacuation process to complete. |
| 6037 | HA on node cannot be disabled while HA is enabled on cluster | Attempt to disable high availability on a node in a high availability cluster. | Disable high availability in the cluster. |
| 6038 | Node does not have HA disabled failed flag set | This method should be used to disable high availability on a node only if disabling high availability in the cluster failed. | No solution. |
| 6039 | SPICE is not available on NoOS | SPICE is not available on VMs with NoOS. | Install an OS or do not specify the parameter for SPICE. |
| 6041 | URL of immortal repository cannot be modified | Modifying ISPsystem repositories is not supported. | No solution. |
| 6050 | Not enough rights for create linked-clone | Insufficient permissions to create a linked clone. | Contact the administrator. |
| 6051 | Linked-clone image id not specified | Image id for the linked clone is not passed in the request. | Pass all required parameters. |
| 6052 | Unsupported linked-clone main disk storage type | Unsupported storage type for a linked clone operation. | Select file or NAS storage. |
| 6054 | The image is used by linked-clone | Impossible to delete the VM image due to created linked clones. | Delete the linked clones created based on this image, and repeat the operation. |
| 6056 | Linked-clone inter cluster migration not available | Linked clone migration between clusters is prohibited. | Perform migration without changing the cluster. |
| 6058 | Linked-clones feature is not supported on this license type | Linked clones are not available for this license type. | Change the license type. |
| 6059 | Linked-clones feature is only available on KVM cluster | Linked clones are only available in KVM clusters. | Use a KVM cluster. |
| 6060 | Bridge with such vlan already exists on the selected node | A bridge for this VLAN already exists on the selected node. | Check the passed parameters. |
| 6062 | New VM migration is forbidden while current migration is not finished | Cannot migrate a VM that is in the migration process. | Wait for the migration process to complete. |
| 6063 | Live migration between nodes with inconsistency of OS versions | Database record about OS version is incorrect. Migration from a node with AlmaLinux OS below version 8.9 to a node with AlmaLinux OS version 8.9 and above is not supported. | Check operating system versions. |
| 6064 | Live migration between nodes with inconsistency of kernel versions | Database record about OS version is incorrect. Migration from a node with OS version kernel 5 or below to a node with OS version kernel 5 and above is not supported. | Check operating system versions. |
| 6065 | Qemu version on destination node should be equal vesion on source node or newer | Migration between nodes with a lower QEMU version is not supported. | Update QEMU on the target node. |
User already exists | A user with this email already exists. |
| |
User does not exist | The user with this email does not exist. | Check if the email in the request is correct and repeat the request. | |
Host limit exceeded | The license limit for the number of virtual machines has been exceeded. | Increase your license limit or delete some VMs. | |
| 6069 | Account cannot be deleted. There is a dependent recipe | Deleting a user who has dependent scripts is not supported. | Change the script owner or delete the user's scripts. |
| 6071 | Host limit exceeded | License limit for VM creation reached. | Increase license limits or delete unused VMs. |
| 6074 | The master cannot be in a HA cluster while there is node with overselling > 1 | A master-VM cannot be in a high availability cluster if there are nodes in it with overselling greater than 1. | Reduce the overselling value to 1 or lower. |
| 6100 | Unknown IOMMU device | There are no records in the database about the specified PCI device. | Check the correctness of the request. |
| 6101 | Cannot change PCI device mode - device is linked to host | Cannot change the mode of a PCI device that is attached to a VM. | Detach the device from the VM. |
| 6102 | Cannot change PCI device mode - device is used by node | Changing the PCI device mode is not supported for IOMMU Group 0 or if the device is used by a node, not attached to a VM, and not used for vGPU. | Check the device status. |
| 6104 | Cannot passthrough PCI device to VM with balancer. Disable balancer first. | PCI device passthrough for a VM with a balancer is not supported. | Disable the balancer before passthrough. |
| 6105 | Cannot enable balancer for VM with PCI passthrough devices. Detach PCI devices first. | Cannot enable a balancer for a VM with PCI passthrough devices. | Detach PCI devices before enabling the balancer. |
| 6106 | Cannot migrate VM with PCI passthrough devices. | Cannot migrate a VM with PCI passthrough devices. | Disable PCI device passthrough. |
| 6107 | Snapshots not supported for VM with PCI passthrough devices. | Cannot create a snapshot for a VM with PCI passthrough devices. | Disable PCI device passthrough. |
| 6108 | Cannot passthrough PCI device to VM with snapshots. Remove all VM snapshots first. | Cannot perform PCI device passthrough for a VM with snapshots. | Delete snapshots before passthrough. |
| 6109 | Cannot enable HA for VM with PCI passthrough devices. Detach PCI devices first. | Cannot enable high availability for a VM with PCI passthrough devices. | Detach PCI devices. |
| 6110 | Cannot passthrough PCI device to VM with enabled HA. Disable HA first. | Cannot perform PCI device passthrough for a VM with high availability enabled. | Disable high availability. |
| 6111 | Not enough GPUs available on the node | Insufficient graphics processors on the node. | Examine logs for more detailed information. |
Adding a node with a non-root account is not available for this OS | When connecting a node with AlmaLinux or Ubuntu OS, a user name other than root is specified. | Reconnect the node. Specify the root username. | |
| 6113 | Cannot change PCI device mode - device is failed or its mode already being modified | PCI device is not ready. The device has failed or its mode is already being changed. | Check the device status. |
| 6114 | Unknown mediated device type (vGPU profile) | Unknown vGPU profile type passed. | Pass correct parameters. |
| 6115 | No suitable devices for requested vGPU profile | No suitable device for the vGPU profile. | Check the profile and device status. |
| 6118 | Cannot change PCI device mode - device is used by vGPU device | Cannot change the mode of a PCI device while it is being used for vGPU. | Disable vGPU. |
| 6120 | Snapshots not supported for VM with vGPU. | Snapshot creation for a VM with vGPU is not supported. | Disable vGPU. |
| 6121 | Cannot enable HA for VM with vGPU. Detach vGPU profile first. | Cannot enable high availability for a VM with vGPU. | Detach vGPU. |
| 6122 | Cannot attach vGPU to VM with balancer. Disable balancer first. | Cannot attach vGPU to a VM with an enabled balancer. | Disable the balancer. |
| 6123 | Cannot attach vGPU to VM with snapshots. Remove all VM snapshots first. | Cannot attach vGPU to a VM with created snapshots. | Delete snapshots from the VM. |
| 6124 | Cannot attach vGPU to VM with enabled HA. Disable HA first. | Cannot attach vGPU to a VM with high availability. | Disable high availability. |
| 6125 | Cannot enable balancer for VM with vGPU enabled. Detach vGPU profile first. | Cannot enable a balancer on a VM with vGPU enabled. | Detach vGPU. |
| 6126 | Cannot migrate VM with vGPU. | Cannot migrate a VM with vGPU enabled. | Disable vGPU. |
| 6128 | RBAC roles must be specified. | Custom (RBAC) roles are not defined. | Pass correct parameters. |
| 6129 | RBAC roles are not found. | A non-existent custom (RBAC) role is specified. | Pass correct parameters. |
| 6130 | Groups are not found. | A non-existent user group is specified. | Pass correct parameters. |
| 6131 | Bad shebang in script | Incorrect shebang passed in the script. | Use the correct shebang format. |
| 6132 | Shebang is not supported | The passed shebang is not supported. | Specify shebang #!/bin/sh or #!/bin/bash |
| 6133 | Shell script is not supported on Windows | Shell scripts are not supported for Windows OS. | Check the specified OS. For Windows family OS |
| 6134 | PowerShell script is not supported on Linux | PowerShell scripts are not supported for Linux OS. | Check the specified OS. For Linux family OS |
| 6135 | A script cannot be shared between Windows and Linux | A script cannot be supported for both Windows OS and Linux OS. | Use separate scripts for Linux and Windows: for Linux — Shell, for Windows — PowerShell. |
| 6136 | Shebang is not supported in PowerShell scripts. | A shebang is specified for a PowerShell script. | Remove the shebang from the script. |
| 6137 | Adding a node with a non-root account is not available for this OS | An SSH user with a name other than root is not supported for this OS. | Specify the root user. |
| 6138 | LDAP user cant be edited in VMmanager | An LDAP user cannot be modified in VMmanager. | Modify the user in the LDAP source. |
| 7000 | Not yet implemented | This operation is not yet implemented. | Wait for a product update. |
Getting license from server error | Licensing service error. | Examine the licensing service logs. |
- FAQ
- Virtual machines
- How to reset password on a Windows VM?
- How to change timeout for operations with VMs?
- If the VMs status is “Unavailable”
- If the VMs status is "Suspended"
- If VMs are not created in an LXD cluster
- How to limit VM bandwidth when traffic threshold is exceeded?
- Reinstalling the operating system on a VM fails
- How to create a VM without IP addresses?
- If a VM cannot be deleted
- How to connect a USB device to a VM?
- libguestfs errors
- Clusters
- How many VMs can be created in a high availability cluster?
- How to change netfilter parameters?
- How to get the list of free IP addresses of a cluster node?
- How to configure a cluster node in OVH data center?
- If the cluster node is unavailable
- "Attempt to migrate guest to the same host" error
- How to prepare the server for a KVM cluster node
- How to disable nested virtualization?
- If the SSH key file on the cluster node is deleted
- LXD
- How to expand the port range for VNC and SPICE?
- Users
- Backups
- Troubleshooting
- "Creating snapshot failed" error
- "Failed to get cgroup backend" error
- Almalinux repositories GPG key validation error
- A standard operating system template is missing
- Backup is under 1 MB in size
- Basic diagnostics
- CPU core number exceeded
- Data not displayed in Swagger
- Diagnosing the network availability of VMs
- Error #3009 Forbidden under administrator account
- Error when deleting dataset: dataset is busy
- Failed to add default bridge
- Guest OS cannot detect virtual machine UUID
- If "Creating snapshot fail" error appears
- If a getrandom error occurs during installation
- If the LDAP server has a self-signed SSL certificate
- Known issues
- Possible issues with migration from VMmanager 5
- Possible issues with Windows OS images
- Problems of increasing CPU and RAM without rebooting the VM
- QEMU Guest Agent cannot be installed on AlmaLinux 10 from ISO
- Registry resource unavailable
- Script terminates with the error “No complete agent response found”
- Statistics not displayed
- Ubuntu 16.04 fails to boot after reinstallation
- Unidentified SCSI device during VMware migration
- VM disk size is not decreasing
- VM fails to start with error "can't add memory device"
- VMs fail to start after enabling dynamic resource changes
- Error "Cannot delete inactive domain with snapshots" when deleting VM
- Error "RuntimeError: Not found os on node" when creating or reinstalling a VM
- IP address addition model not detected when Installing OS from an ISO repository
- VM displays incorrect uptime
- Time synchronization troubleshooting
- Error "Timed out during operation: cannot acquire state change lock" when stopping or starting a VM
- Let's Encrypt certificate cannot be issued
- How-to guides
- How to change the node's main network interface?
- How do I change the IP address of the server with the platform?
- How to restart a frozen LXD container
- How to change the OS repository URL
- How to restore a deleted VM from a backup copy
- How to change a MAC address generation pattern for VM
- How to create your own script repository?
- How to change SSH keys on nodes
- How to migrate IP addresses from IPmanager 6?
- How to set up an IP check before allocation?
- How to add a physical network with a gateway from another subnet?
- How to change the VMmanager license?
- How to sign in to the platform with a key?
- How do I add drivers to the Windows template?
- How to check and restore QEMU Guest Agent?
- Disabling high availability
- How to change the network used by Docker?
- How to avoid VM disk corruption in Ceph v.16 (Pacific) or higher?
- How to change the platform's web interface ports?
- How to block access to a particular website
- How to block access to a website (IP address) for all VMs on a node
- How to group VMs by keyword
- How to edit a username for the node
- How to set up the period for automatic deletion of notifications
- Errors
- Errors list
- 0
- 401
- 403
- 404
- 501
- 503
- 504
- 1003
- 1111
- 1352
- 1354
- 3001
- 3003
- 3004
- 3005
- 3008
- 3009
- 3021
- 3023
- 5006
- 5007
- 5008
- 5009
- 5010
- 5011
- 5012
- 5014
- 5016
- 5017
- 5018
- 5019
- 5020
- 5021
- 5022
- 5023
- 5024
- 5025
- 5026
- 5027
- 5028
- 5029
- 5030
- 5031
- 5032
- 5033
- 5034
- 5035
- 5036
- 5037
- 5038
- 5039
- 5040
- 5041
- 5042
- 5043
- 5046
- 5047
- 5048
- 5049
- 5050
- 5052
- 5053
- 5054
- 5055
- 5056
- 5057
- 5058
- 5059
- 5060
- 5061
- 5063
- 5064
- 5065
- 5068
- 5070
- 5071
- 5072
- 5073
- 5075
- 5076
- 5077
- 5078
- 5083
- 5084
- 5085
- 5086
- 5087
- 5094
- 5095
- 5096
- 5100
- 5101
- 5102
- 5103
- 5104
- 5105
- 5106
- 5107
- 5108
- 5112
- 5113
- 5114
- 5117
- 5145
- 5120
- 5121
- 5123
- 5124
- 5125
- 5126
- 5127
- 5128
- 5129
- 5130
- 5131
- 5132
- 5134
- 5135
- 5137
- 5138
- 5140
- 5141
- 5146
- 5147
- 5148
- 5149
- 5151
- 5152
- 5153
- 5154
- 5155
- 5156
- 5159
- 5160
- 5162
- 5163
- 5164
- 5165
- 5166
- 5167
- 5169
- 5170
- 5171
- 5172
- 5173
- 5174
- 5178
- 5179
- 5181
- 5182
- 5183
- 5184
- 5185
- 5190
- 5193
- 5194
- 5195
- 5196
- 5197
- 5198
- 5199
- 5200
- 5201
- 5202
- 5203
- 5205
- 5206
- 5207
- 5209
- 5210
- 5211
- 5212
- 5213
- 5214
- 5215
- 5216
- 5217
- 5218
- 5219
- 5222
- 5224
- 5225
- 5226
- 5227
- 5228
- 5230
- 5231
- 5233
- 5236
- 5237
- 5238
- 5241
- 5242
- 5245
- 5246
- 5247
- 5248
- 5250
- 5252
- 5254
- 5257
- 5258
- 5259
- 5261
- 5262
- 5263
- 5267
- 5269
- 5273
- 5278
- 5280
- 5299
- 5300
- 5301
- 5302
- 5303
- 5305
- 5306
- 5308
- 5309
- 5310
- 5313
- 5314
- 5315
- 5316
- 5319
- 5320
- 5321
- 5322
- 5324
- 5325
- 5326
- 5327
- 5330
- 5331
- 5332
- 5338
- 5339
- 5342
- 5343
- 5344
- 5345
- 5349
- 5350
- 5352
- 5353
- 5354
- 5355
- 5356
- 5357
- 5359
- 5360
- 5361
- 5362
- 5363
- 5364
- 5365
- 5366
- 5368
- 5369
- 5370
- 5371
- 5373
- 5375
- 5376
- 5377
- 5378
- 5379
- 5382
- 5383
- 5384
- 5385
- 5386
- 5387
- 5388
- 5389
- 5390
- 5391
- 5392
- 5393
- 5394
- 5395
- 5396
- 5397
- 5403
- 5404
- 5405
- 5406
- 5408
- 5409
- 5410
- 5411
- 5413
- 5416
- 5502
- 5504
- 5700
- 5701
- 5702
- 5703
- 5706
- 5707
- 5708
- 5709
- 5902
- 5903
- 5904
- 5905
- 5906
- 5907
- 5908
- 5909
- 5910
- 5911
- 5912
- 5913
- 5914
- 5915
- 5916
- 5917
- 5918
- 5920
- 5921
- 5922
- 5923
- 5924
- 5925
- 5926
- 5927
- 5929
- 5931
- 5932
- 5933
- 5934
- 5936
- 5939
- 5941
- 5943
- 5944
- 5945
- 5947
- 5948
- 5950
- 5951
- 5952
- 5954
- 5958
- 5959
- 5960
- 5962
- 5963
- 5964
- 5966
- 5969
- 5970
- 5972
- 5973
- 5975
- 5976
- 5977
- 5980
- 5985
- 5986
- 5989
- 5991
- 5992
- 5997
- 5999
- 6000
- 6001
- 6002
- 6004
- 6005
- 6009
- 6010
- 6011
- 6012
- 6015
- 6017
- 6018
- 6019
- 6020
- 6021
- 6022
- 6023
- 6024
- 6025
- 6026
- 6027
- 6028
- 6029
- 6030
- 6031
- 6032
- 6033
- 6036
- 6037
- 6038
- 6039
- 6041
- 6050
- 6051
- 6052
- 6054
- 6056
- 6058
- 6059
- 6060
- 6062
- 6063
- 6064
- 6065
- 6066
- 6067
- 6068
- 6069
- 6071
- 6074
- 6100
- 6101
- 6102
- 6104
- 6105
- 6106
- 6107
- 6108
- 6109
- 6110
- 6111
- 6112
- 6113
- 6114
- 6115
- 6118
- 6120
- 6121
- 6122
- 6123
- 6124
- 6125
- 6126
- 6128
- 6129
- 6130
- 6131
- 6132
- 6133
- 6134
- 6135
- 6136
- 6137
- 6138
- 7000
- 666009
En
Es