It’s a pretty laughable security experience if the browser warns you that your server isn’t trusted! We knew from the start that we needed real, official certificates, and there are a few problems with that. Now anyone can make a (self-signed) certificate, but it can be tedious to install, and for a browser to trust it and give it that elusive green lock, it has to have been signed by a trusted authority. Let’s look at some of the complexities: For starters, secure communication requires something called a certificate, which securely identifies a website. Our blog post announcing the release of secure communications spoke about some of the details: You can safely and securely connect to your media no matter where you are.Īfter all, everyone loves to see beautiful secure locks, right? There’s no need to set up VPNs and no need to create and install your own certs. Plex has teamed up with Let’s Encrypt to provide our users with high-quality secure certificates for your media servers, at no cost to you. When browsing the internet or making other connections these days, everyone wants to make sure that the communication taking place is secure and encrypted.

What’s the Deal With Secure Connections? Why Is It Important?

Plex aws