You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm currently doing a college project which requires video and audio transmission from person to person within a browser. rtc.io seems like a great way to achieve this. I am however running into a problem. I am serving the HTML page with the rtc.io content over HTTPS, since Chrome requires HTTPS to be used when handling the webcam. While this isn't an issue perse, the problem arises when I try to connect a client to a self-hosted switchboard. Chrome will only allow me connect a client to a switchboard if the switchboard is also served over HTTPS, which it isn't as far as I can tell. What would be the correct way to connect a client to the switchboard over HTTPS?
The text was updated successfully, but these errors were encountered:
Hi, thanks a lot for your reply! I'll try to implement nginx as soon as I get the chance. I'm curious though, why doesn't rtc.io supply any solution for this at the moment, since the switchboard can only be used in practice when combined with HTTPS?
Hi, I'm currently doing a college project which requires video and audio transmission from person to person within a browser. rtc.io seems like a great way to achieve this. I am however running into a problem. I am serving the HTML page with the rtc.io content over HTTPS, since Chrome requires HTTPS to be used when handling the webcam. While this isn't an issue perse, the problem arises when I try to connect a client to a self-hosted switchboard. Chrome will only allow me connect a client to a switchboard if the switchboard is also served over HTTPS, which it isn't as far as I can tell. What would be the correct way to connect a client to the switchboard over HTTPS?
The text was updated successfully, but these errors were encountered: