Couldn't open vCD VM console from vCloud Connector

Lensar · ‎12-30-2016

Recently, I setup a vCloud Director 8.10 and vCloud Connector 2.7.2 environment in lab.
I installed vCC 2.7.2 Server in private cloud and vCC 2.7.2 node in a vCloud Director tenant. All the functions like template copy/deploy worked fine, but when I opened the VM's VMRC console, it displayed black screen. The VMRC logs shown "connection timed out". My vCloud Director had two address 192.168.2.22 for HTTP, and 192.168.2.23 for Console Proxy. I guess it maybe a SSL issue between vCC node and Console Proxy.

Does anyone have these experience? Thanks.

bayupw · ‎12-30-2016

Did you configure the Public Addresses? VMware vCloud Director 8.10 Documentation - Public Addresses

What certificates format do you use, self signed or public CA signed?

If it is self signed, you may want to try trust the certs, trust the sites (in the browser), and add the certs (root, any intermediates) to Trusted Root & Trusted Intermediate Stores within the client computer

See this KB too: Cannot connect to vCloud Director HTML5 console with Mozilla Firefox or Google Chrome (2058496) | VM...

This KB on SSL cert sections may be useful too: Troubleshooting Virtual Machine Remote Console (VMRC) connectivity issues in VMware vCloud Director ...‌

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw

Lensar · ‎01-03-2017

Thanks for your help.

I used self-signed cert, and I also configured Public Address in vcd management page.
I can open VM console by Firefox. I just couldn't open VM console from vCloud Connector interface. When I select a VM and click to open a consoe. It displayed a black screen.

The VMRC log shown an error of "Connection timed out".

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: Log for VMware Remote Console pid=4816 version=e.x.p build=build-415252 option=BETA

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: The process is 32-bit.

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: Host codepage=windows-936 encoding=GBK

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: Host is Windows Server 2008 R2 Datacenter Edition, 64-bit Service Pack 1 (Build 7601)

2017-01-04T00:30:02.938+08:00| vmplayer| I120: VTHREAD initialize main thread 2 "vmplayer" host id 5260

2017-01-04T00:30:02.938+08:00| vmplayer| I120: POLL Using the WSAPoll API Implementation for PollDefault

2017-01-04T00:30:02.938+08:00| vthread-3| I120: VTHREAD start thread 3 "vthread-3" host id 4776

2017-01-04T00:30:02.938+08:00| vmplayer| I120: LOCALE GBK -> NULL User=804 System=804

2017-01-04T00:30:02.938+08:00| vmplayer| I120: Enabling HTTPS tunnellingSSLOpenLibrariesDirect: Loaded SSL libraries, version 9080DF, paths:

2017-01-04T00:30:02.938+08:00| mks_vmrc| I120+ libcrypto: C:\Program Files (x86)\Common Files\VMware\VMware VMRC Plug-in\Internet Explorer\libeay32.dll

2017-01-04T00:30:02.938+08:00| mks_vmrc| I120+ libssl: C:\Program Files (x86)\Common Files\VMware\VMware VMRC Plug-in\Internet Explorer\ssleay32.dll

2017-01-04T00:30:03.228+08:00| mks_vmrc| I120: FILE: FileLockDynaLink: Further process validation tools are: available

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: Debug VMX "" not found. Using standard VMX ""

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: Stats VMX "" not found. Using standard VMX ""

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: vmxFilePath=""

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: vmxFilePathDebug=""

2017-01-04T00:30:03.298+08:00| mks_vmrc| I120: vmxFilePathStats=""

2017-01-04T00:30:03.308+08:00| mks_vmrc| I120: HostDeviceInfo: Failed to enumerate host parallel ports via the registry. Could not open device map parallel port registry key.

2017-01-04T00:30:03.328+08:00| mks_vmrc| I120: Host OS: 'Windows Server 2008 R2 Datacenter Edition, 64-bit 6.1.7601, Service Pack 1', product type '3', suite mask '0x0190'.

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Foundry Init: setting up global state (1 poll threads, 0 worker threads).

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: vixLogLevel = 0

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: vixApiTraceLevel = 0

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: vixDebugPanicOnVixAssert = 0

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: vixLogRefcountOnFinalRelease = 0

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: asyncOpWarningThreshold = 1000000

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: enableSyncOpSelection = FALSE

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: enableExternalThreadInterface = TRUE

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: Vix_InitializeGlobalState: enableVigor = FALSE

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: LOCALE GBK -> NULL User=804 System=804

