Can't connect to VM's error 1006

Hopefully this is something simple...

Our Nutanix system was built a few months ago as a POC and once it was built out and vm's created it has sat unattended but has had 400+ healthy check status reports, no errors, no failures etc etc

Today I log in to start actually using the system and we cannot connect to any of the vm's(13) via console as we get the following error:

"There was an error connecting to the VM. This could be due to an invalid or untrusted certificate chain or the VM being powered off. Please use the latest version of Chrome, Firefox or Internet Explorer if the problem persists."

I am running the latest version of Chrome and also tried IE 11 but we get the same error. I also powered down a few vm's and brought them back up healthy but still no luck.


19 replies

Userlevel 7
Badge +35

Let me see if I can get some additional eyes on this post and help 🙂
Same issue. Is there an update with a resolution?
Userlevel 3
Badge +17
Hey guys,
Could you please provide some details on your Nutanix system?
AHV version, AOS version?
AOS 5.6.1 and AHV 20170830.124

It is important to note this user experience is not reproducible by all. It is also important to note that the latest version of Chrome and IE.
Userlevel 3
Badge +17
You may try upgrading your AHV version to the latest one is AHV-20170830.157 (can download it from Nutanix portal > Hypervisor Details section)

The newest version officially supports for the latest web browsers version listed below:
Mozilla FF 38 or later
IE 11
(and maybe also fix for Chrome browsers?!)
Updating to the latest version of Hypervisor does not solve this issue.

It is important to note that I was able to identify the difference in steps allowing some users to launch console while others (including myself are not). Launch console works while accessing prism via IP address, but not using DNS.
Hi @cbowlby , @BNHCBob , could you please let me know if you are using Prism Central? If yes, the version of Prism Central please.
@Seema, Prism Central 5.6
@cbowlby As of Prism Central 5.6, Prism Central can manage clusters running more recent versions of the AOS 5.6 family (for example, Prism Central 5.6 can manage Prism Element clusters running up to AOS The PC version 5.6 is compatible with clusters :
  • 5.6 through 5.6.0.x
  • 5.5 through 5.5.0.x
  • 5.1 through 5.1.5.x
  • 5.0 through 5.0.4.x
Since you are using AOS 5.6.1, PC 5.6 cannot manage this cluster. To resolve the issue, please upgrade PC to a later version and try accessing the VM console.
@cbowlby One more question, is launching the VM console failing from both PC and PE?
@Seema, apologies, but I don't see the relevance of your comments on Prism Central as VMs are only able to be launched via Console using Prism Element which the reported issue. I will submit a ticket for support to review as this appears to be a bug or configuration issue when assigning DNS to Prism Element - as this issue is able to be replicated when using Prism Central via IP/Port.
Userlevel 2
Badge +3
We are also getting this error on a newly created VM (v5.5.2 and v5.5.7).

Interestingly, we get this error when we launch the Console from PRISM Elements but when we launch the Console from PRISM Central it works?

(PC->click Explore, click on VM Name (VM summary window appears), click on Console, Voila!)
Userlevel 3
Badge +17
Should better to check the time on your PC whether it is matching with CVM and AHV host or not
Userlevel 2
Badge +3
The time is the same but the PC is PST and the CVM is EST...
I have the same error when try to connect to any of the vm's of my cluster via console when i use Chrome or Internet Explorer as browser, with Edge the connection to the console is OK but i have other problems with Edge.
Some one have a solution to this problem?
Userlevel 2
Badge +3
Do you use Certificates to access the Cluster?

In one of our Environments we do not. As a result we get the 1006 when trying to access the VMs from PRISM Elements. However if we use PRISM Central and Explore the VM from there the Console works.

I will check to see if it seems to be Chrome or Firefox in that Environment...
Not, we don't have configured certificates in the access. In a future we configure this certificates, but actually we have a POC environment.
I have the same problem with Prism Central and with Prism Element.
We use a proxy pac file in the configuration of the browser, with this file we can't Access to the console, but if we disable the proxy configuration the console launch correctly.
I check the configuration of this file and the IPs of the Prism Central and with Prism Element are configured as Direct, don't use proxy.


Was this ever resolved? I’ve been trying to run CE nested on vSphere Hypervisor 6.7 and keep running into this problem. Version of CE is the latest - 2019.11.22.

Badge +6

I have run into the same error while using the AOSonGCP Hands On Lab, just now. (1006)