Start a new topic

WebPlugin with full HTML5 support like Chrome

I can`t use Royal TSX to manage vCenter and ESX today via html5 interface. Safari webplugin is not supported by VMware because lack of full html5 compatibility. For example, tasks are not displayed, blue screen instead of login prompt in esxi.



1 person likes this idea

But still, manage VMware vSphere is not possible because missing "task screen in the down part of the screen". HTML5 console is not working and so on... (look at HPE iLO) In my opinion a lot fo admins work on VMware vSphere vCenter Server and HPE servers and they have to use google chrome instead of your product.

looks like this is related to my issue. I'm getting unsupported browser from https://anypoint.mulesoft.com/, and even with user agent is faked, the session is not saved at all.

Hi Reynold,


I cannot reproduce the unsupported browser issue but obviously I don't have an account and can't check what happens after login.

Which user agent string did you use?


Also, I'm not sure what you mean by "the session is not saved at all", can you please elaborate?


thx,

felix

Hi Felix, I have made a screen recording -- uploaded to youtube for your viewing -- https://youtu.be/a8r-a0udJ0A -- pardon with the quality, it was just upload so the higher quality may not be completed 


yethttps://youtu.be/a8r-a0udJ0A.

Hi Felix here's the reproduction of the unsupported browser in action. https://www.youtube.com/watch?v=a8r-a0udJ0A&feature=youtu.be

Hi Reynold, so in the video I can't see that you provided a custom user agent string. Please try to copy the user agent string from Safari and check again. Thx, Felix

Hi Felix, here's the video showing wiht custom user agent, logged-in, closed the browser tab, but instead requiring login again -- https://youtu.be/naBmU0o87zo

Hi Reynold,


can you please try disabling "Prevent cross-site tracking"?


thx,

felix

Disappointing to still see no Chrome support 2 years after the first post in this thread.


I can't use Royal TS on OS X to manage Proxmox because the console (which uses noVNC) doesn't work with the web browser Royal TS are using in the OS X version.


Please either implement Chrome or Safari support on OS X.

Hi Ben,


Royal TSX' WebKit plugin is essentially Safari. It uses the same engine as your locally installed Safari. The difference is basically the shell around it and that we're not using the same user agent string as Safari.

That being said, I just installed NoVNC on a CentOS 7 machine and was able to successfully integrate it into Royal TSX without any changes to the default configuration of a web page connection.

What exactly happens when you try to use NoVNC? Do you see any error messages? In any case, please open a separate support ticket as we're better able to help you than posting on a public forum.


Hi Felix, I've been using Royal TSX for some time and followed all your tips and steps trying to make the HTML5 console to work for Proxmox VE without success. 

Did you tried to reproduce the issue with Proxmox VE during your tests? I saw other comments around the same issue with Proxmox but I don't find any specific solutions.

Any help would be much appreciated.

Thanks,
Joao

Hi Wojciech,


additional testing showed that the same procedure helps with the vCenter console.

We've just updated our WebKit troubleshooting KB article with all the steps necessary to fix this issue.

Please read the "Issues with the modern WebKit engine" section of the KB article and let us know if the workaround works for you too.


thx,

felix

We just updated the KB article again with some additional tips for troubleshooting.


cheers,

felix

Hi Wojciech,


I just checked my iLO installation in my test lab and was also able to get the HTML5 console to work.

In my case the problem was SSL validation related.


Please try this:

  • Close the connection if it's open
  • Make sure you have "Advanced - Ignore invalid certificates" disabled in the properties of your web connection
  • Open the connection
  • If you're using a self-signed SSL certificate, you should get a OS-standard certificate prompt
  • Enable "Always trust HOST NAME" and click "Continue"
  • It's very important to select "Always trust" because the HTML5 console uses web sockets which require the certificate chain to be trusted and there's no separate prompt if you only select "Continue" without always trusting the certificate
  • Next, you'll be prompted for your Mac user's password
  • If the connection fails right after entering your password, just open it again and you should be able to use the web console from now on

Let me know if that helps!

cheers,
felix

Hi Joao,


no, we did no tests with Proxmox.


Could you please try the suggestion to troubleshoot the issue using the Safari Developer console mentioned in this KB article.

Once you gather the console logs, please open a ticket to troubleshoot the issue with us.


cheers,

Felix

Login or Signup to post a comment