- #PLEX MEDIA SERVER UBUNTU 16.04 REPOSITORY INSTALL#
- #PLEX MEDIA SERVER UBUNTU 16.04 REPOSITORY UPDATE#
- #PLEX MEDIA SERVER UBUNTU 16.04 REPOSITORY SOFTWARE#
#PLEX MEDIA SERVER UBUNTU 16.04 REPOSITORY UPDATE#
Then you can open the browser of the machine just as if you are sitting there and can run the download and update (I personally almost solely use VNC and even my smartphone to admin my server 95% of the time and mostly doing stuff while at work so I can vouch for this sort of setup (though I do usually prefer a bridged OpenVPN server, but I also have an SSH server setup so I can tunnel in if VPN is unhappy for some crazy reason). Last word, if you use something like an Amazon S3 cloud instance or remote system if you say setup VNC (DO NOT PORT FORWARD VNC ITSELF) and a basic SSH server then you could connect to your computer via SSH tunnel and open VNC.
#PLEX MEDIA SERVER UBUNTU 16.04 REPOSITORY INSTALL#
Once you set it to check for updates you will see a link there stating Please Install Manually that when you click that it directly downloads the correct binary for the OS your system is running! so really scripts and what not can help, but I have no problems with clicking Settings>Server>Download Link (I also like to manually issue sudo service plexmediaserver stop before installing updates just to ensure nothing is in use while being updated). To download direct from Plex in web interface Click Settings>Click Server and it already does an auto update check for you right on top of the server settings general page (click show advanced to change between checking Plex Pass or Public channels).
#PLEX MEDIA SERVER UBUNTU 16.04 REPOSITORY SOFTWARE#
So I always like to put out a word of caution on software repos and adding third party repos in particular.īesides Updates are super easy to download anyways. So back to my point that if the owner or contributor of a software repo can add, or edit the code hosted then IN THEORY they could introduce malware (be it a virus or spyware, etc.). So why do I mention this? I have not checked the repo listed here and I am not commenting on this particular repo just repos in general. If the maintainer of the repo (or a contributor with the permissions to add code to it) could add, edit, or otherwise change that code in anyway they choose. This sounds easy and great on the face of it, but at the same time you are opening up a security hole. By adding a repo to your system you are essentially telling the system I trust this repo, the code (read applications, files, whatever it is holding) so check it and apply updates. Nice of you to set something like that up, but word fo caution in general folks… With Software repos (any is not limited to Plex and/or Ubuntu) you want to be very careful. I don’t know well how the deb works, but i think if i don’t modify packet, the inside signature can validate it. Sudo apt-get update sudo apt-get install plexmediaserver Sudo add-apt-repository 'deb trusty main' Also, it contains only the public release of plex, not the plex pass. And it only have the plex media server packet (no risk of overlapping update). Actualy, all my computer use trusty, so the repository have only the trusty entry (to not break other system if the package are not functional), but if you are sure that the plex package works for you, you can add it safely. Then it was automaticly add without any modification (so, not usable on debian). I use plexupdate script ( /mrworf/plexupdate) with cron to verify and fetch new version. So, to automatise update, i make a little repository on my dedicated server. I use plexmediaserver on 3 computer with ubuntu.