Plex: Difference between revisions

From NixOS Wiki
Klinger (talk | contribs)
m Category:Applications
TheToto (talk | contribs)
Reorganize Plex clients
 
(4 intermediate revisions by 3 users not shown)
Line 3: Line 3:
== Basic setup ==
== Basic setup ==


Plex is pre-packaged on NixOS already. All you need is to edit your <code>configuration.nix</code>. A simple configuration looks like
Plex is packaged in Nix. All you need is to edit your <code>configuration.nix</code>. A simple configuration looks like:


<syntaxhighlight lang="nix">
<syntaxhighlight lang="nix">
Line 16: Line 16:
Of course there's some more [https://search.nixos.org/options?query=plex options] that you can customize.
Of course there's some more [https://search.nixos.org/options?query=plex options] that you can customize.


If your Plex media server is behind a router, you'll need to forward tcp port <code>32400</code> to your Plex media server.
If your Plex media server is behind a router, you'll need to forward TCP port <code>32400</code> to your Plex media server.


Access Plex media server by browsing to <code>http://lan_ip:32400/web</code>
Access Plex media server by browsing to <code>http://lan_ip:32400/web</code>
Line 22: Line 22:
=== Allow Plex to read external drives ===
=== Allow Plex to read external drives ===


You might encounter permission issues when you try to access external drives if you haven't configured anything else with the server yet. If you haven't explicitly set up a mounting configuration for your drives and instead have your desktop environment (e.g. GNOME or KDE) automatically mount it when you try accessing it via their file explorers, Plex won't be able to access the drive. This is because the desktop environment mounts it to your user, while Plex uses by default the "plex" user.
You might encounter permission issues when you try to access external drives if you haven't configured anything else with the server yet. If you haven't explicitly set up a mounting configuration for your drives and instead have your desktop environment (e.g. GNOME or KDE) automatically mount it when you try accessing it via their file explorers, Plex won't be able to access the drive. This is because the desktop environment mounts it to your user, while Plex runs by default as the "plex" user.


