Abiquo 5.2

Skip to end of metadata
Go to start of metadata

This page describes how to configure and enable WebMKS for vCenter in environments with no previous VNC configurations.

Before you begin:

  1. Install WebMKS proxy
  2. Brand the WebMKS interface as required. See Branding WMKS.


  • If any of your vCenter VMs have a VNC configuration, see Enable WebMKS for vCenter instead. It describes how to change VMs from VNC to WebMKS.

    • VMs that may have a VNC configuration are: VMs deployed using Abiquo; VMs created in ESXi before vSphere 6.5

  • Do not modify remote access or VNC configurations when WebMKS is activated because this will cause an error
  • VMs with WebMKS active will always have remote access and you cannot enable it or disable it in the VM


To enable the WebMKS functionality for remote access to vCenter VMs, edit the abiquo.properties file:

  1. Enable WebMKS for all VMs with no VNC configuration. 

    com.abiquo.esxi.webmks = true
  2. Define the WebMKS proxy path

    com.abiquo.esxi.webmks.proxypath = api.cloud.example.com/wsdata

    The value of the proxy path property is the FQDN and Location of the proxy in Apache on the Abiquo Server (without the protocol). 

    You may choose to operate a test environment without the WebMKS proxy. In this case, the users will need access to the websocket host and port, to reach the websocket as follows:

    wss://host:port/ticket/ticketID

Users will now be able to access VM console via WebMKS when:

  1. They are the VM owner
  2. They have the privileges to Access virtual datacenters view and Manage virtual appliances. By default the standard user has these privileges 

The VM has a VNC user and password that are not valid for WebMKS.


  • No labels