You can also take a look at the logs to make sure everything is humming along – mine were located in /var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Logs/Plex\ Media\ Server.log systemctl restart plexmediaserver Save your settings and restart Plex Media Server. Lastly make sure you enter the full URL for your home server under Custom Server Access URLs. While you’re there set secure connections to required, at this stage in Plex development all clients should work fine with it. NOTE: Be sure that the permissions are correct on the certificates, they should be owned by the plex user. You will also want to put the Common Name you entered during SSL certificate creation here in the custom certificate domain area. Login to Plex Media Server and go to Settings -> Server -> Network and place the above info like below – the path to the certificate.p12 and the really long hash (passphrase) that was generated earlier. Let’s move on to installing this in Plex. You should see something like this (save it). The hash is a decryption passphrase for the PKCS #12 file. It will also generate a certificate.p12 file. If all is well you’ll see a long hash as the return, save this as you’ll need this later. The syntax is plex.cert plex.key ProcessedMachineIdentifier python pem2plex.py plex.crt plex.key 547bzw4423296e0ba072364f11c84kj3fae632ld5 Now you’ll snag the following Python tool, it will create your pkcs12 certificate as well as generate a long hash that you’ll need for Plex as the “private key” (this is confusing as you’d normally think it refers to your actual private key – not so. Let’s assume mine is ProcessedMachineIdentifier=” 547bzw4423296e0ba072364f11c84kj3fae632ld5” for this example. Obtain the long 30-35 character alphanumeric string after ProcessedMachineIdentifier= in the following file: cat /var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Preferences.xml You first need your ProcessedMachineIdentifier number from your Plex installation, thanks to the Reddit post that cleared this up. Plex requires a pkcs12 certificate to be generated, but we’re going to use a python script for that. Openssl rsa -in -out plex.keyĬreate the Certificate openssl x509 -req -days 5475 -in plex.csr -signkey plex.key -out plex.crt Now we’re going to strip the passphrase out of the keyfile, it will prompt you one more time for the passphrase. openssl req -new -key plex.key -out plex.csr There are plenty of free services that provide dynamic DNS for this if you don’t have the ability to add an A record somewhere. The only important thing that must match is the Common Name which should be valid FQDN / hostname of your home machine where any external clients will connect. You can enter any value you want here, don’t overthink it. Next you’ll create the certificate signing request and be prompted with some questions. Verifying - Enter pass phrase for plex.key: Generating RSA private key, 1024 bit long modulus This will prompt you for a passphrase, enter something here and remember it. We’re going to do everything else as the plex user inside their home directory. We’re going to be using the openssl commands and a Python script to create our certificates. This is aimed for a CentOS7/RHEL7 installation, substitute appropriately for other Linux distributions. We will focus on creating, installing and using your own self-signed SSL certificates to encrypt connection streams to the outside world. I am going to assume you have Plex Media Server already setup, if not there are plenty of other guides to do this. Here’s how to use your own self-signed SSL certificates to encrypt connection streams. Plex is a fork of the Open Source Kodi (previously XBMC) project from 2008, the Plex Media Server has evolved into what amounts to a free, personal Netflix Spotify that lets you stream home content to devices or browsers with an optional subscription model for added features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |