7 comments on “Let’s Encrypt – how get to free SSL for WebRTC

  1. I have not tried with nginx, but have used it for Apache. I could automatically setup http to https redirect with –redirect option. Also I could enable HSTS simply by using –hsts option. Of course individual deployments have to evaluate there are no gotchas (like mixed content) when HSTS is enabled.

    I find https://www.ssllabs.com/ssltest/ useful to get “a deep analysis of the configuration of any SSL web server.”

  2. If you ask me, it was a silly decision from the Chrome team. Despite the costs, I’m still wondering what would be the SSL solution for LAN without Internet access or even in lack of a real domain name?

    • To let browser accept a local-signed certificate, you may need to add signer certificate to for each client. The exact steps depend on browser / OS.

    • Hi Mohsen, have figured out a solution for your use case (LAN without Internet access or even in lack of a real domain name)?

  3. Pingback: Free SSL for WebRTC | 0ddn1x: tricks with *nix

  4. It’s been 90 days. Let’s Encrypt is nice enough to send a bunch of reminders that your certificate was about to expire. It turns out the auto-renew cron-tab failed because of a conflict on port 80. Looks like I need to make some adjustments.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.