2017-01-04T00:30:03.438+08:00| mks_vmrc| I120: VixHost_ConnectEx: version -1, hostType 3, hostName (null), hostPort 0, options 8707

2017-01-04T00:30:03.438+08:00| mks_vmrc| W110: cui::ScheduleCallback is not initialized.

2017-01-04T00:30:03.438+08:00| vthread-4| I120: VTHREAD initialize thread 4 "vthread-4" host id 316

2017-01-04T00:30:03.448+08:00| mks_vmrc| I120: vmClientCore::RunAsMKSServer: Parent PID - 3664, instanceID - "vmrc-ax-t-{87209E9D-4A08-4421-86F9-10B6D9A13D6A}"

2017-01-04T00:30:03.448+08:00| mks_vmrc| I120: vmClientCore::RunAsMKSServer: eventName = "VMRC_EVENT_vmrc-ax-t-{87209E9D-4A08-4421-86F9-10B6D9A13D6A}", monikerName = "VMRC_MONIKER_vmrc-ax-t-{87209E9D-4A08-4421-86F9-10B6D9A13D6A}", monikerEvent = 3F8

2017-01-04T00:30:03.448+08:00| mks_vmrc| W110: IMonikerImpl::vmClientCore::MonikerImpl<class vmClientCore::InvokeMgrDisp>::GetTimeOfLastChange invoked

2017-01-04T00:30:03.448+08:00| mks_vmrc| I120: HOSTINFO 11264064839998 @ 10000000Hz -> 0 @ 1000000000Hz

2017-01-04T00:30:03.448+08:00| mks_vmrc| I120: HOSTINFO ((x * 3355443200) >> 25) + -1126406483999800

2017-01-04T00:30:03.928+08:00| mks_vmrc| I120: vmClientCore::VMControl::Connect: hostname "192.168.2.23"

2017-01-04T00:30:03.928+08:00| mks_vmrc| I120: Setting proxy environment variable: VMWARE_HTTPSPROXY=

2017-01-04T00:30:03.928+08:00| mks_vmrc| I120: cui::vmrc::VMCnx::Connect: Connect to MOID "vm-96" on "192.168.2.23"

2017-01-04T00:30:03.928+08:00| mks_vmrc| I120: Resolving IP address for hostname 192.168.2.23

2017-01-04T00:30:03.928+08:00| mks_vmrc| I120: Resolved to 192.168.2.23

2017-01-04T00:30:23.948+08:00| mks_vmrc| I120: cui::vmrc::VMCnx::OnConnectAborted: Connect failed for MOID "vm-96" on "192.168.2.23"

2017-01-04T00:30:23.948+08:00| mks_vmrc| I120: cui::vmrc::VMCnxMgr::EmitConnectionStateSignal: Emitting "disconnected" signal (requested) for MOID "vm-96" on "192.168.2.23" - reason 'Connection timed out.'

bayupw · ‎01-03-2017

The vCloud Connector interface seems to use Internet Explorer

How about open VM console from Internet Explorer? Does it work or black screen?

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw

Lensar · ‎01-08-2017

Hi Bayu,

Thanks for you reply. When I open VM console from vCloud Director tenant page, it worked good.

I checked the VMRC log as bellow. The log shown VMRC connected vCloud Director console proxy address and verified SSL certificate, finally opened the VM console.

2017-01-09T14:52:37.871+08:00| vmrc| I120: Log for VMware Remote Console pid=5204 version=e.x.p build=build-3698060 option=Release

2017-01-09T14:52:37.871+08:00| vmrc| I120: The process is 32-bit.

2017-01-09T14:52:37.871+08:00| vmrc| I120: Host codepage=windows-936 encoding=GBK

2017-01-09T14:52:37.871+08:00| vmrc| I120: Host is Windows Server 2008 R2 Datacenter Edition, 64-bit Service Pack 1 (Build 7601)

2017-01-09T14:52:37.831+08:00| vmplayer| I120: VTHREAD initialize main thread 2 "vmplayer" host id 6132

2017-01-09T14:52:37.831+08:00| vmrc| I120: FILE: FileLockDynaLink: Further process validation tools are: available

2017-01-09T14:52:37.841+08:00| vmrc| I120: POLL Using the WSAPoll API Implementation for PollDefault

2017-01-09T14:52:37.841+08:00| vmrc| I120: LOCALE GBK -> NULL User=804 System=804

