WebRTC could not connect to your microphone

[Gabriel Sere]

Hello,

Same error here:

"WebRTC audio failure. Detected the following WebRTC issue:
Could not get your microphone for a WebRTC call.
Do you want to try Flash instead?"

I have two BBB installations configured on servers with Ubuntu 16.04.

One server with BBB 1.1.0 and a Comodo certificate. On this server
webrtc works fine.

The other server was configured first with BBB 1.1.0 and Let's encrypt
certificate. Webrtc give the error above.
After upgraded it to version 2.0 the error remains.

No nat, both servers with public IP.
Open tcp/ip ports: 80,443, 1935, 2812, 7443 and 9123
Open udp ports: all

I also tried demo.bigbluebutton.org and I got the same error. I see this
server also have a Let's encrypt certificate.

Perhaps nginx doesn't like this certificate?

I use two browsers, Firfox ESR 52.3.0 (64-bits) and Google Chrome
Versión 60.0.3112.113 (Build oficial) (64 bits) on a machine with Debian
Jessie.

Gabriel.








--
---
--- Lic. Gabriel Seré
--- gab...@sere.uy
---

[Chad Pilkey]

If you are getting an error about not being able to access your microphone on our demo server then the issue is on your local end not on the server or the certificate (should only happen in Chrome). If your computer is rejecting certificates from Let's Encrypt then you should be seeing warnings near the top of your browser about the certificate not being recognized. I've only seen this once before and it was because a school had locked down the allowed certificates and were missing some new ones. The most likely option is that your OS doesn't have the intermediate certificate for Let's Encrypt. There's a page that Let's Encrypt created that has links for testing different certificate states and it has their intermediate certificates https://letsencrypt.org/certificates/.

[Gabriel Sere]

Still have same error after upgrade both browsers to

Firefox ESR 52.4.0 (64-bits)
Chrome Versión 62.0.3202.75 (Build oficial) (64 bits)



El 06/11/17 a las 13:28, Gabriel Sere escribió:

[Chad Pilkey]

I'm pretty sure trusted certificates are OS-wide not local to the browser so updating your browser wouldn't change anything. I know how to fix it on Windows, but I don't use Debian so I can't really help you actually add the Let's Encrypt certificate to the list of trusted certificates.

The demo server is configured correctly and is working so the likely source is on your computer. Did you go to the official Let's Encrypt page and try any of their test pages?

[Gabriel]

There was no warnings on the browser but you are right, the problem was on the OS, probably in the lack of the intermediate certificate.
But it's quite a common problem: 3 of 5 machines here (windows and linux) have the same issue.
Since I prefer that users have no problem with this I have chosen to change the certificate and after doing that the problem is gone and everything works fine.

Thank you.
Gabriel.