Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I'm on localhost and trying to use the MediaDevices.getUserMedia method in Chrome. I receive the error as titled. I understand that in Chrome it is only possible to use this function with a secure origin and that localhost is considered a secure origin. Also, this works in Firefox.

This is how I'm using it as shown on the Google Developers website https://developers.google.com/web/updates/2015/10/media-devices?hl=en :

var constraints = window.constraints = {
            audio: false,
            video: true
navigator.mediaDevices.getUserMedia(constraints).then(function(stream) {
            callFactory.broadcastAssembly(stream);
                @Tom Serving over localhost is specifically allowed: chromium.org/Home/chromium-security/…
– Nateowami
                Sep 22, 2016 at 10:16
On some latest browsers navigator.getUserMedia does not perform well. So, try using navigator.mediaDevices.getUserMedia. Or, better you check if navigator.mediaDevices.getUserMedia is available for the browser use navigator.mediaDevices.getUserMedia or else use navigator.getUserMedia.    
navigator.getWebcam = (navigator.getUserMedia || navigator.webKitGetUserMedia || navigator.moxGetUserMedia || navigator.mozGetUserMedia || navigator.msGetUserMedia);
if (navigator.mediaDevices.getUserMedia) {
    navigator.mediaDevices.getUserMedia({  audio: true, video: true })
    .then(function (stream) {
                  //Display the video stream in the video object
     .catch(function (e) { logError(e.name + ": " + e.message); });
else {
navigator.getWebcam({ audio: true, video: true }, 
     function (stream) {
             //Display the video stream in the video object
     function () { logError("Web cam is not accessible."); });
Hope this will solve your problem.
                Worked for me as well. Is navigator.mediaDevices.getUserMedia defined in Chrome but not Chromium? MDN warns against using the deprecated  navigator.getUserMedia, warning that "it may break at any time." I'm trying not to use it, but navigator.mediaDevices.getUserMedia isn't available in Chromium without changing that flag. EDIT: Contrary to what I read, it didn't come out until Chrome 53 (I'm using Chromium 52).
– Nateowami
                Sep 22, 2016 at 10:40
                I found the answer in the footnotes on MDN: From version 47 to 52, the promise-based interface was only available through the adapter.js polyfill, or using the flag chrome://flags/#enable-experimental-web-platform-features. Starting with version 53, the promise-based interface is on by default, though that interface is still not available through navigator.
– Nateowami
                Sep 22, 2016 at 11:11
                I'm using Version 71.0.3578.98 (Official Build) (64-bit), and #enable-experimental-web-platform-features has not helped me with using Twilio: github.com/TwilioDevEd/client-quickstart-js/blob/….
– Ryan
                Feb 8, 2019 at 16:00
                Darn. I'm back again and didn't read my comment above and tried again in Brave (Brave is up to date Version 1.22.71 Chromium: 89.0.4389.114 (Official Build) (64-bit)) and it still didn't work.
– Ryan
                Apr 9, 2021 at 15:16
I too had the same  problem in my chrome browser.
first check your phone is supported by testing it in https://test.webrtc.org/
if your phone passes all the cases, then check step 2
step 2:
If your hosting a webpage or running a third party webpage,see whether camera permissions are enabled on your phone.
Also the main issue is WEBRTC is not supported in HTTP site and it is supported only in HTTPS site
This is the https site which allows web
 This is the http site which gives a error
I got stuck in the same issue. One solution is to follow and download the extension Web Server for Chrome shared in the comment above by @ellerynz, or
if you have python installed you could also do
python -m SimpleHTTPServer [port]
After you hit enter, you should see the following message:
Serving HTTP on 0.0.0.0 port 8000 ...
Open the browser and put 
http://127.0.0.1:[port]
                Excellent - ran exactly into this using SimpleHTTPServer; changing IP from 0.0.0.0 to 127.0.0.1 solved it
– 0__
                Jan 1, 2021 at 16:08
Have you tried to include adapter.js polyfill ? Check this page : 
https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia#Browser_compatibility
It looks like this or enabling chrome://flags/#enable-experimental-web-platform-features as per @Simon Malone's note, is needed for Chrome.
                I was hoping to use MediaDevices.getUserMedia because Navigator.getUserMedia is listed as deprecated on Mozilla. I'm still confused why the former does not work for me.
– kybak
                May 19, 2016 at 17:28
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.