upon running npm run dev the app loads the error view only
alfydavy opened this issue · 4 comments
alfydavy commented
I have npm installed , have installed all the project dependecies, yet the app does not seem to load the main view; this on all the browsers on my mac (chrome/opera/safari)
I built a webRTC app to check if my accesibility to video etc is fine ; that piece works spendidly.
Could you help me on this ; am I missing something here?
dmotz commented
Are you seeing any errors in the console? Note that camera access won't work in Safari.
alfydavy commented
Hi Dan,
Thank you for your response.
I ran the application through the chrome console and was able to identify the problem.
The problem is that ‘getusermedia’ function call needs to be called through a https as opposed to http , while running a local instance of a server
error Msg:
getUserMedia() no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
I was reviewing the docs around it , so need to get a certificate /rather build one and run it against it.
Any ideas you could share for a quick hack on this .
let me know.
Regards
Alfy
… On 29-Dec-2016, at 06:17, Dan Motzenbecker ***@***.***> wrote:
Are you seeing any errors in the console? Note that camera access won't work in Safari.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABiGx02Kqt_1hnpzNHALOktglsBtCJSuks5rMwMjgaJpZM4LWfLK>.
amitness commented
@alfydavy I also got the same error when using 127.0.0.1:9966 or 0.0.0.0:9966. But it worked for localhost:9966. Workaround for now.
alfydavy commented
Amit/Dan,
still plagued with the same problem , I’m building an equivalent app using webrtc with ionic and angular 2 ; will pot the code once I integrate the api’s.
The camera works and best part mobile ready too.
Regards
Alfy
… On 18-Jan-2017, at 11:45, Amit Chaudhary ***@***.***> wrote:
@alfydavy <https://github.com/alfydavy> I also got the same error when using 127.0.0.1:9966 or 0.0.0.0:9966. But it worked for localhost:9966. Workaround for now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABiGx0QOws_yFklG44I01MuQkpV5gjQGks5rTa4MgaJpZM4LWfLK>.