When console connections are failing for vCommander® or the service portal, no information is captured about the failure in the standard vCommander logs. This is because the operation is very simple; vCommander receives the request for a console connection and constructs a URL which is passed to the client.


The URL is  the exact same one used when connecting to the vCenter web client directly, when users have to enter their own credentials to vCenter. If vCommander is passing credentials on their behalf, the URL contains the defined credentials in an encrypted string.

If you need more information about why console connections are failing, there are log files on the client computers where the connection request is originating.

Windows


On Windows computers, you can access the console connection log files under the user profile of the user making the request:


X:\Users\trodney\AppData\Local\Temp\VMware-trodney

Look for the log with a Date Modified matching the user’s connection attempt, and send that file to Embotics® support.

Linux


On Linux computers, you can access the console connection log files under the temp directory for the user profile of the user making the request:

/tmp/trodney-VMware/

Look for the log with a Date Modified matching the user’s connection attempt, and send that file to Embotics® support.