The service starts wsgate.exe with the “-c” parameter and a file path for “wsgate.ini”. If wsgate is started manually “-c <filepath>” is mandatory. Details for wsgate.ini : Configuration doc

Port must be 3389 for normal RDP connection. Port must be 2179 for Hyper-V RDP Console. Check that the username is like “.\username” or “COMPUTER-NAME\username”. If the case disable security NLA and TLS (network level authentication, transport layer security).

If using with Hyper-V, make sure the user used to authenticate against the server is member of “Hyper-V Administrators”.

If using with Openstack: Open “Event Viewer→Windows Logs→Application”, source: “wsgate”. Entries go from top to bottom, from most recent to the oldest. Ignore the header of the log messages, example:

  The description for Event ID 256 from source wsgate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.<br>
  If the event originated on another computer, the display information had to be saved with the event.
  The following information was included with the event: 
  Request from 127.0.0.1: /css/style.css => 304 Not modified

Notice that the actual message coming from wsgate.exe is at the end (“Request from 127.0.0.1: /css/style.css ⇒ 304 Not modified”). This example states that the web server responded to the request for “/css/style.css”

When the Openstack authentication begins, the procedure starts by sending an event in the log with this message:

  Starting OpenStack token authentication

Which coresponds to the line of code

Possible message:

  OpenStack token authentication failed: URI must contain a hostname.

The message returned will be either what Openstack replied (i.e. Unauthorized) or any other error that occurred while sending the request.

Issues with Openstack can be debugged by running This Script by having Openstack keystone.rc sourced beforehand