The easiest way to allow Plex to see these external drives mounted is to change the Plex service's user . Here is an example:
The easiest way to allow Plex to see these external drives is to change the Plex service's user . Here is an example:
<syntaxhighlight lang="nix">
<syntaxhighlight lang="nix">
services.plex = {
services.plex = {
Line 38: Line 38:
</syntaxhighlight>
</syntaxhighlight>


The alternative to this is to explicitly mount the drives via [[Filesystems]], but takes more effort to set up and requires every new drive you want plex to see to be explicitly declared, but allows more control in what Plex is allowed to see.
The alternative to this is to explicitly mount the drives via [[Filesystems]]. This takes more effort to set up and requires every new drive you want plex to see to be explicitly declared, but allows more control in what Plex is allowed to see.


== Plex Media Player (PMP) ==
== Clients ==


Plex Media Player is the current release of Plex's media client. Plex has made PMP [https://www.plex.tv/blog/plex-media-player-now-ambidextrous-free-kodi-said/ available] to all users and it has also become compatible with Kodi.
=== Plex Media Player ===
[https://www.plex.tv/blog/plex-media-player-now-ambidextrous-free-kodi-said/ Plex Media Player] is Plex's media client, packaged in Nix as plex-media-player.  


'''Installation'''
=== Plex Desktop ===
Alternatively, a more newer and modern Plex client called Plex Desktop is packaged in Nix as plex-desktop.


<syntaxhighlight lang="console">
To be able to sign in in Plex Desktop, you may need to set <code>xdg.portal.xdgOpenUsePortal = true;</code> in your NixOS configuration. [https://github.com/NixOS/nixpkgs/issues/341968 See this issue].
$ nix-env -i plex-media-server
 
</syntaxhighlight>
=== Plexamp ===
Plex also provide Plexamp for music. It's packaged in Nix but (as of August 2024) only for x86_64.


== SSL Access via Nginx Reverse Proxy ==
== SSL access via Nginx reverse proxy ==


Because of several redirects within Plex media server it's not easy to make it accessible through SSL. Browser can complain, even if you have configured proper SSL certificates in your plex setup.
Because of several redirects within Plex media server it's not easy to make it accessible through SSL. The browser can complain, even if you have configured proper SSL certificates in your Plex setup.


Fortunately [https://www.nginx.com/ Nginx] can be used as a reverse proxy server to access Plex media server. Most of the configuration below comes from [https://forums.plex.tv/t/how-to-setup-nginx-as-a-reverse-proxy-for-plex/212702/2 kopfpilot] on the Plex forum.
Fortunately [https://www.nginx.com/ Nginx] can be used as a reverse proxy server to access Plex media server. Most of the configuration below comes from [https://forums.plex.tv/t/how-to-setup-nginx-as-a-reverse-proxy-for-plex/212702/2 kopfpilot] on the Plex forum.

Latest revision as of 13:33, 6 October 2024

Plex media server allows you to aggregate all your personal media and access it anywhere you go. Enjoy your own content on all your devices with Plex.

Basic setup

Plex is packaged in Nix. All you need is to edit your configuration.nix. A simple configuration looks like:

services.plex = {
  enable = true;
  openFirewall = true;
};

After adding this to your configuration.nix just rebuild your system.

Of course there's some more options that you can customize.

If your Plex media server is behind a router, you'll need to forward TCP port 32400 to your Plex media server.

Access Plex media server by browsing to http://lan_ip:32400/web

Allow Plex to read external drives

You might encounter permission issues when you try to access external drives if you haven't configured anything else with the server yet. If you haven't explicitly set up a mounting configuration for your drives and instead have your desktop environment (e.g. GNOME or KDE) automatically mount it when you try accessing it via their file explorers, Plex won't be able to access the drive. This is because the desktop environment mounts it to your user, while Plex runs by default as the "plex" user.

The easiest way to allow Plex to see these external drives is to change the Plex service's user . Here is an example:

services.plex = {
  enable = true;
  openFirewall = true;
  user="yourusername";
};

If you have changed the user option after you have already installed Plex, you have to change the permissions of the folder /var/lib/plex via chown to the user you set it to by doing this:

  sudo chown -R /var/lib/plex

The alternative to this is to explicitly mount the drives via Filesystems. This takes more effort to set up and requires every new drive you want plex to see to be explicitly declared, but allows more control in what Plex is allowed to see.

Clients

Plex Media Player

Plex Media Player is Plex's media client, packaged in Nix as plex-media-player.

Plex Desktop

Alternatively, a more newer and modern Plex client called Plex Desktop is packaged in Nix as plex-desktop.

To be able to sign in in Plex Desktop, you may need to set xdg.portal.xdgOpenUsePortal = true; in your NixOS configuration. See this issue.

Plexamp

Plex also provide Plexamp for music. It's packaged in Nix but (as of August 2024) only for x86_64.

SSL access via Nginx reverse proxy

Because of several redirects within Plex media server it's not easy to make it accessible through SSL. The browser can complain, even if you have configured proper SSL certificates in your Plex setup.

Fortunately Nginx can be used as a reverse proxy server to access Plex media server. Most of the configuration below comes from kopfpilot on the Plex forum.

# Nginx Reverse SSL Proxy
services.nginx = {
  enable = true;
  # give a name to the virtual host. It also becomes the server name.
  virtualHosts."sub.domain.tld" = {
    # Since we want a secure connection, we force SSL
    forceSSL = true;

    # http2 can more performant for streaming: https://blog.cloudflare.com/introducing-http2/
    http2 = true;

    # Provide the ssl cert and key for the vhost
    sslCertificate = "/https-cert.pem";
    sslCertificateKey = "/https-key.pem";
    extraConfig = ''

      #Some players don't reopen a socket and playback stops totally instead of resuming after an extended pause
      send_timeout 100m;

      # Why this is important: https://blog.cloudflare.com/ocsp-stapling-how-cloudflare-just-made-ssl-30/
      ssl_stapling on;
      ssl_stapling_verify on;

      ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
      ssl_prefer_server_ciphers on;
      #Intentionally not hardened for security for player support and encryption video streams has a lot of overhead with something like AES-256-GCM-SHA384.
      ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';

      # Forward real ip and host to Plex
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header Host $server_addr;
      proxy_set_header Referer $server_addr;
      proxy_set_header Origin $server_addr; 

      # Plex has A LOT of javascript, xml and html. This helps a lot, but if it causes playback issues with devices turn it off.
      gzip on;
      gzip_vary on;
      gzip_min_length 1000;
      gzip_proxied any;
      gzip_types text/plain text/css text/xml application/xml text/javascript application/x-javascript image/svg+xml;
      gzip_disable "MSIE [1-6]\.";

      # Nginx default client_max_body_size is 1MB, which breaks Camera Upload feature from the phones.
      # Increasing the limit fixes the issue. Anyhow, if 4K videos are expected to be uploaded, the size might need to be increased even more
      client_max_body_size 100M;

      # Plex headers
      proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier;
      proxy_set_header X-Plex-Device $http_x_plex_device;
      proxy_set_header X-Plex-Device-Name $http_x_plex_device_name;
      proxy_set_header X-Plex-Platform $http_x_plex_platform;
      proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version;
      proxy_set_header X-Plex-Product $http_x_plex_product;
      proxy_set_header X-Plex-Token $http_x_plex_token;
      proxy_set_header X-Plex-Version $http_x_plex_version;
      proxy_set_header X-Plex-Nocache $http_x_plex_nocache;
      proxy_set_header X-Plex-Provides $http_x_plex_provides;
      proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor;
      proxy_set_header X-Plex-Model $http_x_plex_model;

      # Websockets
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";

      # Buffering off send to the client as soon as the data is received from Plex.
      proxy_redirect off;
      proxy_buffering off;
    '';
    locations."/" = {
      proxyPass = "http://plex.domain.tld:32400/";
    };
  };
};

In order to use that, basically set the vhost name from sub.domain.tld to your actual (sub)domain name. Also point to the right sslCertificate and sslCertificateKey. Finally set the proxyPass address to where your Plex media server is.

After applying the changes, just browse to https://sub.domain.tld/web. Of course use your actual (sub)domain name.