Hi,

Please try to use Firefox ESR lastest release to connect a ESXi host.

Tks

Looks like it has been fixed in the latest patch. I have yet to try it out myself though.

VMware ESXi 6.5, Patch ESXi650-201704402-BG: Updates esx-ui (2149715) | VMware KB

Cause: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest

Version: 1.8.0

Build: 4516221

ESXi: 6.5.0

Browser: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Exception stack:

Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest

  at https://esxi/ui/scripts/main.js:263:20611

  at l (https://esxi/ui/scripts/main.js:265:12567)

  at k.$apply (https://esxi/ui/scripts/main.js:265:16690)

  at HTMLInputElement.<anonymous> (https://esxi/ui/scripts/main.js:267:828)

  at HTMLInputElement.dispatch (https://esxi/ui/scripts/main.js:262:14464)

  at HTMLInputElement.r.handle (https://esxi/ui/scripts/main.js:262:11251)

  at prop (https://esxi/ui/scripts/main.js:263:3018)

  at n.access (https://esxi/ui/scripts/main.js:262:6702)

  at n.fn.init.prop (https://esxi/ui/scripts/main.js:263:2642)

  at V.$set (https://esxi/ui/scripts/main.js:264:21408)

---------------

As mentioned, with chrome- if I press the button with mouse instead of pressing enter, I do not get this error! VERY STRANGE! Hope this is fixed in next release. Will update now.

Encountered same issue and was able to find a workaround.

When opening a tab to connect to ESXi server 6.5 it has crashed with the same error after successful login.

Keeping the tab which crashed open and opening a second tab to same address resulted in getting inside without the need for login.

Best regards,

Vlad Tonne.

Just connected to version 6.5 of esxi and see the same error. I guess you did not fix that at all as you claim at 6.0 release.

For those who are still experiencing the issue (because I always hit Enter before I remember to click the Login button.. old habits!), I found that doing a full reload in Chrome (CTRL-SHIFT-R) clears the exception. It's a quick way to clear it and carry on with what you need to do.

I've also found that after hitting enter to login (instead of clicking login - which avoids the issue) that once presented with the mishandled exception message, one can simply strike the Escape key and begin working.

I can confirm that using either shift-command-r or the escape key in chrome on Mac OS lets will remove the error so you don't have to go back and re-login and use the mouse to click the login button. The escape button is much faster as you don't have to re-download anything or re-draw the page. How ironic that you can fix a bug that throws an error when you use a keyboard key by using a different keyboard key.

We had this issue on 6.0 and 6.5. Dont press enter after entering user/pass. Click 'Logon' and it wont happen.

Must be a bug.

It is a bug, but it's fixed in the latest 6.5 release (VMware-VMvisor-Installer-201704001-5310538.x86_64)

FYI... I built a new server with the latest 6.5 version (4887370) and the issue did not pop up until I replaced the default SSL certificate. I think the issue is related to custom certificates, but the vib noted as the solution does fix the issue.

This worked for me also. Don't use the "Enter" key after entering your password to log in. Select the "Log In" button.

ause: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest

Version: 1.8.0

Build: 4516221

ESXi: 6.5.0

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Exception stack:

Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest

    at https://192.168.0.55/ui/scripts/main.js:263:20611

    at l (https://192.168.0.55/ui/scripts/main.js:265:12567)

    at k.$apply (https://192.168.0.55/ui/scripts/main.js:265:16690)

    at HTMLInputElement.<anonymous> (https://192.168.0.55/ui/scripts/main.js:267:828)

    at HTMLInputElement.dispatch (https://192.168.0.55/ui/scripts/main.js:262:14464)

    at HTMLInputElement.r.handle (https://192.168.0.55/ui/scripts/main.js:262:11251)

    at prop (https://192.168.0.55/ui/scripts/main.js:263:3018)

    at n.access (https://192.168.0.55/ui/scripts/main.js:262:6702)

    at n.fn.init.prop (https://192.168.0.55/ui/scripts/main.js:263:2642)

    at V.$set (https://192.168.0.55/ui/scripts/main.js:264:21408)

just click login or press F5

Beres...gitu lho..

THAT...IS...INSANE...but worked!  Thanks for the tip, probably would have NEVER thought of that.  Obviously, there's some patching that needs to be done, but at least I don't have to switch browsers anymore

Yes, clicking the "login" button instead of hitting enter worked for me as well.

This is not production software guys. VMware SO needs to clean this shit up. After wasting so much time battling with the totally useless vCenter Installer (just google it. no seriously, just google) it's bugs like this that really promotes alternatives to vmware.

So long and thanks for all the fish. Yeah. Fish.

Happens with ESXi 6.5 also.

Freakin A!  This resolved it for me.  Thank you SeanGazaway!

I'm using VMware-VMvisor-Installer-201701001-4887370.x86_64.iso

Amazing - worked for me too! Thank you!

Sometimes i have the same problem at ESXi 6.5. These problems happen when i leave the session opened in a browser tab (Chrome) on Ubuntu 16.04

To resolve I simple clear browsing data. And the problem goes away.