2017-01-09T14:52:37.871+08:00| vmrc| I120: Hostinfo_OpenProcessBits: OpenProcess access bits are 1000.

2017-01-09T14:52:37.881+08:00| vmrc| I120: OBJLIB-LIB: Objlib initialized.

2017-01-09T14:52:37.931+08:00| vmrc| I120: Debug VMX "" not found. Using standard VMX ""

2017-01-09T14:52:37.931+08:00| vmrc| I120: Stats VMX "" not found. Using standard VMX ""

2017-01-09T14:52:37.931+08:00| vmrc| I120: vmxFilePath=""

2017-01-09T14:52:37.931+08:00| vmrc| I120: vmxFilePathDebug=""

2017-01-09T14:52:37.931+08:00| vmrc| I120: vmxFilePathStats=""

2017-01-09T14:52:37.941+08:00| vmrc| I120: HostDeviceInfo: Failed to enumerate host parallel ports via the registry. Could not open device map parallel port registry key.

2017-01-09T14:52:37.961+08:00| vmrc| I120: Host OS: 'Windows Server 2008 R2 Datacenter Edition, 64-bit 6.1.7601, Service Pack 1', product type '3', suite mask '0x0190'.

2017-01-09T14:52:38.071+08:00| vmrc| I120: Foundry Init: setting up global state (1 poll threads, 0 worker threads).

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: vixLogLevel = 0

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: vixApiTraceLevel = 0

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: vixDebugPanicOnVixAssert = 0

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: vixLogRefcountOnFinalRelease = 0

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: asyncOpWarningThreshold = 1000000

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: enableSyncOpSelection = FALSE

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: enableExternalThreadInterface = TRUE

2017-01-09T14:52:38.071+08:00| vmrc| I120: Vix_InitializeGlobalState: enableVigor = FALSE

2017-01-09T14:52:38.071+08:00| vmrc| I120: LOCALE GBK -> NULL User=804 System=804

2017-01-09T14:52:38.071+08:00| vmrc| I120: VixHost_ConnectEx: version -1, hostType 3, hostName (null), hostPort 0, options 8707

2017-01-09T14:52:38.071+08:00| vthread-3| I120: VTHREAD start thread 3 "vthread-3" host id 5824

2017-01-09T14:52:38.071+08:00| vmrc| I120: REM-USB: Protocol version min:15 current:16. hostId:56 4d 9a bb be 5e 20 59-83 76 be d5 03 1e 6b 5e

2017-01-09T14:52:38.071+08:00| vmrc| I120: REM-USB: Initializing 'Generic' backend

2017-01-09T14:52:38.071+08:00| vmrc| I120: USBGW: Write arbitrator op:15 len:4

2017-01-09T14:52:38.071+08:00| vmrc| I120: USBGW: Write arbitrator op:0 len:4

2017-01-09T14:52:38.071+08:00| vmrc| I120: USBGW: Write arbitrator op:13 len:13

2017-01-09T14:52:38.071+08:00| vmrc| I120: REM-USB: Initializing 'Virtual CCID' backend

2017-01-09T14:52:38.081+08:00| vmrc| I120: USB-CCID: Could not establish context: SCARD_E_NO_SERVICE(0x8010001d).

2017-01-09T14:52:38.091+08:00| vmrc| I120: USB-CCID: Could not establish context: SCARD_E_NO_SERVICE(0x8010001d).

2017-01-09T14:52:38.091+08:00| vmrc| I120: HOSTINFO 16101611235555 @ 10000000Hz -> 0 @ 1000000000Hz

2017-01-09T14:52:38.091+08:00| vmrc| I120: HOSTINFO ((x * 3355443200) >> 25) + -1610161123555500

2017-01-09T14:52:38.091+08:00| usbCCIDEnumCards| I120: VTHREAD start thread 4 "usbCCIDEnumCards" host id 2116

2017-01-09T14:52:38.091+08:00| usbCCIDEnumCards| I120: USB-CCID: Card enum thread created.

2017-01-09T14:52:38.101+08:00| vmrc| I120: Enabling HTTPS tunnelling

2017-01-09T14:52:38.101+08:00| vmrc| I120: vmClientCore::RunEmbeddedVMRC: parent PID: 5644, instance ID: "vmrc-ax-t-{C145F73E-1953-4FB0-9246-C7A5B4DEBDED}", modes: 4, messageMode: 2, features: 3

