MobiControl 126.96.36.19967 - Remote Control (non-html) fails
I believe this was first seen after an update to Google Chrome Version 58. What browser and version are you using?
Can you use another browser to access the MobiControl Console?
Confirmed. The users are able to access as expected with IE and Firefox. I'll direct them to use those for now instead of Chrome. Any idea what caused the issue or if there will be a resolution?
At the time it was brought o our attention "Google had recently released version 58 of the Google Chrome browser. This version has a change in how it deals with certificates as presented by the server which causes our remote control launcher to no longer be trusted by default. This manifests itself when attempting to remote control a device by causing the remote control plugin installer to repeatedly download, no matter how many times it’s run."
Here are two possible solutions to work around this issue.
- The first is to simply use another browser. In particular, both Internet Explorer and Firefox are known to still work with the current remote control solution.
- The second is to manually override the invalid certificate warning temporarily within Chrome which allows remote control to function as normal. To do this, open https://127.0.0.1:38103/ in the browser, click Advanced in the security warning message that pops up, and click “Proceed to 127.0.0.1 (unsafe).” This will bring a message saying that remote control has now been installed. You should now be able to go back to the web console and remote control devices. Please note that this solution is not permanent and will have to be repeated from time to time. Additionally, if the customer has a green “Secure” note in the address bar, this will change to a red “Not Secure” note when remote controlling devices. This is unavoidable for the time being, but is not an indication of a security breach on the web server.
Nonetheless we would be more than glad to address your circumstances directly by submitting a case with firstname.lastname@example.org for a permanent fix.
I have included the link to create a case below.
Hope this helps!
Thanks for the details on that issue. I confirmed that workaround 2 worked on a users machine.