Chrome 47+ Requires HTTPS for Gruveo Embeds to Work

One of the changes introduced in Chrome 47 was a "secure origin" policy for accessing the user’s camera and microphone. In a nutshell, a web page can now access the user's camera and microphone only if the page itself is accessed via HTTPS. If the page is accessed via HTTP, media device access will be automatically denied.

Gruveo <iframe> embeds have always used HTTPS. Unfortunately, the “secure origin” policy means that if the host page is accessed via HTTP, the Gruveo embed will still fail to get access to the user’s camera and microphone and display the “Cannot access camera and/or microphone” error.

What this means is that for Gruveo embeds to continue to work on your site, you need to switch to HTTPS for the page(s) where the Gruveo embed is hosted. Fortunately, there are plenty of SSL certificate providers out there where you can get an SSL certificate for $10 or less. Or favorite is Comodo PositiveSSL which at the time of this writing cost only $4.99 per year at SSLs.com.

The “secure origin” change in Chrome 47 is part of a broader initiative on the part of the Chrome team to emphasize the non-secure nature of HTTP. While we are sorry for the inconveniences this may cause to our Gruveo embed users, we applaud Google for their efforts to make the Web a safer place – something all of us will benefit from.