Plex.TV (vm)

auto lo
iface lo inet loopback

allow-hotplug ens18
iface ens18 inet dhcp

https://app.plex.tv/desktop https://support.plex.tv/articles/200375666-plex-media-server-requirements/ https://support.plex.tv/articles/201370363-move-an-install-to-another-system/ https://support.plex.tv/articles/200288596-linux-permissions-guide/

Open a Terminal window or your command prompt Enter the following command (substituting the IP address of your server as appropriate): ssh -L 8888:127.0.0.1:32400 ip.address.of.server Open a browser window Type http://127.0.0.1:8888/web into the address bar The browser will connect to the server as if it were local and load Plex Web App https://support.plex.tv/articles/200288586-installation/

Best practice in Proxmox VE 9 is one VLAN-aware bridge (e.g., vmbr0) as a trunk, then tag each VM NIC with the VLAN it should use.

Why one VLAN-aware bridge? • Simplicity & scale: One trunked bridge carries many VLANs; you just set the VLAN Tag on each VM’s NIC. • Fewer moving parts: Easier to manage bonding/LACP and switch configs. • Works great with Proxmox firewall/ipfilter for per-VM IP enforcement.

Recommended setup 1. Make the main bridge VLAN-aware (UI: Datacenter → Node → Network → vmbr0 → check VLAN Aware). 2. Trunk the switchport facing your Proxmox NIC/bond (allow required VLANs). 3. On each VM NIC, set VLAN Tag to the right VLAN ID.

/etc/network/interfaces

auto vmbr0

iface vmbr0 inet manual bridge-ports bond0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes

auto vmbr0.10 iface vmbr0.10 inet static address 192.168.10.2/24 gateway 192.168.10.1 # if this is your mgmt VLAN

=== INitial configs

This file describes the network interfaces available on your system

and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

The loopback network interface

auto lo iface lo inet loopback

The primary network interface

allow-hotplug ens18 iface ens18 inet dhcp

This is an autoconfigured IPv6 interface

iface ens18 inet6 auto

auto lo iface lo inet loopback

source /etc/network/interfaces.d/*

Physical NIC, no IP here

allow-hotplug enp117s0 iface enp117s0 inet manual

VLAN-aware bridge

auto vmbr0 iface vmbr0 inet manual bridge-ports enp117s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes

Host management on VLAN 100

auto vmbr0.100 iface vmbr0.100 inet static address 192.168.248.2/24 # <– pick your host’s IP gateway 192.168.248.1 vlan-raw-device vmbr0

apt-get install nfs-common gpg

https://reintech.io/blog/setting-up-plex-media-server-on-debian-12

=========================== To resolve the Plex “Not Authorized” error on a Debian VM in Proxmox, first, ensure the VM is in a privileged mode, then use an SSH tunnel to connect to the server and access the web interface at localhost:32400/web to claim the server and link it to your Plex account. If the issue persists, verify Plex’s permissions for media directories, check for incorrect authentication tokens by renaming the Preferences.xml file, and ensure you’re signed into the same account on both the server and the web client.

1. Connect via SSH Tunnel This is the most reliable way to access the Plex interface for initial setup.

   Find your Plex server’s IP address within your Debian VM. Open a terminal on a device on the same network. Establish the SSH tunnel by running: ssh -L 32400:localhost:32400 root@. Open your web browser and navigate to http://localhost:32400/web. Log in with your Plex account and complete the setup to claim the server and link it to your account. Exit the SSH tunnel by typing exit in the terminal.

2. Verify Permissions The plex user needs access to your media files and directories.

   Identify the location of your media files. Use the ls -l command in the terminal to check the permissions. Grant read and execute permissions to the plex user using a command like sudo setfacl -R -m u:plex:rwx /path/to/your/media.

3. Check Authentication Token An invalid or expired authentication token can cause this error.

   Stop the Plex Media Server service on your Debian VM. Browse to the Plex data directory and locate the Preferences.xml file. Rename Preferences.xml to Preferences.old. Restart the Plex Media Server and try accessing the web interface again to force re-authentication.

4. Confirm Account Consistency You must be signed into the same Plex account on the server and the web client.

   Check the Plex server settings to ensure it’s signed into your account. Verify you are signed into the same account in your web browser when trying to access Plex.

5. Check Proxmox Container Mode Ensure your container is set to a privileged mode if it’s an LXC container, as this allows for better interaction with the host system. Unprivileged containers may require explicit host permission for operations