2017-01-09T14:52:38.101+08:00| vmrc| I120: vmClientCore::RunEmbeddedVMRC: eventName = "VMRC_EVENT_vmrc-ax-t-{C145F73E-1953-4FB0-9246-C7A5B4DEBDED}", monikerName = "VMRC_MONIKER_vmrc-ax-t-{C145F73E-1953-4FB0-9246-C7A5B4DEBDED}", monikerEvent = 3F0

2017-01-09T14:52:38.101+08:00| vmrc| W110: IMonikerImpl::vmClientCore::MonikerImpl<class vmClientCore::InvokeMgrDisp>::GetTimeOfLastChange invoked

2017-01-09T14:52:38.111+08:00| usbCCIDEnumCards| I120: USB-CCID: Could not establish context: SCARD_E_NO_SERVICE(0x8010001d).

2017-01-09T14:52:41.911+08:00| vmrc| I120: Setting proxy environment variable: "VMWARE_HTTPSPROXY="

2017-01-09T14:52:41.911+08:00| vmrc| I120: cui::vmrc::VMCnx::Connect: Connect to MOID "vm-97" on "192.168.2.23"

2017-01-09T14:52:41.931+08:00| vmrc| I120: Resolving IP address for hostname 192.168.2.23

2017-01-09T14:52:41.931+08:00| vmrc| I120: Resolved to 192.168.2.23

2017-01-09T14:52:41.981+08:00| vthread-5| I120: VTHREAD initialize thread 5 "vthread-5" host id 7572

2017-01-09T14:52:41.981+08:00| vmrc| W110: SSL_IsVerifyEnabled: failed to open the product registry key. Falling back to default behavior: verification on. LastError = 0

2017-01-09T14:52:41.997+08:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: allowSSLErrors: true

2017-01-09T14:52:41.997+08:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: Found the following errors for 192.168.2.23's SSL certificate: {

2017-01-09T14:52:41.997+08:00| vmrc| I120: - 3

2017-01-09T14:52:41.997+08:00| vmrc| I120: - The host name used for the connection does not match the subject name on the host certificate.

2017-01-09T14:52:41.997+08:00| vmrc| I120: - The host's certificate is self-signed.

2017-01-09T14:52:41.997+08:00| vmrc| I120: }

2017-01-09T14:52:41.997+08:00| vmrc| I120: cui::CertificateCheck::CheckCertEmbedded - thumbprint for "192.168.2.23" OK

2017-01-09T14:52:43.225+08:00| vmrc| I120: cui::vmrc::VMCnx::OpenVM: Cnx connected for MOID "vm-97" on "192.168.2.23"

2017-01-09T14:52:43.225+08:00| vmrc| I120: VMMgr::OpenVM (cnx=192.168.2.23, moid=vm-97)

2017-01-09T14:52:43.865+08:00| vmrc| I120: cui::HostMgr::OpenHost - opening host with MOID "host-22"

2017-01-09T14:52:43.875+08:00| vmrc| I120: cui::HostMgr::OpenHost - opening host with MOID "host-22"

2017-01-09T14:52:43.875+08:00| vmrc| I120: cui::MsgMgrVIM::Manage: Suppressing VM questions

2017-01-09T14:52:43.875+08:00| vmrc| I120: VMStatus: Unknown guest os type: rhel5_64

2017-01-09T14:52:43.895+08:00| vmrc| I120: VMMgr: Finished opening VM at /vm/#_21F8330_vm-97/ from 192.168.2.23:vm-97

2017-01-09T14:52:43.895+08:00| vmrc| I120: cui::vmrc::VMCnx::OnOpenVMDone: VM opened for MOID "vm-97" on "192.168.2.23"

2017-01-09T14:52:43.895+08:00| vmrc| I120: cui::vmrc::VMCnxMgr::EmitConnectionStateSignal: Emitting "connected" signal (requested) for MOID "vm-97" on "192.168.2.23" - reason 'Connection successful.'

2017-01-09T14:52:43.895+08:00| vmrc| I120: cui::vmrc::VMRC::OnActiveVMCnxChanged: Active VMCnx: MOID "vm-97" on "192.168.2.23"

2017-01-09T14:52:43.905+08:00| vmrc| I120: SnapshotTree: Emitting refresh ([Gold] Web-01b (bed3125a-92f5-443b-8b62-9f626214ee0b)/Web-01b (bed3125a-92f5-443b-8b62-9f626214ee0b).vmx)