WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / Automation / HTML5 console now defaults to HTTPS/WSS in vSphere 5.5 Update 2

HTML5 console now defaults to HTTPS/WSS in vSphere 5.5 Update 2

09.24.2014 by William Lam // 5 Comments

I just found out from one of my readers that with the latest release of vSphere 5.5 Update 2, the HTML5 Console in vCenter Server now goes over a secure connection (HTTPS) as well as using secure web socket connection (WSS) by default. In addition to this change, the HTML5 console port has also been changed from 7331 to 7343. I know customers have asking about this in the past and though this was not possible with previous releases, I am glad to see that VMware Engineering has now added this capablity, another reason to go to vSphere 5.5 Update 2!

This new change is also documented in the vSphere 5.5 Update release notes, which I some how must have missed:

Virtual machines with HTML 5 console in vSphere 5.5 open connections with http:// instead of https://
When the HTML 5 console is launched on a virtual machine, it uses connections like http:// and web sockets like ws:// instead of secure connections like https:// and wss://.

This release resolves the issue by launching the virtual machine console with secure connection over port 7343 instead of the connection over port 7331.

For those of you using my generateHTML5VMConsole script to generate a pre-authenticated HTML5 VM Console, I have updated the script to include a new variable called isvSphere55u2 which will default to "false" but you can set it in the command-line to "true" and this will automatically generate a URL using HTTPS instead of HTTP and use port 7343 instead of 7331. Other than these two minor changes, the URL format is exactly the same and will continue to work.

Here is a quick screenshot of the HTML5 VM Console URL in my lab running vSphere 5.5 Update 2:

vsphere-55u2-html5-console-https-webmks

More from my site

  • How to audit vSphere Standalone VMRC or HTML5 VMRC connections?
  • How to change the default HTML5 VM console port in vSphere 5.5?
  • How to generate a pre-authenticated HTML5 VM console link in vSphere 5.5 that works on all OSes!
  • How to restrict access to both the Standalone VMRC & HTML5 VM Console?
  • Standalone VMRC now available for Mac OS X

Categories // Automation Tags // HTML5, remote console, vmrc, vSphere 5.5, webmks

Comments

  1. *protectedMaik says

    02/04/2015 at 7:40 am

    Hi William
    Which entry could I set in the webclient.properties to change the secure html port from 7343 to another?

    Reply
    • William Lam says

      02/04/2015 at 1:53 pm

      Maik,

      Take a look at this blog post on changing the HTML5 port http://www.virtuallyghetto.com/2013/10/how-to-change-default-html5-vm-console.html

      Reply
  2. *protectedpsv141 says

    04/16/2015 at 6:48 am

    Hi William,
    is it possible to switch back to HTTP instead of HTTPS?

    Reply
    • William Lam says

      04/17/2015 at 5:14 pm

      not afaik.

      Reply
  3. *protectedSean says

    01/26/2016 at 9:41 am

    Have you heard of any attempt to generate the one time URL and then in order to restrict direct access to the ESX host use a reverse proxy to access the host from an external endpoint?

    Reply

Leave a Reply to psv141Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • VCF 9.0 Installer workaround for ESXi hosts with different vendor 06/19/2025
  • NVMe Tiering with AMD Ryzen CPU workaround for VCF 9.0 06/19/2025
  • vSAN ESA Disk & HCL Workaround for VCF 9.0 06/19/2025
  • Disable 10GbE NIC Pre-Check in the VCF 9.0 Installer 06/19/2025
  • Minimal resources for deploying VCF 9.0 in a Lab 06/18/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...