These aren’t specific to the Pi but just things I encountered. Sudo apt-get install -t jessie plexmediaserver -y Sudo apt-get install apt-transport-https -y -force-yesĮcho "deb jessie main" | sudo tee /etc/apt//pms.list On the Pi I installed and enabled the rpcbind service: On my Synology NAS I enabled NFS as a service and then enabled NFS sharing for my media library. That was all preliminaries for the interesting part-making my existing media libraries available to the Pi. You can disable password authentication by setting PasswordAuthentication to no in /etc/ssh/sshd_config and restarting ssh. SSH access is disabled by default I enabled it and setup key-based authentication as an extra security measure.
This causes problems with mouting an NFS share. This is a little misleading the interface still gets an IP address via DHCP when set to manual, but it happens later in the boot process. As an additional step, I changed the configuration in /etc/network/interfaces from iface eth0 inet manual to iface eth0 inet dhcp. You’ll need to know the hardware address of the interface you’re using (wired or wireless). The procedure for doing so will vary depending on your home networking environment. I created a reservation on my router for the Pi’s hardware address so that the IP would be consistent. I changed it to Generic 105-key PC and selected a US keyboard layout. Raspberry Pi’s come with the keyboard set to the UK, which works for most things but can trip you up. I used Etcher on OSX for this and didn’t encounter problems. I’m comfortable in Debian so I started with a stock Raspbian image on a 32 GB SD card. I decided to get into the Raspberry Pi game and build a Plex server on it, while keeping my media on the NAS.
It’s worked well enough, but my DS 216 struggles at times to keep up with the movie (I’m not transcoding that would never work). I’ve been running Plex on a Synology NAS for the last year, with a Google Chromecast handling display.
0 kommentar(er)
