See the mixed-content problem described in this rovercode-web issue.

Perhaps instead of using a Chrome extension, the rover could generate a self-signed certificate with its local ip address in the SAN field. This could make the browser happy, even without installing the certificate.

Let's do an experiment to see if that would work. We could manually create the cert on the rover, then see if rovercode-web app complains about talking to it over HTTPS.