Skip to main content

Plex and LetsEncrypt

Work in Progress:

Plex and LetsEncrypt

So... I'm not entirely sure where to begin with all this. And this write-up is a mess (right now). I was not certain this was going to work and therefore I was not keeping absolute notes.
Apache webserver allowing 80/443 through my firewall.
- www.linuxrevolution.com
- plex.linuxrevolution.com
Plex Media Server currently running on OSX Mac Mini at port 32400 (standard port)
I own a domain "linuxrevolution.com" and I also have a Plex Media Server running on any particular system (Mac Mini/OSX, Nvidia Shield TV, Linux).
On my webserver, I am using CertBot
- create a webroot (vhost) on your Apache Server.

wget https://dl.eff.org/certbot-auto
chmod a+x certbot-auto
./certbot-auto 


./certbot-auto certonly -d plex.linuxrevolution.com --webroot

openssl pkcs12 -export -out ~/plex_linuxrevolution_com.pfx \
  -inkey /etc/letsencrypt/archive/plex.linuxrevolution.com/privkey1.pem \
  -in /etc/letsencrypt/archive/plex.linuxrevolution.com/cert1.pem \
  -certfile /etc/letsencrypt/archive/plex.linuxrevolution.com/chain1.pem

- Enter a passphrase
Getting the certs downloaded locally.
You then have to create the pkcs12 file and you will be asked for a passphrase which you will need to enter in your Plex configuration.
Custom certificate location /Users/jradtke/Music/plex_linuxrevolution_com.pfx
Custom certificate encryption key <this is the key you used when you created the pkcs12 file>
Custom certificate domain plex.linuxrevolution.com

Review Logs
cp /Users/jradtke/Library/Logs/Plex Media Server
grep CERT Plex\ Media\ Server.log

I'd like to thank:
Labels:

Comments

  1. CliffMarch 20, 2018 at 6:05 AM

    I recently wrote a script to automate the install and update of letsencrypt certificates on a plex server that is running on Ubuntu.

    https://oisec.net/blog/plex-letsencrypt

    ReplyDelete

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more