Admin FAQs & Troubleshooting


After finishing install the default isard-hypervisor is disabled

If you open de hypervisor details (click on + button) you will see messages from IsardVDI engine that can be useful to determine what happened. If you just finished install wizard and isard-hypervisor is disabled probably the problem is with virtualization capabilites.

Your hardware needs to have virtualization enabled. You can check that in your BIOS but also from CLI:

egrep ‘(vmx|svm)’ /proc/cpuinfo

If you see nothing in the output your CPU has no virtualization capabilites or they are disabled in BIOS. Please verify that your CPU has that capability and that it is not disabled in BIOS.


Tries to connect to localhost or incorrect IP/hostname

Disable isard-hypervisor in Hypervisors menu and check that viewer hostname is correct:

  1. Disable isard-hypervisor in Hypervisor menu
  2. Edit Hypervisor (details edit button)
  3. Check/Update viewer hostname. Should be the hostname accessible from clients.
  4. Enable isard-hypervisor again and start new domain to check viewer connection.


Can't access Isard after replacing certificates

The new certificate will be used to access your IsardVDI webserver now. Verify that it is using it in your browser (usually there will be a locker icon before url input).

  • In case it is not using new certificate check nginx isard container logs while bringing it up with docker-compose up (withouth daemonizing it with -d). There you will see information about the cert found in folder.
  • Check the certificates now in default folder /opt/isard/certs/default. Code should have generated a ca-cert.pem (server certificate extracted from fullchain). You may remove all certificates, put new ones again and start it with docker-compose up.

Which viewer connections are encrypted?

Certificate info will be shown at menu Hypervisors -> Default pool, showing that it is in Secure mode and the domain info taken from the updated cert.

You may connect to a running desktop with spice client and see [[Encrypted]] in window bar. Also connect through vnc or spice websockets and check that it is using https URI with the provided certificate. These are the viewer connections that can be encrypted using certs:

  • Spice client (remote-viewer)
  • Spice websockets (browser)
  • VNC websockets (browser)

Note that VNC client can't be encrypted and should use a tunnel as described in viewers section.

Viewer connections are not encrypted

In case it is not using certificates to access viewers after you replaced certificates and IsardVDI webserver is using it correctly, there must be a server-cert.pem error. IsardVDI extracts a ca-cert.pem from the given server-cert.pem. Please check that extracted ca-cert.pem key is the correct one with:

  • openssl x509 -in /opt/isard/certs/default/ca-cert.pem -text
  • Verify that you have a full chain with your server certificate first and then your root CA chain of certificates inside server-cert (cat myserver.pem ca-chain.pem > server-cert.pem)