PIA INSTALL UBUNTU INSTALL
PIA INSTALL UBUNTU ZIP FILE

PIA INSTALL UBUNTU INSTALL

Install and configure NetworkManager along with the NetworkManager applet and OpenVPN plugin. In other words, only OpenVPN can be used when using the NetworkManager approach. It is worth noting that even when WireGuard can be used on the Linux binary and on the app, PIA has yet to provide WireGuard files for configuration.

PIA INSTALL UBUNTU ZIP FILE

Extract the ZIP file to a place in your user home directory or elsewhere that is memorable for future access. NetworkManager applet approach Installationĭownload OpenVPN configuration files from PIA. Ensure you are using PIA's DNS servers, listed on their website.Disable IPv6 since it is not supported by PIA.The same goes for all the other services listed above, e.g. You can access the individual services for setup by hitting the ports that are commented at the beginning of the docker-compose.yml file, specifically this: - 8112:8112 # delugeįor example, if your hostname is, then you'd go to the following URL to access Jackett. They even make a fancy plugin for syncing the two.

I'm a fan of using Jellyfin as the server, and streaming the media using Infuse on Apple TV. This should hopefully give you a starting point for your HTPC setup.

For example: config]$ config]$ lsĭeluge hydra2 jackett nzbget radarr htpc]$ htpc]$ ls EXTRA_SUBNETS=10.0.0.0/8,192.168.0.0/16,172.16.0.0/12Īssuming all goes well, you'll see a bunch of directories created based on the ENV variables that we'd set. 8000:8000/tcp # Built-in HTTP control server Please note that you'll need to customize the settings for the Glueton container: version: '3' Vi /opt/dockerfiles/htpc/docker-compose.ymlĬopy and paste the following into the file above. Sonarr depends on Jackett which depends on Glueton.Īnd now for the docker-compose.yml file to bring it all together. The containers have dependencies so they start in the right order, e.g.The ports are listed in the docker-compose comments. It also acts as the front door for you to access the containers.

they need to route their connections through the VPN. The Glueton containers acts as a VPN gateway for all the other containers, i.e.You'll see where the variables above are automatically reused throughout the file. Next we'll create the docker-compose.yml file. # The directory where data and configuration will be stored. # The UID and GID that I'd mentioned above. Now add the following to the file created above: # Creating the file is simple enough: # Create the file env file that allows us to reuse values throughout the docker-compose.yml file that we'll create. Sudo chown -R 1000:1000 /storage00/media/htpc Creating the Docker Environment Sudo chown -R 1000:1000 /opt/dockerfiles/htpc # The directory where all of my media is stored # The directory that holds configurations The setup looks like this: # The directory that holds my docker-compose files More of that in a minute when we get to the LinuxServer.io containers and how that is leveraged. These are run under the uid:gid of 1000:1000 which is typically the first user that you've added to your system. There are a few variables you'll need to change based on your setup, but it should be fairly straight-forward. I've got a homebrew NAS/HTPC setup using Arch Linux and ZFS. NZBHydra2 for generic newsgroup searching.Docker Containersįor reference, these are the containers that are used: I'm running this on Arch Linux in a Proxmox container, but it should be the same across most distros. This assumes you already have docker up and running. This guide does not walk through configuring the individual components. All of the media-centric docker containers come from the outstanding work of the LinuxServer.io team. Please note the link above includes a referral code.

I'm using Private Internet Access, but the VPN docker container is designed to work with a bunch of different providers. This guide will walk you through the process of setting up an HTPC docker stack that routes everything through a VPN.

Pia install ubuntu